[poky] gcc -print-file-name option without path?
Zoufal Andreas
Andreas.Zoufal at ait.ac.at
Mon Mar 26 09:23:55 PDT 2012
Thanks Matthew, yes it seems this is the solution. I tried it manually.
I wonder, I sourced the environment file and the CFLAGS, LDFLAGS and so on should be set with --sysroot. Can it be, kernel make file overwrite this options? And how can I make this option available to kernels makefile without modifying it?
Andi
-----Original Message-----
From: McClintock Matthew-B29882 [mailto:B29882 at freescale.com]
Sent: Monday, March 26, 2012 6:02 PM
To: Zoufal Andreas
Cc: poky at yoctoproject.org
Subject: Re: [poky] gcc -print-file-name option without path?
On Mon, Mar 26, 2012 at 10: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
Andi,
Make sure you are passing the --sysroot option to gcc, this is the
default CC used in Yocto. Then it should find libgcc OK.
-M
More information about the poky
mailing list