Hi all,

I was wondering if anyone has managed to successfully compile a GDC cross compiler to target the Raspberry Pi?

I tried following the instructions found at http://bitbucket.org/goshawk/gdc/wiki/crosstool-ng but when I try the "ct-ng build" command I get the following output:

[INFO ]  Performing some trivial sanity checks
[INFO ]  Build started 20120613.010123
[INFO ]  Building environment variables
[ERROR]  Static linking impossible on the host system 'x86_64-build_unknown-linux-gnu'
[00:02] / make: *** [build] Error 1

Should I continue along the path of using crosstools to make a cross compiler, and if so; how? Or is there a better way to achieve my end goal of having a cross compiler targeting the Raspberry Pi?

Thanks in advance for any help :-)

On Tuesday, 12 June 2012 at 13:06:05 UTC, Henry Robbins Gouk
wrote:
> Hi all,
>
> I was wondering if anyone has managed to successfully compile a GDC cross compiler to target the Raspberry Pi?
>
> I tried following the instructions found at http://bitbucket.org/goshawk/gdc/wiki/crosstool-ng but when I try the "ct-ng build" command I get the following output:
>
> [INFO ]  Performing some trivial sanity checks
> [INFO ]  Build started 20120613.010123
> [INFO ]  Building environment variables
> [ERROR]  Static linking impossible on the host system 'x86_64-build_unknown-linux-gnu'
> [00:02] / make: *** [build] Error 1
>
> Should I continue along the path of using crosstools to make a cross compiler, and if so; how? Or is there a better way to achieve my end goal of having a cross compiler targeting the Raspberry Pi?
>
> Thanks in advance for any help :-)

I tried to build it as a cross compiler and on the raspberry
directly - and faild at both. On the raspberry I got a compiler
crash, and the cross compiler build process produced random
errors - it seems to be very fragile in terms of library versions
and such.

...so I would also be very interested in any sucess stories.

On 12 June 2012 16:57, <sludwig@outerproduct.org>"@puremagic.com <"\"Sönke".Ludwig"> wrote:
> On Tuesday, 12 June 2012 at 13:06:05 UTC, Henry Robbins Gouk wrote:
>
>> Hi all,
>>
>> I was wondering if anyone has managed to successfully compile a GDC cross compiler to target the Raspberry Pi?
>>
>> I tried following the instructions found at http://bitbucket.org/goshawk/gdc/wiki/crosstool-ng but when I try the "ct-ng build" command I get the following output:
>>
>> [INFO ]  Performing some trivial sanity checks
>> [INFO ]  Build started 20120613.010123
>> [INFO ]  Building environment variables
>> [ERROR]  Static linking impossible on the host system
>> 'x86_64-build_unknown-linux-gnu'
>> [00:02] / make: *** [build] Error 1
>>
>> Should I continue along the path of using crosstools to make a cross compiler, and if so; how? Or is there a better way to achieve my end goal of having a cross compiler targeting the Raspberry Pi?
>>
>> Thanks in advance for any help :-)
>
>
> I tried to build it as a cross compiler and on the raspberry directly - and faild at both. On the raspberry I got a compiler crash, and the cross compiler build process produced random errors - it seems to be very fragile in terms of library versions and such.
>
> ...so I would also be very interested in any sucess stories.

Does it get as far as building libphobos/libdruntime ?

I would be interested in, if possible:

1) Build logs or exact errors of what ICE's / crashes you are getting
from the compiler.
2) A copy of the generated phobos-vers-sym file from the libphobos
build directory.
3) A copy of d-confdefs.h from the gcc/d build directory.


Regards

-- 
Iain Buclaw

*(p < e ? p++ : p) = (c & 0x0f) + '0';

Am 12.06.2012 18:09, schrieb Iain Buclaw:
> On 12 June 2012 16:57,<sludwig@outerproduct.org>"@puremagic.com
> <"\"Sönke".Ludwig">  wrote:
>> On Tuesday, 12 June 2012 at 13:06:05 UTC, Henry Robbins Gouk
>> wrote:
>>
>>> Hi all,
>>>
>>> I was wondering if anyone has managed to successfully compile a GDC cross
>>> compiler to target the Raspberry Pi?
>>>
>>> I tried following the instructions found at
>>> http://bitbucket.org/goshawk/gdc/wiki/crosstool-ng but when I try the "ct-ng
>>> build" command I get the following output:
>>>
>>> [INFO ]  Performing some trivial sanity checks
>>> [INFO ]  Build started 20120613.010123
>>> [INFO ]  Building environment variables
>>> [ERROR]  Static linking impossible on the host system
>>> 'x86_64-build_unknown-linux-gnu'
>>> [00:02] / make: *** [build] Error 1
>>>
>>> Should I continue along the path of using crosstools to make a cross
>>> compiler, and if so; how? Or is there a better way to achieve my end goal of
>>> having a cross compiler targeting the Raspberry Pi?
>>>
>>> Thanks in advance for any help :-)
>>
>>
>> I tried to build it as a cross compiler and on the raspberry
>> directly - and faild at both. On the raspberry I got a compiler
>> crash, and the cross compiler build process produced random
>> errors - it seems to be very fragile in terms of library versions
>> and such.
>>
>> ...so I would also be very interested in any sucess stories.
>
> Does it get as far as building libphobos/libdruntime ?
>
> I would be interested in, if possible:
>
> 1) Build logs or exact errors of what ICE's / crashes you are getting
> from the compiler.
> 2) A copy of the generated phobos-vers-sym file from the libphobos
> build directory.
> 3) A copy of d-confdefs.h from the gcc/d build directory.
>
>
> Regards
>

