[Buildroot] svn commit: trunk/buildroot/toolchain/gcc
rep.dot.nop at gmail.com
Sat Oct 13 11:23:29 UTC 2007
On Sat, Oct 13, 2007 at 12:19:42PM +0200, Cristian Ionescu-Idbohrn wrote:
>On Sat, 13 Oct 2007, Ulf Samuelsson wrote:
>> lör 2007-10-13 klockan 10:49 +0200 skrev Cristian Ionescu-Idbohrn:
>> > On Fri, 12 Oct 2007, ulf at uclibc.org wrote:
>> > > Author: ulf
>> > > Date: 2007-10-12 14:01:41 -0700 (Fri, 12 Oct 2007)
>> > > New Revision: 20237
>> > >
>> > > Log:
>> > > Allow library copy to fail
>> > As it's not obvious to me, may I ask why?
>> > Why not making sure it doesn't fail, instead?
>> That is the long term approach, but I have no control over that part.
>Who has the "control over that part"?
>> If copying fails,
>Why should it?
>Have you seen it failing?
>Can you reproduce that?
It can be seen with x86_64 as target; see archives for my suggestion on
how to fix this properly instead of once again papering over a bug in an
>Is there a use case you can share with us?
>> then libgcc.a is available,
>> and the end application can be linked with this instead
>> It is better than aborting the build.
>But doesn't cure the disease :(
It's plain wrong i would have said.
>In other words, you prefer aspirine :)
More information about the buildroot