This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: [ping2] Re: [ping] Re: [patch] PR40134, use a linker script on arm-linux to link with -lgcc_s -lgcc
- From: Paolo Carlini <paolo dot carlini at oracle dot com>
- To: Matthias Klose <doko at ubuntu dot com>
- Cc: "libstdc++ at gcc dot gnu dot org" <libstdc++ at gcc dot gnu dot org>, Richard Earnshaw <Richard dot Earnshaw at arm dot com>, Andrew Haley <aph at redhat dot com>, Jakub Jelinek <jakub at redhat dot com>, Alexandre Oliva <aoliva at redhat dot com>, Nathan Froyd <froydnj at codesourcery dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>, GCJ-patches <java-patches at gcc dot gnu dot org>
- Date: Thu, 12 Nov 2009 19:32:00 +0100
- Subject: Re: [ping2] Re: [ping] Re: [patch] PR40134, use a linker script on arm-linux to link with -lgcc_s -lgcc
- References: <4A530F5C.4040500@ubuntu.com> <20090707091425.GB4462@tyan-ft48-01.lab.bos.redhat.com> <4A5B32BB.5010308@ubuntu.com> <20090909112436.GV14664@tyan-ft48-01.lab.bos.redhat.com> <4AAA8510.8060906@ubuntu.com> <4AB8C07D.3010807@ubuntu.com> <4AB8F3C2.60909@redhat.com> <4ABB2CB3.8090800@ubuntu.com> <4ABB30DE.6050502@redhat.com> <4ABB3BE6.4060800@ubuntu.com> <4ABB4C9B.3070200@redhat.com> <1255527525.4842.29.camel@e200601-lin.cambridge.arm.com> <4ADF0B67.9070505@ubuntu.com> <4AEA2FF1.6060508@ubuntu.com> <4AEA3318.6060607@oracle.com> <4AEF025A.5060403@ubuntu.com> <4AEF08BF.4020500@oracle.com> <4AFC5187.2010909@ubuntu.com>
Matthias Klose wrote:
> In http://gcc.gnu.org/ml/gcc-patches/2009-07/msg00733.html I wrote
> that this scheme requires fixing libtool; I never got feedback from
> the libtool maintainers. In
> http://gcc.gnu.org/ml/gcc-patches/2009-09/msg00592.html Jakub and
> Alexandre did "agree that the linker script for targets that need it
> is probably easier".
I'm still not convinced that all the targets possibly affected have been
dealt with. But, I don't consider myself knowledgeable enough in this
area, I'd like to see some comments from, eg, Jakub and Joseph, before
going ahead with the libstdc++ changes for 40133.
>> In other
>> terms, 40134 still blocks 40133, and we cannot fix the latter until the
>> former is really fully fixed for *all* the affected targets. By the way,
>> that's why, sorry, I disregarded your ping in the first place, I was
>> pretty sure it wasn't time yet...
> So it looks like 40134 is fixed at least for all *-linux targets (I
> accidentally dropped the patch for parisc, now testing again). How to
> proceed with this for linux targets?
In your original message you mentioned sparc too. Is it now fine?
Anyway, the configure changes I prepared for 40133 aren't linux-specific
would run anywhere, as I said above I'd like to be reassured by Joseph
and/or Jakub that such kind of test is now safe to use everywhere as far
as the compiler proper bits are concerned.
Paolo.