This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: Link tests after GCC_NO_EXECUTABLES
- From: Rask Ingemann Lambertsen <rask at sygehus dot dk>
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, rsandifo at nildram dot co dot uk, fortran at gcc dot gnu dot org, java-patches at gcc dot gnu dot org
- Date: Fri, 7 Dec 2007 22:47:46 +0100
- Subject: Re: Link tests after GCC_NO_EXECUTABLES
- References: <20071201120251.GT17368@sygehus.dk> <jesl2mlen1.fsf@sykes.suse.de> <20071201223447.GU17368@sygehus.dk> <47531F54.6010802@codesourcery.com> <20071205172224.GM17368@sygehus.dk> <47574456.1070108@codesourcery.com> <20071206175819.GO17368@sygehus.dk> <4758A3BD.5050102@codesourcery.com> <20071207153101.GR17368@sygehus.dk> <47599307.30409@codesourcery.com>
On Fri, Dec 07, 2007 at 10:37:59AM -0800, Mark Mitchell wrote:
>
> I have to admit that I'm getting concerned. The issue Richard has
> raised about Cygwin, and the various corner-cases here are making me
> think that we're at risk of introducing instability.
I think so too. If the Cygwin example had been raised a week ago I
wouldn't have used ${with_newlib} to enable use of the cache file.
Status is that I would still hate to loose the ability to build the
simulator targets in a straight-forward way. At the same time, I can easily
live with adding one more option to the configure command to get the
simulator targets to build. So my suggestion is this:
1) Make the cached link test results require an explicit option to enable
them. I can code that up tomorrow.
2) Put in the libstdc++ patch.
3) Revert the top level changes for the -B and -L options.
Does this sound safe enough?
--
Rask Ingemann Lambertsen
Danish law requires addresses in e-mail to be logged and stored for a year