This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 01/16/10 17:02, Yann E. MORIN wrote: > Jonathan, All, > > On Friday 15 January 2010 19:59:51 Jonathan Cameron wrote: >> On 01/15/10 18:03, Yann E. MORIN wrote: >>> What is really important is the complete log file, as pointed to by >>> the excerpt you quoted: >> fair point, attached. At first glance it isn't a great deal more >> informative. >> Actually this precise log is the cvs version of newlib. Same thing at >> least superficially >> occurs with 1.17 and 1.18 releases. > > Looks very much like: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34226 > > And the patch attached to the PR still applies (albeit with offset): > http://gcc.gnu.org/bugzilla/attachment.cgi?id=14678&action=view > > Could you please try to apply this patch to your gcc sources, try to > rebuild, and tell us the result? > It does indeed look pretty similar. Unfortunately, the dumb approach of applying that patch to gcc without really following what it is doing doesn't seem to fix the problem. I haven't reattached the log as it appears to be exactly the same in the relevant regions. (only changes are the additional local patch as per the link above). Thanks, Jonathan -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |