[Top][All Lists]

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

Re: [Lynx-dev] Determining previous configure command used to build lynx

From: Ivan Shmakov
Subject: Re: [Lynx-dev] Determining previous configure command used to build lynx
Date: Wed, 11 Apr 2012 14:09:29 +0700
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)

>>>>> Keith Bowes <address@hidden> writes:
>>>>> Je 2012-04-03 je 12:49:26 (+0100) Mark Skilbeck skribis:

 >> Just me again.

 >> If I've compiled lynx from source, can I determine the configure
 >> command (and options) that was used to compile it?  I've lost the
 >> command from my terminal command history and can't remember all the
 >> options I used.

 > If you've saved the source, the configure options are stored in
 > config.status.  For example, to reconfigure based on your previous
 > options:

        IFTR if there were any specifics in Lynx, but for GNU Autoconf,
        it's the /build/ (and not the /source/) directory that is to be
        saved (although they may coincide.)

        Consider, e. g.:

$ mkdir -- ~/builds/lynx-XXX-build 
$ cd ~/builds/lynx-XXX-build 
$ ~/src/lynx-XXX/configure … 

        This way, ~/src/lynx-XXX/configure creates config.status in
        ~/builds/lynx-XXX-build/, while ~/src/lynx-XXX remains untouched
        (and may be read-only, and used for several builds at the same

 > ./config.status --recheck # recheck what's available on your system

 > ./config.status # regenerate the files in AC_OUTPUT

        Also, --version prints the options passed to configure.

        Note that it doesn't print the relevant environment variables,
        if any were set at the time of configure.  For this reason, one
        should pass them as command line arguments to configure, like:

$ …/configure CC=gcc-4.4 … 

        instead of either of the following:

$ CC=gcc-4.4 …/configure … 

$ export CC=gcc-4.4 
$ …/configure … 

FSF associate member #7257

reply via email to

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