gnupgp-1.2.3 (et al) build workarounds for OpenBSD 3.2 and IBM AIX 4.x

[David Shaw]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Oct 06, 2003 at 10:01:34AM -0600, Nelson H. F. Beebe wrote:
> Builds of gnupgp-1.2.3 (and other nearby releases) fail on OpenBSD 3.2
> and IBM AIX 4.[23] because of incompatible assembly code in the mpi
> subdirectory.
> 
> With OpenBSD 3.2 on Intel IA-32, I got builds to succeed and all tests
> to pass using
> 
> 	env CC=gcc CXX=g++ LDFLAGS=-Wl,-rpath,/usr/local/lib ./configure --disable-asm
> 	make all check
> 
> Without the --disable-asm, there are link failures because of
> confusion over leading underscores in external names:
> 
> 	gcc  -g -O2 -Wall  -Wl,-rpath,/usr/local/lib -o mpicalc  mpicalc.o \
> 		../cipher/libcipher.a ../mpi/libmpi.a ../util/libutil.a ../intl/libintl.a
> 	mpi-inline.h:119: Undefined symbol `_mpihelp_sub_n' referenced from text segment
> 	mpi-add.c:143: Undefined symbol `_mpihelp_sub_n' referenced from text segment
> 	mpi-add.c:136: Undefined symbol `_mpihelp_sub_n' referenced from text segment
> 	...many many more...

In the main GnuPG build directory, what does
"grep underscore config.log" return?

Try building with the opposite value (i.e. if
ac_cv_sys_symbol_underscore=no, build with
"./configure ac_cv_sys_symbol_underscore=yes")

David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.3-cvs (GNU/Linux)
Comment: Key available at http://www.jabberwocky.com/david/keys.asc

iHEEARECADEFAj+CqMMqGGh0dHA6Ly93d3cuamFiYmVyd29ja3kuY29tL2Rhdmlk
L2tleXMuYXNjAAoJEOJmXIdJ4cvJ/LEAn3nIWD2y2djqVjTUkTYSWh7FGIhKAKC7
oowvAMQRTDKza02Xr209prbk2A==
=uXUu
-----END PGP SIGNATURE-----