Bug #310 openssl tests are not working
Submitted: 20 Apr 2003 19:12 Modified: 25 Apr 2003 8:44
Reporter: Alexandre Vaniachine Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Installing Severity:S3 (Non-critical)
Version:4.0.13 OS:Any (any)
Assigned to: Sergei Glukhov CPU Architecture:Any

[20 Apr 2003 19:12] Alexandre Vaniachine
The openssl test requirements files
are constructed in such a way that they can never be satisfied.
As a result the openssl_1 and openssl_2 tests are always skipped.

>MySQL support: none
>Release:	mysql-4.0.13 (Source distribution)
>C compiler:    gcc (GCC) 3.2
>C++ compiler:  gcc (GCC) 3.2
	<machine, os, target, libraries (multiple lines)>
System: Linux 12-250-131-109 2.4.18-27.7.x.cern #1 Tue Mar 18 15:08:37 CET 2003 i686 unknown
Architecture: i686

Some paths:  /usr/bin/perl /usr/bin/make /usr/bin/gmake /usr/local/gcc-alt-3.2/bin/gcc /usr/bin/cc
GCC: Reading specs from /usr/local/gcc-alt-3.2/lib/gcc-lib/i686-pc-linux-gnu/3.2/specs
Configured with: ./configure --prefix=/usr/local/gcc-alt-3.2 --enable-shared
Thread model: posix
gcc version 3.2
Compilation info: CC='gcc'  CFLAGS='-O3 -march=pentiumpro'  CXX='gcc'  CXXFLAGS='-O3 -mpentiumpro -felide-constructors -fno-exceptions -fno-rtti'  LDFLAGS=''  ASFLAGS=''

Configure command: ./configure '--prefix=/usr/local/mysql-G' '--exec-prefix=/usr/local/mysql-G' '--enable-assembler' '--with-unix-socket-path=/usr/local/mysql-G/var/mysql.sock' '--libexecdir=/usr/local/mysql-G/bin' '--with-vio' '--with-openssl' '--with-embedded-server' 'CFLAGS=-O3 -march=pentiumpro' 'CXXFLAGS=-O3 -mpentiumpro -felide-constructors -fno-exceptions -fno-rtti' 'CXX=gcc'

How to repeat:
./configure --with-vio --with-openssl
cd mysql-test
./mysql-test-run --with-openssl --skip-test=ctype_latin1_de --force

Suggested fix:
change the line in mysql-4.0/mysql-test/t/openssl_1.test

-- source include/have_openssl_1.inc 
-- source include/have_openssl.inc 

do the same for the openssl_2.test
[25 Apr 2003 8:44] Michael Widenius
Thank you for your bug report. This issue has been fixed in the latest
development tree for that product. You can find more information about
accessing our development trees at