Thomas Martitz wrote:
Am 19.11.2009 17:19, schrieb Tobias Ringström:
On 11/19/2009 04:44 PM, Kai Ruottu wrote:
Probably not any more, why else libgcc was moved away from
'gcc'.... What must be
used when producing both GCC and libgcc, this the docs should tell.
I would expect:
make all-target-libgcc
being that. Producing libgcc for the $target has GCC for the
$target as prerequisite so
this sounds logical to me...
Thank you! I can now successfully build gcc-4.4.2 for arm-elf, though
I had to run:
make all-gcc all-target-libgcc
make install-gcc install-target-libgcc
to have the actual compiler installed as well. :-)
/Tobias
I too managed that. However, I still think it's a bug in gcc, as 4.4.1
compiles fine with the very same settings.
The 'arm-*eabi*' targets handling at least seem to be somehow buggy, for
myself it happened
that the build of a cross GCC for 'arm-maemo-linux-gnueabi' went really
weirdly when I had
the newlib's two subdirs, 'newlib' and 'libgloss' symlinked into the
gcc-4.4.2 sources. There
was no '--with-newlib' in the GCC configure command but despite of this
the build tried to use
the newlib headers in the sources before the proper target ones /from
'www.scratchbox.otg'),
sysrooted in the chosen $sysroot....
