[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: nit about ./config.status
From: |
Raja R Harinath |
Subject: |
Re: nit about ./config.status |
Date: |
Sat, 19 Jan 2002 15:44:38 -0600 |
User-agent: |
Gnus/5.090005 (Oort Gnus v0.05) Emacs/21.2.50 (i686-pc-linux-gnu) |
Hi,
Simon Josefsson <address@hidden> writes:
> Akim Demaille <address@hidden> writes:
>
>>>>>>> "Simon" == Simon Josefsson <address@hidden> writes:
>>
>> Simon> In older autoconf versions, I often used 'less config.status'
>> Simon> and cut'n'pasted the cmdline to ./configure to reconfigure a
>> Simon> package. With autoconf 2.5 the cmdline used is available with
>> Simon> ./config.status --version, but not in a cut'n'paste friendly
>> Simon> format. Any chance of including the ./configure cmdline in a
>> Simon> comment at the start of config.status as before? (Or make
>> the Simon> --version output more cut'n'paste friendly.)
>>
>> Am I missing something, you just want to run ./config.status
> --recheck?
>
> If I'm on the same machine and if the package had proper make rules to
> regenerate Makefile etc when needed, yes, but I often find myself
> compiling the same package on different platforms at the same time and
> I usually wants to use the same configure params. Hence my use of
> 'less config.status' and cut'n'paste. As I said, not a major
> issue. :-)
I often do
mkdir -p build/{linux,sol}
cd build/linux
../../configure --prefix=foo --enable-bar
cd ../sol
../linux/config.status --recheck && ./config.status
It works most of the time.
- Hari
--
Raja R Harinath ------------------------------ address@hidden
"When all else fails, read the instructions." -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing." -- Roy L Ash
Re: nit about ./config.status, Tom Tromey, 2002/01/19