[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [patch] remove config.status race condition

From: akim
Subject: Re: [patch] remove config.status race condition
Date: Sat, 24 Feb 2001 01:31:46 +0100
User-agent: Mutt/1.3.12i

On Fri, Feb 23, 2001 at 02:54:06PM -0500, Pavel Roskin wrote:
> > > Are you sure that $$ is always preserved across subshells? What it I
> > > create conf$$ in a subshell but want to access it in the top level shell?
> >
> > Sorry, but I don't understand why you are referring to subshells here.
> > If anyway we were actually playing with subshells, we'd be in trouble
> > to have the subshell pass relevant information to the mother, who is
> > the one who wants information.
> Unless you are using files with known names.
> > Please develop.
> Maybe it's too primitive, but I hope you will get the idea:
> (
> # Do it in subshell to avoid saving all variables
> cat >conf$$.c <<EOF
> $1
> CFLAGS="$CFLAGS -fnord"
> LIBS="$LIBS -lol"
> $CC $CFLAGS $LIBS -o conf$$ conf$$.c
> ./conf$$ >conf$$.val
> rm -f conf$$ conf$$.c
> )
> ac_result=`cat conf$$.val`
> rm -f conf$$.val

So, I have been underspecific.  In mean in the context of Autoconf.
I just don't care about m4sh.m4 *at all*, the point is Autoconf, preiod.
My question is where do you think the subshell issue matters at all for
the present problem.

We have one issue, and only one: relasing Autoconf.  Everything else
is pleasant but up to the current date useless, M4sh is *not* released,
it is just a detail of Autoconf's implementation.

If you can see a problem *in Autoconf*, please make it clear.
If there are no problem with Autoconf, then there are no problems
at all.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]