4.3.1 test failures on alphaev56-dec-osf4.0g (Tru64)

[Torbjorn Granlund]

[Sorry for replying somewhat slowly, I am mainly vacationing in this
period.]

"Daniel Richard G." <skunk at iSKUNK.ORG> writes:

  Okay, so -DNO_ASM is supposed to appear in CPPFLAGS after specifying
  --host=none. Looking at the configure script in the GMP 4.3.1
  distribution, I added a couple of statements to print out the value of
  $cppflags/$CPPFLAGS after lines 3875 and 6454 (marked with "1>" and "2>"
  below, respectively):

  ----8<----
  checking for none-strip... no
  checking for strip... strip
  checking whether to enable maintainer-specific portions of Makefiles...
  no
  checking ABI=long
  1> cppflags = -DNO_ASM
  checking compiler none-gcc -O2 -pedantic -DNO_ASM... no
  1> cppflags = -DNO_ASM
  checking compiler gcc -O2 -pedantic -DNO_ASM... no
  1> cppflags = 
  checking compiler none-cc -O ... no
  1> cppflags = 
  checking compiler cc -O ... yes
  2> CPPFLAGS = 
  checking for none-gcc... cc
  checking for C compiler default output file name... a.out
  checking whether the C compiler works... yes
  checking whether we are cross compiling... no
  ---->8----

  It seems that the NO_ASM definition is dependent on the choice of
  compiler. Shouldn't it be unconditional?

I think it might be even more confused than that, actually.  :-)

What do we actually want --host=none to mean?  Clearly, it should avoid
the host specific code in mpn/CPUFAMILY.  This is accomplished by
configure's playing with the various path variables.  Then longlong.h
should have LONGLONG_STANDALONE defined, else it might make references
that need mpn/CPUFAMILY.  NO_ASM is meant to be something different,
which might do strictly more switching-off than LONGLONG_STANDALONE, but
not necessarily so.

I suppose this should be fixed in different ways depending on whether we
want --host=none to use (standalone) assembly code from longlong.h or
not.

Perhaps we should use more pedestrian mechanisms for disabling
mpn/CPUFAMILY, like --disable-assembly and for also disabling
longlong.h, --disable-all-assembly?  --host=none is a little strange.

  I'd be happy to provide any further information on this, as well as test
  potential fixes.

There will be no potential fixes for the FAILures before somebody with
access debugs it.  How about you?

-- 
Torbjörn