On 03/02/18 23:48, Paulo Moura wrote: > Hi, > >> On 3 Feb 2018, at 19:42, Joachim Schimpf <jschimpf_at_...311...> wrote: >> >> On 03/02/18 15:26, Paulo Moura wrote: >>> Hi, >>> I'm trying to build 7.0#37 from sources on macOS 10.13.3 (High Sierra): >> ... >>> unimplemented functionality in integer_list(9007474139725823, 31, _404977) >> >> This is caused by building without bignum support (GMP or MPIR library): >> the compiler can then not process clauses with too many environment variables. >> >> >> The current configure script will look for gmp/mpir in >> >> $ECLIPSETHIRDPARTY/{gmp4.2,gmp4.1,mpir1.3.1}/$ECLIPSEARCH/{lib,include} > > Why such a odd location for third-party software? macOS users usually use either MacPorts or Homebrew for installing third-party software like GMP. MacPorts install on /opt/local. Homebrew install on /usr/local. I use MacPorts and tried several variants: > > export ECLIPSETHIRDPARTY=/opt/local > export ECLIPSETHIRDPARTY=/opt/local/lib > export ECLIPSETHIRDPARTY=/opt/local/include > > each after a make -f Makefile.$ECLIPSEARCH clean but got the same errors. ECLIPSETHIRDPARTY is a directory structure you set up yourself. It has a fixed structure, independent of operating system whims: useful for cross-compilation (where we can't configure) and for cases where configure doesn't do the right thing. > I'm also at: > > $ port info gmp > gmp _at_6.1.2_1 (devel, math) > > Are the old 4.1/4.2 versions required? No -- as long as gmp sticks to its APIs. > >> or, failing this, try to use a system-wide installed one by linking with -lgmp > > How exactly? Well, you tell me! How _do_ you link something with gmp on macOS? Apparently our configure check AC_CHECK_LIB(gmp, __gmpz_import) fails... -- JoachimReceived on Sun Feb 04 2018 - 01:38:28 CET
This archive was generated by hypermail 2.3.0 : Tue Apr 16 2024 - 09:13:20 CEST