Re: Leveraging gcc in a cross-compilation environment

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 01/12/2010 10:43 AM, Ian Lance Taylor wrote:
> "Philip A. Prindeville" <philipp_subx@xxxxxxxxxxxxxxxxxxxxx> writes:
> 
>> Ok, so I'm invoking the compiler as:
>>
>> $ /home/philipp/kernel/build_i586/staging_dir/bin/i586-linux-uclibc-gcc -Os -pipe -fomit-frame-pointer -march=k6-2 -fno-align-functions -fno-align-loops -fno-align-jumps -fno-align-labels --sysroot=/home/philipp/kernel/build_i586/staging_dir -isystem /usr/include -Wall -O2 -D_REENTRANT -fPIC -Isrc/include -I/usr/include/openssl -I- '-DPROXY_VERSION="NOVER"' '-DCDIR="/etc"' '-DCFILE="astmanproxy.conf"' '-DMDIR="/usr/lib/astmanproxy/modules"' '-DPDIR="/etc/asterisk"' '-DPFILE="astmanproxy.users"' -cb -o ssl.o src/ssl.c -v
> 
> You explicitly passed -isystem /usr/include, so gcc searches
> /usr/include.
> 
> As of gcc 4.3 you would -isystem =/usr/include to apply the sysroot to
> your -isystem parameter.
> 
> Ian

I have to say, the overloading of '=' *plus* the fact that some arguments use '=' (like --sysroot=) while others don't (-isystem xxx) is confusing.

Ok, what about how 'ld' interprets --sysroot?  If I have "ld --sysroot /xyzzy -L/a/b/c" will it look in /xyzzy/a/b/c?



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux