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 ...?
mark
On 08/03/11 10:39 AM, m.roth@5-cent.us 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 ...?
/path/to/pg_config --configure
On 08/03/11 10:49 AM, John R Pierce wrote:
On 08/03/11 10:39 AM,m.roth@5-cent.us 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 ...?
/path/to/pg_config --configure
oh geez, ignore me, I was on the postgresql list moments earlier and blurred them together in my mind.
John R Pierce wrote:
On 08/03/11 10:49 AM, John R Pierce wrote:
On 08/03/11 10:39 AM,m.roth@5-cent.us 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 ...?
/path/to/pg_config --configure
oh geez, ignore me, I was on the postgresql list moments earlier and blurred them together in my mind.
Ok. Thanks for making that clear - I was wondering.
mark
On Wed, 3 Aug 2011, John R Pierce wrote:
To: centos@centos.org From: John R Pierce pierce@hogranch.com Subject: Re: [CentOS] configure
On 08/03/11 10:49 AM, John R Pierce wrote:
On 08/03/11 10:39 AM,m.roth@5-cent.us 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 ...?
/path/to/pg_config --configure
oh geez, ignore me, I was on the postgresql list moments earlier and blurred them together in my mind.
LOL! I did wonder about that John.
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] -----------------------------------------------------------------
At Wed, 3 Aug 2011 13:39:03 -0400 CentOS mailing list centos@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.
mark
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Robert Heller wrote:
At Wed, 3 Aug 2011 13:39:03 -0400 CentOS mailing list centos@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.
*bing*
Thank you, very much. Now I can document it, and try it in an alternate version. I've been working to get a newer (5.4+) version of openssh built for CentOS 6.0, because we have to be able to use US gov't PIV-II cards. My manager built a version for 5.5 that we've used for 5.6, but he wasn't remembering the options he'd used.
mark
On Wed, 3 Aug 2011, Robert Heller wrote:
To: CentOS mailing list centos@centos.org From: Robert Heller heller@deepsoft.com Subject: Re: [CentOS] configure
At Wed, 3 Aug 2011 13:39:03 -0400 CentOS mailing list centos@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] -----------------------------------------------------------------