I deleted /bin/sh, and linked /bin/bash to /bin/sh, and then re-ran the
entire installation in a new directory.
The results are not quite the same. The .libs directory is now created,
but it is empty and assert.o and the rest of the programs listed below
still have the Oct 11 2021 date and only exist in the root directory
(/tmp/gmp621).
Let me know if you need the new config and make logs.
Jack
o rand/.libs/randmt.o rand/.libs/randmts.o rand/.libs/rands.o
rand/.libs/randsd.
o rand/.libs/randsdui.o rand/.libs/randbui.o rand/.libs/randmui.o
-m32 -m32
-Wl,-soname -Wl,libgmp.so.14 -o .libs/libgmp.so.14
gcc: error: .libs/assert.o: No such file or directory
gcc: error: .libs/compat.o: No such file or directory
gcc: error: .libs/errno.o: No such file or directory
gcc: error: .libs/extract-dbl.o: No such file or directory
gcc: error: .libs/invalid.o: No such file or directory
gcc: error: .libs/memory.o: No such file or directory
gcc: error: .libs/mp_bpl.o: No such file or directory
gcc: error: .libs/mp_clz_tab.o: No such file or directory
gcc: error: .libs/mp_dv_tab.o: No such file or directory
gcc: error: .libs/mp_minv_tab.o: No such file or directory
gcc: error: .libs/mp_get_fns.o: No such file or directory
gcc: error: .libs/mp_set_fns.o: No such file or directory
gcc: error: .libs/version.o: No such file or directory
gcc: error: .libs/nextprime.o: No such file or directory
gcc: error: .libs/primesieve.o: No such file or directory
gcc: error: .libs/tal-reent.o: No such file or directory
make[2]: *** [libgmp.la] Error 1
make[2]: Leaving directory `/tmp/gmp621'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/gmp621'
make: *** [all] Error 2
unix:/tmp/gmp621#
On 2/3/22 15:54, Niels Möller wrote:
> Torbjörn Granlund writes:
>
>> Marco Bodrato writes:
>>
>>==> /tmp/config.guess.log <==
>>./config.guess: syntax error at line 284: `(' unexpected
>>
>> Perhaps the $(command ...) syntax is not known by the old SCO shell?
>> Really old /bin/sh only had `command ...`.
> I take it this is gmp's config.guess (not the plain autoconf/gnulib
> version, which is configfsf.guess in gmp)?
>
> Autoconf is usually very careful about problems with old and obscure
> variants of /bin/sh, but perhaps gmp's shell scripts are not.
>
> I think the autoconf configure script has a CONFIG_SHELL environment,
> maybe it would work better to install, e.g., bash, and set
> CONFIG_SHELL=/usr/bin/bash (that's a feature I've never had to use)?
>
> Regards,
> /Niels
>
___
gmp-bugs mailing list
gmp-bugs@gmplib.org
https://gmplib.org/mailman/listinfo/gmp-bugs
