[Buildroot] svn commit: trunk/buildroot/package

[Daniel Laird]

All,

I have been looking a bit more into the issues around the --rpath-link
options. 
1. It seems that we should only do this for people using external toolchains
as currently it appears buildroot built toolchains are ok.
2. I think that we could use --sysroot cflags.
   This is only supported in GCC 4.2 and later so this would need to be
checked.
   We would then need to copy all compiler includes into
$STAGING_DIR/usr/include
   Then I believe we could pass --sysroot=$STAGING_DIR as a cflag and this
should then pick up all headers and libraries.

Does anyone have any thoughts on this.   I have not tried it yet but perhaps
you have?

Hope you can help
Daniel Laird

-----Original Message-----
From: buildroot-bounces at uclibc.org [mailto:buildroot-bounces at uclibc.org] On
Behalf Of Roberto A. Foglietta
Sent: 2008 Nov 15 06:07
To: Arnar Mar Sig
Cc: buildroot at uclibc.org
Subject: Re: [Buildroot] svn commit: trunk/buildroot/package

2008/11/12 Arnar Mar Sig <antab at valka.is>:
>
> On Nov 12, 2008, at 8:55 AM, Thomas Petazzoni wrote:
>
>> Le Tue, 11 Nov 2008 20:09:06 -0500,
>> "hartleys" <hartleys at visionengravers.com> a écrit :
>>
>>> Each source file hit with CC produces a warning message. Everything
>>> hit with LD is fine. Here's a snip of the output:
>>>
>>> ...
>>> LD      lib/zlib_inflate/zlib_inflate.o
>>> LD      lib/zlib_inflate/built-in.o
>>> CC      lib/audit.o
>>> arm-linux-gcc: --rpath-link: linker input file unused because linking
>>> not done
>>> arm-linux-gcc: /home/bigguiness/buildroot/build_arm/staging_dir/lib:
>>> linker input file unused because linking not done
>>> arm-linux-gcc: --rpath-link: linker input file unused because linking
>>> not done
>>> arm-linux-gcc: /home/bigguiness/buildroot/build_arm/staging_dir/usr/
>>> lib:
>>> linker input file unused because linking not done
>>
>> Odd. I did try to build the kernel and didn't see this messages. I
>> will
>> try something else.
>>
>> Sincerly,
>>
>> Thomas
>
>
> This also happen when building for AVR32.

It happens in i586 too, please take a look to this report

http://busybox.net/bugs/view.php?id=6324

may be it is related with your changes.

 Ciao,
-- 
/roberto
_______________________________________________
buildroot mailing list
buildroot at uclibc.org
http://busybox.net/mailman/listinfo/buildroot