[Top][All Lists]

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

Re: Overriding LN_S

From: Ralf Wildenhues
Subject: Re: Overriding LN_S
Date: Thu, 2 Sep 2010 22:43:07 +0200
User-agent: Mutt/1.5.20 (2010-04-22)

* Peter Rosin wrote on Thu, Sep 02, 2010 at 09:45:13PM CEST:
> Den 2010-09-02 21:32 skrev Ralf Wildenhues:
> > * Peter Rosin wrote on Thu, Sep 02, 2010 at 09:18:29PM CEST:
> >> I also want this to
> >> propagate to recursive autoconf invocations, so it is not
> >> sufficient to manually edit the generated configure script.
> > 
> > You mean recursive configure invocations?
> No, I meant that some libtool tests invoke autoconf, and then configures
> the result, e.g. libtool/tests/
> If I hack up my top level configure to go with LN_S="cp -p", that will
> not matter when the testsuite gets to, since it will
> reset LN_S to "ln -s". At least I think it will, I haven't actually
> tried...

Well, we /should/ fix Autoconf to allow overriding, and at that point,
you should be able to override globally with export LN_S=...
(though I'm not sure if LN_S will be the variable to set, that's not in
the m4sh name space).


reply via email to

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