mumps @5.0.1: /opt/local/include/parmetis.h:33:4: error: "Incorrect user-supplied value fo IDXTYPEWIDTH"

[lnmaurer (Leon Nathaniel Maurer)]

I failed to install mumps on OS X 10.11.6 with Xcode 8.2.1. I've attached the log file for details. The terminal output is below.

$ sudo port install mumps
Password:
--->  Computing dependencies for mumps
--->  Fetching archive for mumps
--->  Attempting to fetch mumps-5.0.1_0+accelerate+gfortran+mpich.darwin_15.noarch.tbz2 from https://packages.macports.org/mumps
--->  Attempting to fetch mumps-5.0.1_0+accelerate+gfortran+mpich.darwin_15.noarch.tbz2 from http://fco.it.packages.macports.org/mirrors/macports-packages/mumps
--->  Attempting to fetch mumps-5.0.1_0+accelerate+gfortran+mpich.darwin_15.noarch.tbz2 from http://her.gr.packages.macports.org/mumps
--->  Fetching distfiles for mumps
--->  Verifying checksums for mumps
--->  Extracting mumps
--->  Applying patches to mumps
--->  Configuring mumps
--->  Building mumps
Error: Failed to build mumps: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_mumps/mumps/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port mumps failed

[lnmaurer (Leon Nathaniel Maurer)]

Log file from failed build.

[seanfarley (Sean Farley)]

Hmmm, I wasn't able to reproduce this. Do you have any conflicting header files in /usr/local?

[lnmaurer (Leon Nathaniel Maurer)]

I'm not sure if I have any conflicting header files in /user/local . How would I find out?

[mf2k (Frank Schima)]

See wiki:FAQ#usrlocal.

[lnmaurer (Leon Nathaniel Maurer)]

Building in trace mode didn't help.

There's really not much in my /usr/local folder. I don't see any header files at all. FWIW, here are the libraries:

$ find /usr/local/ -name *.h
$ ls /usr/local/lib
IDPrimePKCS11			libconnectionsclient.a		libpersonalfirewall.a		pcsc
libappfirewall.a		libecomlodr.dylib		libsymsea.1.1.0.dylib		pkcs11
libautoblock.a			libidprimepkcs11.0.dylib	libsymsea.dylib
libautosetup.a			liblocationawareness.a		libtrustedcomponents.a

Do you think any of those would cause the problem?

[seanfarley (Sean Farley)]

I guess we need to grep your system for where IDXTYPEWIDTH is being defined :-/

[lnmaurer (Leon Nathaniel Maurer)]

So, here's what a search of /opt reveals:

$ sudo find /opt -type f -exec sudo fgrep -n -H IDXTYPEWIDTH {} \;
Password:
/opt/local/include/metis.h.mp_1474311426:37:#define IDXTYPEWIDTH 64
/opt/local/include/metis.h.mp_1474311426:39:#define IDXTYPEWIDTH 32
/opt/local/include/metis.h.mp_1474311426:102:#if IDXTYPEWIDTH == 32
/opt/local/include/metis.h.mp_1474311426:113:#elif IDXTYPEWIDTH == 64
/opt/local/include/metis.h.mp_1474311426:129:  #error "Incorrect user-supplied value fo IDXTYPEWIDTH"
/opt/local/include/parmetis.h:24:#if IDXTYPEWIDTH == 32
/opt/local/include/parmetis.h:28:#elif IDXTYPEWIDTH == 64
/opt/local/include/parmetis.h:33:  #error "Incorrect user-supplied value fo IDXTYPEWIDTH"
/opt/local/var/macports/sources/distfiles.macports.org/ports/math/metis/files/cmake64.patch:49:-   elementary data type used in METIS. This is controled by the IDXTYPEWIDTH
/opt/local/var/macports/sources/distfiles.macports.org/ports/math/metis/files/cmake64.patch:162:-#define IDXTYPEWIDTH 32
/opt/local/var/macports/sources/distfiles.macports.org/ports/math/metis/files/cmake64.patch:217:-#if IDXTYPEWIDTH == 32
/opt/local/var/macports/sources/distfiles.macports.org/ports/math/metis/files/cmake64.patch:228:-#elif IDXTYPEWIDTH == 64
/opt/local/var/macports/sources/distfiles.macports.org/ports/math/metis/files/cmake64.patch:244:-  #error "Incorrect user-supplied value fo IDXTYPEWIDTH"
/opt/local/var/macports/sources/distfiles.macports.org/ports/math/metis/files/cmake64.patch:520:+#define IDXTYPEWIDTH 64
/opt/local/var/macports/sources/distfiles.macports.org/ports/math/metis/files/cmake64.patch:522:+#define IDXTYPEWIDTH 32
/opt/local/var/macports/sources/distfiles.macports.org/ports/math/metis/files/cmake64.patch:585:+#if IDXTYPEWIDTH == 32
/opt/local/var/macports/sources/distfiles.macports.org/ports/math/metis/files/cmake64.patch:596:+#elif IDXTYPEWIDTH == 64
/opt/local/var/macports/sources/distfiles.macports.org/ports/math/metis/files/cmake64.patch:612:+  #error "Incorrect user-supplied value fo IDXTYPEWIDTH"
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/math/metis/files/cmake64.patch:49:-   elementary data type used in METIS. This is controled by the IDXTYPEWIDTH
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/math/metis/files/cmake64.patch:162:-#define IDXTYPEWIDTH 32
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/math/metis/files/cmake64.patch:217:-#if IDXTYPEWIDTH == 32
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/math/metis/files/cmake64.patch:228:-#elif IDXTYPEWIDTH == 64
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/math/metis/files/cmake64.patch:244:-  #error "Incorrect user-supplied value fo IDXTYPEWIDTH"
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/math/metis/files/cmake64.patch:520:+#define IDXTYPEWIDTH 64
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/math/metis/files/cmake64.patch:522:+#define IDXTYPEWIDTH 32
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/math/metis/files/cmake64.patch:585:+#if IDXTYPEWIDTH == 32
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/math/metis/files/cmake64.patch:596:+#elif IDXTYPEWIDTH == 64
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/math/metis/files/cmake64.patch:612:+  #error "Incorrect user-supplied value fo IDXTYPEWIDTH"
Binary file /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports.tar matches

A similar search found nothing in /usr.

[lnmaurer (Leon Nathaniel Maurer)]

Well, I uninstalled my copies of metis and parmetis and tried installing mumps again (which installs metis and parmetis in the process), and everything worked. I'm not sure what to make of it. FWIW, I previously manually installed metis and parmetis before installing mumps, so maybe the order of installation matters? If not, maybe this was all just a fluke.

[seanfarley (Sean Farley)]

Glad it works! It seems you had a manual install of metis at one point since you have a file called /opt/local/include/metis.h.mp_1474311426. Uninstalling / reinstalling would seem to have fixed that. Closing ticket now.