[poky] gcc -print-file-name option without path?
Andreas Zoufal
andreas.zoufal at ait.ac.at
Tue Mar 27 01:13:16 PDT 2012
I can only say that this part of the Makefile, here is the grep output:
./arch/arm/boot/compressed/Makefile: $(shell $(CC) $(KBUILD_CFLAGS)
--print-libgcc-file-name) -T
We use the TI PSP.03.XX.00.37 Kernel. I checked the source code for the
current stable kernel release, the usage of '-print-libgcc-file-name'
vanished for the ARM architecture, but is still used for some others.
On 03/26/2012 11:44 PM, Khem Raj wrote:
> On Mon, Mar 26, 2012 at 8:57 AM, Zoufal Andreas
> <Andreas.Zoufal at ait.ac.at> wrote:
>> Hello,
>> We am starting to use the Yocto/Poky toolchain as replacement for ELDK5. Trying to compile our existing kernel fails, but it worked fine with ELDK5. Doing some investigation we recognized a different behavior which I guess is the reason for the problem: using the cross compiler to show the path of the libgcc.a with the option "-print-libgcc-file-name" doesn't show the full path, only the filename itself! But ELDK5 does.
>> I'm using poky-1.2_M3.final for arm, and the build folder is in my home directory, like:
>> /home/user/path/to/project/poky/build/tmp/sysroots ...and so on
>> Am I doing something wrong? gcc --help says that the -print-file-name should return the full path, which is even not true.
>> Kind regards, Andi
>
> while the problem is not passing --sysroot option I wonder why do you query for
> libgcc when you are building kernel ? kernel should not need libgcc as
> it provides any function needed from libgcc in a library of its own.
>> _______________________________________________
>> poky mailing list
>> poky at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/poky
More information about the poky
mailing list