This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: top level makefile cleanup (prep for autoconfiscation)
- From: Nathanael Nerode <neroden at doctormoo dot dyndns dot org>
- To: Daniel Jacobowitz <drow at mvista dot com>
- Cc: Alexandre Oliva <aoliva at redhat dot com>, gcc-patches at gcc dot gnu dot org
- Date: Mon, 28 Jan 2002 21:47:13 -0500 (EST)
- Subject: Re: PATCH: top level makefile cleanup (prep for autoconfiscation)
On Mon, 28 Jan 2002, Daniel Jacobowitz wrote:
> On Mon, Jan 28, 2002 at 09:26:35PM -0500, Nathanael Nerode wrote:
> > On Mon, 28 Jan 2002, Daniel Jacobowitz wrote:
> >
> > > On Mon, Jan 28, 2002 at 11:33:31PM -0200, Alexandre Oliva wrote:
> > > > On Jan 28, 2002, Daniel Jacobowitz <drow@mvista.com> wrote:
> > > >
> > > > > Just be careful trying to configure multiple targets at the same time.
> > > > > They share a config.cache; really only one of the scripts can safely
> > > > > run at once.
> > They don't have to share a cache, and they probably shouldn't...
> > I just haven't figured out the best way to manipulate cache file choice in
> > autoconf scripts...
>
> No, they absolutely should do so. If they don't then you repeat tests
> dozens of times.
Rrgh, right, I was thinking of the case where you're configuring for two
different target *systems* :-/
Ideally autoconf scripts would properly lock and unlock the cache file :-)
That may be too much to hope for though.
--Nathanael