Closed Tom-python0121 closed 3 years ago
You are probably missing libiconv or something.
Anyway, this is really a distro packaging issue and 2.6.23 is ancient history.
@jstedfast There's a dependency on this package, or it's a failure.
[root@centos8 ~]# spack spec gmime
Input spec
--------------------------------
gmime
Concretized
--------------------------------
gmime@2.6.23%gcc@8.4.1 arch=linux-centos8-aarch64
^glib@2.66.7%gcc@8.4.1~libmount patches=b3fd45063a19c871048aa1f28692293ab8971a871bdcbe65f06f17fdd79db9e2 tracing=none arch=linux-centos8-aarch64
^gettext@0.21%gcc@8.4.1+bzip2+curses+git~libunistring+libxml2+tar+xz arch=linux-centos8-aarch64
^bzip2@1.0.8%gcc@8.4.1+shared arch=linux-centos8-aarch64
^diffutils@3.7%gcc@8.4.1 arch=linux-centos8-aarch64
^libiconv@1.16%gcc@8.4.1 arch=linux-centos8-aarch64
^libxml2@2.9.10%gcc@8.4.1~python arch=linux-centos8-aarch64
^pkgconf@1.7.3%gcc@8.4.1 arch=linux-centos8-aarch64
^xz@5.2.5%gcc@8.4.1~pic arch=linux-centos8-aarch64
^zlib@1.2.11%gcc@8.4.1+optimize+pic+shared arch=linux-centos8-aarch64
^ncurses@6.2%gcc@8.4.1~symlinks+termlib arch=linux-centos8-aarch64
^tar@1.32%gcc@8.4.1 arch=linux-centos8-aarch64
^libffi@3.3%gcc@8.4.1 patches=26f26c6f29a7ce9bf370ad3ab2610f99365b4bdd7b82e7c31df41a3370d685c0 arch=linux-centos8-aarch64
^meson@0.57.1%gcc@8.4.1 arch=linux-centos8-aarch64
^ninja@1.10.2%gcc@8.4.1 arch=linux-centos8-aarch64
^python@3.8.8%gcc@8.4.1+bz2+ctypes+dbm~debug+libxml2+lzma~nis~optimizations+pic+pyexpat+pythoncmd+readline+shared+sqlite3+ssl~tix~tkinter~ucs4+uuid+zlib patches=0d98e93189bc278fbc37a50ed7f183bd8aaf249a8e1670a465f0db6bb4f8cf87 arch=linux-centos8-aarch64
^expat@2.2.10%gcc@8.4.1+libbsd arch=linux-centos8-aarch64
^libbsd@0.10.0%gcc@8.4.1 arch=linux-centos8-aarch64
^gdbm@1.18.1%gcc@8.4.1 arch=linux-centos8-aarch64
^readline@8.0%gcc@8.4.1 arch=linux-centos8-aarch64
^openssl@1.1.1j%gcc@8.4.1~docs+systemcerts arch=linux-centos8-aarch64
^perl@5.32.1%gcc@8.4.1+cpanm+shared+threads arch=linux-centos8-aarch64
^berkeley-db@18.1.40%gcc@8.4.1~docs patches=b231fcc4d5cff05e5c3a4814f6a5af0e9a966428dc2176540d2c05aff41de522 arch=linux-centos8-aarch64
^sqlite@3.34.0%gcc@8.4.1+column_metadata+fts~functions~rtree arch=linux-centos8-aarch64
^util-linux-uuid@2.36%gcc@8.4.1 arch=linux-centos8-aarch64
^py-setuptools@50.3.2%gcc@8.4.1 arch=linux-centos8-aarch64
^pcre@8.44%gcc@8.4.1~jit+multibyte+utf arch=linux-centos8-aarch64
^libgpg-error@1.37%gcc@8.4.1 arch=linux-centos8-aarch64
^gawk@5.1.0%gcc@8.4.1 arch=linux-centos8-aarch64
^gmp@6.1.2%gcc@8.4.1 arch=linux-centos8-aarch64
^autoconf@2.69%gcc@8.4.1 arch=linux-centos8-aarch64
^m4@1.4.18%gcc@8.4.1+sigsegv patches=3877ab548f88597ab2327a2230ee048d2d07ace1062efe81fc92e91b7f39cd00,fc9b61654a3ba1a8d6cd78ce087e7c96366c290bc8d2c299f09828d793b853c8 arch=linux-centos8-aarch64
^libsigsegv@2.12%gcc@8.4.1 arch=linux-centos8-aarch64
^automake@1.16.3%gcc@8.4.1 arch=linux-centos8-aarch64
^libtool@2.4.6%gcc@8.4.1 arch=linux-centos8-aarch64
^mpfr@4.0.2%gcc@8.4.1 patches=3f80b836948aa96f8d1cb9cc7f3f55973f19285482a96f9a4e1623d460bcccf0 arch=linux-centos8-aarch64
^autoconf-archive@2019.01.06%gcc@8.4.1 arch=linux-centos8-aarch64
I guess check if the configure script is correctly detecting libiconv's installed location?
You might also have to fix up the configure script. I'm not sure. I don't have Centos so it's hard for me to help you.
You might have a native libiconv and the gnu-iconv package and that might be confusing the configure script - it might be getting the CFLAGS wrong or the CFLAGS might include both include dirs, causing the iconv_open() macro to point to the wrong libiconv_open() method call.
I meet a problem:spack install --keep-stage -v gmime@2.6.23 failed in centos8.
Steps to reproduce the issue
Can you help me out?
Information on your system
[root@centos8 ~]# spack debug report