Bug #2199 Problem configuring mysql 5.0.0
Submitted: 23 Dec 2003 22:56 Modified: 5 Jan 2004 8:52
Reporter: Pierre Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: Compiling Severity:S3 (Non-critical)
Version:5.0.0 OS:Linux (GNU/Linux)
Assigned to: Dean Ellis CPU Architecture:Any

[23 Dec 2003 22:56] Pierre 
Description:
[...]
checking if we should build MySQLFS... yes
checking for OpenSSL... yes
You can't use the --all-static link option when using openssl.

The problem is that I don't specified this option.

How to repeat:
configure mysql --with-openssl
[24 Dec 2003 6:17] Dean Ellis 
Are you using our build scripts (in the BUILD/ directory)?  Some of these do pass this option (the ones which pass $static_link in extra_configs).
[24 Dec 2003 16:43] Pierre 
No, I'm using configure.
[26 Dec 2003 9:37] Dean Ellis 
I cannot repeat this with the latest 5.0 sources (bitkeeper tree) unless I do explicitly pass --with-mysqld-ldflags=-all-static or --with-client-ldflags=-all-static or use one of the build scripts which set it.

Perhaps a cached configure option?
[1 Jan 2004 17:42] Pierre 
Maybe, how can I know ?
[2 Jan 2004 6:10] Dean Ellis 
Just remove config.cache before running configure.
[3 Jan 2004 19:21] Pierre 
There isn't any config.cache file in the root of the source tree.
I just untar and configure and got this.
[5 Jan 2004 8:52] Dean Ellis 
The only thing I see that might force this is the use of libpstack.  Check your configure output to see what "checking if we should use pstack..." reports, and try --without-pstack.

If none of this is tracking down the problem, please attach your configure output via the Files tab here so I can see what your system is doing.
[6 Jan 2004 5:04] Pierre 
I uses the --with-pstack option with configure,
but the corresponding output is :

checking if we should use pstack... no

Without this option this doesn't fail anymore.
Very strange.