Bug in gcc.c for_each_path() (leads to invalid crt0.o selection)?
sebastian.huber at embedded-brains.de
Thu Dec 8 08:58:56 UTC 2016
On 06/12/16 18:09, Joseph Myers wrote:
> On Tue, 6 Dec 2016, Sebastian Huber wrote:
>> thanks for the detailed explanation. I guess, then the root cause for my
>> problem is that the Newlib provided crt0.o files in the build tree are not in
>> the same relative location of the installation tree. In the build tree, they
>> reside in a "newlib" subdirectory. I changed the Newlib build flags set by GCC
>> to use -L instead of -B and this seems to work (comment is wrong now). Does it
>> make sense to submit such a patch or has it maybe some nasty side-effects?
> I don't know what the effects of such a change might be.
Using -L instead of -B had the same problems. My attempt to fix this
problem is this patch:
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber at embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
More information about the devel