It failed already during the gdc build. I'll repeat the process and collect the logs (I hope I can do that sometime this weekend).

> 1) Build logs or exact errors of what ICE's / crashes you are getting
> from the compiler.
> 2) A copy of the generated phobos-vers-sym file from the libphobos
> build directory.
> 3) A copy of d-confdefs.h from the gcc/d build directory.
>

I retried now with your version of GDC on github and didn't get the ICE but always got some compile errors (I first went from gcc 4.6.1 over 4.7.0 and 4.7.1 to a snapshot of 4.8 from march and finally to the 20120617 snapshot). The configure/make output is attached and the gcc/d/d-confdefs.h contains:

#define D_CPU_VERSION "ARM"
#define D_OS_VERSION "linux"
#define TARGET_LINUX 1

The error is that the macro "#define CLEAR_INSN_CACHE(REG, END) not_used" is used somewhere in the libgcc target. There are two logs because there was a weird make crash on the first run - the second build proceeded further. I didn't get to the libphobos stuff so there is no phobos-vers-sym file.

Regards,
Sönke

Am Tue, 12 Jun 2012 17:57:39 +0200
schrieb "Sönke Ludwig" <sludwig@outerproduct.org>:

> On Tuesday, 12 June 2012 at 13:06:05 UTC, Henry Robbins Gouk wrote:
> > Hi all,
> >
> > I was wondering if anyone has managed to successfully compile a GDC cross compiler to target the Raspberry Pi?
> >
> > I tried following the instructions found at http://bitbucket.org/goshawk/gdc/wiki/crosstool-ng but when I try the "ct-ng build" command I get the following output:
> >
> > [INFO ]  Performing some trivial sanity checks
> > [INFO ]  Build started 20120613.010123
> > [INFO ]  Building environment variables
> > [ERROR]  Static linking impossible on the host system
> > 'x86_64-build_unknown-linux-gnu'
> > [00:02] / make: *** [build] Error 1
> >
> > Should I continue along the path of using crosstools to make a cross compiler, and if so; how? Or is there a better way to achieve my end goal of having a cross compiler targeting the Raspberry Pi?
> >
> > Thanks in advance for any help :-)
> 
> I tried to build it as a cross compiler and on the raspberry directly - and faild at both. On the raspberry I got a compiler crash, and the cross compiler build process produced random errors - it seems to be very fragile in terms of library versions and such.
> 
> ...so I would also be very interested in any sucess stories.

Sorry, probably a stupid question, but could the build on the PI have died because of too little ram?

Anyway, building a compiler on the raspberry pi worked for me, although
it took a long time to build. I created a new wiki page with build
instructions:
https://bitbucket.org/goshawk/gdc/wiki/Raspberry%20Pi

On 3 July 2012 18:30, Johannes Pfau <nospam@example.com> wrote:
> Am Tue, 12 Jun 2012 17:57:39 +0200
> schrieb "Sönke Ludwig" <sludwig@outerproduct.org>:
>
>> On Tuesday, 12 June 2012 at 13:06:05 UTC, Henry Robbins Gouk wrote:
>> > Hi all,
>> >
>> > I was wondering if anyone has managed to successfully compile a GDC cross compiler to target the Raspberry Pi?
>> >
>> > I tried following the instructions found at http://bitbucket.org/goshawk/gdc/wiki/crosstool-ng but when I try the "ct-ng build" command I get the following output:
>> >
>> > [INFO ]  Performing some trivial sanity checks
>> > [INFO ]  Build started 20120613.010123
>> > [INFO ]  Building environment variables
>> > [ERROR]  Static linking impossible on the host system
>> > 'x86_64-build_unknown-linux-gnu'
>> > [00:02] / make: *** [build] Error 1
>> >
>> > Should I continue along the path of using crosstools to make a cross compiler, and if so; how? Or is there a better way to achieve my end goal of having a cross compiler targeting the Raspberry Pi?
>> >
>> > Thanks in advance for any help :-)
>>
>> I tried to build it as a cross compiler and on the raspberry directly - and faild at both. On the raspberry I got a compiler crash, and the cross compiler build process produced random errors - it seems to be very fragile in terms of library versions and such.
>>
>> ...so I would also be very interested in any sucess stories.
>
> Sorry, probably a stupid question, but could the build on the PI have died because of too little ram?
>
> Anyway, building a compiler on the raspberry pi worked for me, although
> it took a long time to build. I created a new wiki page with build
> instructions:
> https://bitbucket.org/goshawk/gdc/wiki/Raspberry%20Pi
>

