Re: GnuPG-1.0.7 build errors?

[Ted Cabeen <secabeen@pobox.com>]

Scott Francis <darkuncle@darkuncle.net> writes:
> note: ./configure ran normally, generating no errors, except for a complaint
> that I'm not using GNU make. I also attempted to build by specifying GNU make
> to ./configure, and using 'gmake' afterwards, but I ended up with similar
> compilation errors.
> [snip]
>                 Configured for: OpenBSD (i386-unknown-openbsd3.1)
>     Dynamically linked modules: rndunix rndegd tiger
>      Statically linked modules: rndlinux sha1 rmd160 md5
> [sfrancis@silverlight:~/tmp/gnupg-1.0.7]$ make
> [snip]
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../include     -g -O2 -Wall -c
> _mpih-lshift.s
> _mpih-lshift.s: Assembler messages:
> _mpih-lshift.s:127: Error: operands given don't match any known 386
> instruction
> _mpih-lshift.s:137: Error: operands given don't match any known 386
> instruction
> _mpih-lshift.s:141: Error: operands given don't match any known 386
> instruction

For some reason, the configure script picks the wrong set of ASM
routines when compiling for OpenBSD.  If you don't want to compile
with --without-asm, you can fix this by replacing the .s files that
are selected by configure with the .S files in the mpi/i386
directory.  Those work right, I think.  If they don't try the i586
ones.  I can't remember exactly which ones I used, but that fixed it.

-- 
Ted Cabeen           http://www.pobox.com/~secabeen            ted@impulse.net 
Check Website or Keyserver for PGP/GPG Key BA0349D2         secabeen@pobox.com
"I have taken all knowledge to be my province." -F. Bacon  secabeen@cabeen.org
"Human kind cannot bear very much reality."-T.S.Eliot        cabeen@netcom.com