Page MenuHome GnuPG

Assembler errors in Solaris 10 64-bit compilation
Closed, ResolvedPublic

Description

I know this topic had been discussed before, but I hope I am bringing some
insights into what exactly is happening, and a workaround (works for me ;) )

While trying to compile gnupg-1.4.7 on Sparc Solaris 10 using 64-bit gcc-3.4.6,
I run into these things:

  1. If I run plain `./configure', I get in the end: Version info: gnupg 1.4.7 Configured for: SunOS (sparc-sun-solaris2.10) Extra cpu specific functions: udiv

`make' fails as follows (in the mpi directory):
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../include -g -O2 -Wall -c _mpih-
add1.s
/usr/ccs/bin/as: "_mpih-add1.s", line 23: error: detect global register use not
covered .register pseudo-op
/usr/ccs/bin/as: "_mpih-add1.s", line 26: error: detect global register use not
covered .register pseudo-op
[SNIP]

  1. If I run `./configure --disable-asm', the error is exactly the same.
  1. If I run `./configure --disable-asm --host=sparcv9-sun-solaris2.10', I get Version info: gnupg 1.4.7 Configured for: SunOS (sparcv9-sun-solaris2.10)

(Note that there is no line with "Extra cpu specific functions..."
make' and make check' are both successful.

  1. I also tried `./configure --host=sparcv9-sun-solaris2.10' (without disabling

assembler). I get this:

              Version info:   gnupg 1.4.7
              Configured for: SunOS (sparcv9-sun-solaris2.10)
Extra cpu specific functions: udiv

`make' fails with the same error.

Conclusions:

  1. --disable-asm does not disable assembler everywhere - mpi still uses it.
  2. configure script fails to determine host type correctly and needs to be

forced using --host=sparcv9-sun-solaris2.10. Together with --disable-asm this
fixes compilation.

If you need more input, I can always reproduce the error, or run any tests.

Andy

Details

Version
1.4.7

Event Timeline

andyt added a project: Bug Report.
andyt added a subscriber: andyt.
werner added a subscriber: werner.

Did you run "make distclean" before trying with --disable-asm?
I'll check the OS detection.

Did you run "make distclean" before trying with --disable-asm?
I'll check the OS detection.

I typically do, although I cannot guarantee it after so much time...

I have tried to verify the problem right now, and I am getting these
results:

If I run `./configure', I get the same error as before.

If I run `make distclean; ./configure --disable-asm', there are no errors,
and gpg compiles smoothly as a 64-bit executables. Maybe I did forget to
run `make distclean' before. Moreover, I no longer need to specify host
type. However, there are a few changes that happened since the time I
reported the error. I do not know if they are relevant. Specifically, I
added a few GNU utilities: autoconf-2.61, automake-1.10, grep-2.5.3. If
any of these is used by configure script, it may explain the differences.

Regards,

Andy

Dr Andy Tsouladze
Sr Unix SysAdmin
United Airlines

werner claimed this task.
werner added a project: Too Old.