I have a wiki at http://gdcproject.org/wiki   :-)


-- 
Iain Buclaw

*(p < e ? p++ : p) = (c & 0x0f) + '0';

Am 03.07.2012 19:30, schrieb Johannes Pfau:
> Am Tue, 12 Jun 2012 17:57:39 +0200
> schrieb "Sönke Ludwig" <sludwig@outerproduct.org>:
>
>> On Tuesday, 12 June 2012 at 13:06:05 UTC, Henry Robbins Gouk
>> wrote:
>>> Hi all,
>>>
>>> I was wondering if anyone has managed to successfully compile a
>>> GDC cross compiler to target the Raspberry Pi?
>>>
>>> I tried following the instructions found at
>>> http://bitbucket.org/goshawk/gdc/wiki/crosstool-ng but when I
>>> try the "ct-ng build" command I get the following output:
>>>
>>> [INFO ]  Performing some trivial sanity checks
>>> [INFO ]  Build started 20120613.010123
>>> [INFO ]  Building environment variables
>>> [ERROR]  Static linking impossible on the host system
>>> 'x86_64-build_unknown-linux-gnu'
>>> [00:02] / make: *** [build] Error 1
>>>
>>> Should I continue along the path of using crosstools to make a
>>> cross compiler, and if so; how? Or is there a better way to
>>> achieve my end goal of having a cross compiler targeting the
>>> Raspberry Pi?
>>>
>>> Thanks in advance for any help :-)
>>
>> I tried to build it as a cross compiler and on the raspberry
>> directly - and faild at both. On the raspberry I got a compiler
>> crash, and the cross compiler build process produced random
>> errors - it seems to be very fragile in terms of library versions
>> and such.
>>
>> ...so I would also be very interested in any sucess stories.
>
> Sorry, probably a stupid question, but could the build on the PI have
> died because of too little ram?
>
> Anyway, building a compiler on the raspberry pi worked for me, although
> it took a long time to build. I created a new wiki page with build
> instructions:
> https://bitbucket.org/goshawk/gdc/wiki/Raspberry%20Pi
>

Out of memory was the first problem if I remember right, which I fixed by enabling swap, but all the following errors were something different. Your instructions look a lot like what I've tried last, apart from some command switches. I will try again with those.

>
> Anyway, building a compiler on the raspberry pi worked for me, although
> it took a long time to build. I created a new wiki page with build
> instructions:
> https://bitbucket.org/goshawk/gdc/wiki/Raspberry%20Pi
>

I've done some new attempts. After using a different OS image on a different SD card, everything worked much better (raspbian "Pisces"). I followed your instructions on the wiki page but had to change arm-linux-gnueabi to arm-linux-gnueabihf and later removed them altogether with the same effect.

However, compilation got stuck at the same place as before. It couldn't find <bits/predefs.h> and other architecture specific files. Symlinking from /usr/include/arm-linux-gnueabihf/* to gcc/* helped a bit until it stopped with the same error as in the build log that I posted before.

I will probably just try the debian image, although a system with hardfloat support would be pretty important in the long run. But the fact that it doesn't find the /sys/, /bits/ etc. headers sounds like it is just some stupid little build problem. But I'm much too unfamiliar with the GCC build process to make effective guesses for a solution.

On Sunday, 15 July 2012 at 15:11:03 UTC, Sönke Ludwig wrote:
>
>>
>> Anyway, building a compiler on the raspberry pi worked for me, although
>> it took a long time to build. I created a new wiki page with build
>> instructions:
>> https://bitbucket.org/goshawk/gdc/wiki/Raspberry%20Pi
>>
>
> I've done some new attempts. After using a different OS image on a different SD card, everything worked much better (raspbian "Pisces"). I followed your instructions on the wiki page but had to change arm-linux-gnueabi to arm-linux-gnueabihf and later removed them altogether with the same effect.
>
> However, compilation got stuck at the same place as before. It couldn't find <bits/predefs.h> and other architecture specific files. Symlinking from /usr/include/arm-linux-gnueabihf/* to gcc/* helped a bit until it stopped with the same error as in the build log that I posted before.
>
> I will probably just try the debian image, although a system with hardfloat support would be pretty important in the long run. But the fact that it doesn't find the /sys/, /bits/ etc. headers sounds like it is just some stupid little build problem. But I'm much too unfamiliar with the GCC build process to make effective guesses for a solution.

Following the instructions at Johannes Pfau's link above I
managed to get the compiler up and running on the squeeze image
(not counting stupidity on my part which made the compilation
fail more than six hours into the process...). So thanks for
that! However, I am curious if anyone has made any progress
getting it to work on the raspbian image. I will try some things
tomorrow (though I'm a newbie, so I doubt I'll get very far on my
own) but with the 8-hour compilation cycles I would like to avoid
any stupid mistakes if possible. Any experiences or tips would be
helpful!

Regards,

Stefan