[CentOS] configure

[Keith Roberts]

On Wed, 3 Aug 2011, Robert Heller wrote:

> To: CentOS mailing list <centos at centos.org>
> From: Robert Heller <heller at deepsoft.com>
> Subject: Re: [CentOS] configure
> 
> At Wed, 3 Aug 2011 13:39:03 -0400 CentOS mailing list <centos at centos.org> wrote:
>
>>
>> Does anyone know, or have a link, to something that can tell me how to
>> find out exactly what options a ./configure was run with? Is there
>> something in configure.ac, or the Makefile, or ...?
>
> Look in config.log and config.status.
>
> In fact, running ./config.status will rerun ./configure with the same
> options ./configure was originally run with and running './config.status
> --version' will tell you just what options were used.

On php 5.2.5 this is the contents of .config.nice in the 
main source dir:

#! /bin/sh
#
# Created by configure

'./configure' \
'--with-apxs2=/usr/local/apache-2.2.6/bin/apxs' \
'--prefix=/usr/local/php-5.2.5' \
'--bindir=/usr/local/bin' \
'--enable-shared=all' \ 
'--without-pear' \
'--with-mysql=shared' \
'--with-mysql-sock=/var/lib/databases/mysql/mysql.sock' \
'--with-mysqli=shared' \
'--with-pgsql=/usr/local/postgresql-8.2.5/bin' \
'--with-xsl' \
'--with-zlib-dir=/usr/include' \
'--with-readline' \
"$@"

The above can be run as an option to the ./configure 
command, IIRC. Saves typing it all in on the command line.

IIRC there's also another option to reuse the results of 
the last ./configure run - so you don't have to keep on 
doing the ./configure step.

.config.cache

# This file is a shell script that caches the results of 
configure
# tests run on this system so they can be shared between 
configure
# scripts and configure runs.  It is not useful on other 
systems.
# If it contains results you don't want to keep, you may 
remove or edit it. #
# By default, configure uses ./config.cache as the cache 
file,
# creating it if it does not exist already.  You can give 
configure
# the --cache-file=FILE option to use a different cache 
file; that is
# what configure does when it calls configure scripts in 
# subdirectories, so they share the cache.
# Giving --cache-file=/dev/null disables caching, for 
debugging configure.
# config.status only pays attention to the cache file if you 
give it the
# --recheck option to rerun configure.

Kind Regards,

Keith

-----------------------------------------------------------------
Websites:
http://www.karsites.net
http://www.php-debuggers.net
http://www.raised-from-the-dead.org.uk

All email addresses are challenge-response protected with
TMDA [http://tmda.net]
-----------------------------------------------------------------