Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build fails with "You must have either have gettext support in your C library, or use the GNU gettext library" #8

Open
FxPiGaAo opened this issue Aug 13, 2020 · 4 comments

Comments

@FxPiGaAo
Copy link

I encountered this error while running parsecmgmt -a build -p all:

[PARSEC] [========== Building package parsec.glib [1] ==========]
[PARSEC] [---------- Analyzing package parsec.glib ----------]
[PARSEC] parsec.glib depends on: zlib
[PARSEC] [---------- Analyzing package parsec.zlib ----------]
[PARSEC] Package parsec.zlib already exists, proceeding.
[PARSEC] [---------- Building package parsec.glib ----------]
[PARSEC] Running 'env CFLAGS=-I/home/xhc/parsec-benchmark/pkgs/libs/zlib/inst/amd64-linux.gcc/include -DPARSEC_VERSION=3.0-beta-20150206 LDFLAGS=-L/home/xhc/parsec-benchmark/pkgs/libs/zlib/inst/amd64-linux.gcc/lib /home/xhc/parsec-benchmark/pkgs/libs/glib/src/configure --disable-shared --enable-threads --with-threads=posix --build= --host= --prefix=/home/xhc/parsec-benchmark/pkgs/libs/glib/inst/amd64-linux.gcc':
checking for a BSD-compatible install... /home/xhc/parsec-benchmark/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for the BeOS... no
checking for Win32... no
checking for Mac OS X Carbon support... checking for style of include used by make... GNU
checking for gcc... /usr/bin/gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether /usr/bin/gcc accepts -g... yes
checking for /usr/bin/gcc option to accept ISO C89... none needed
checking dependency style of /usr/bin/gcc... gcc3
checking how to run the C preprocessor... /usr/bin/cpp
no
checking whether to enable garbage collector friendliness... no
checking whether to disable memory pools... no
checking for gcc... (cached) /usr/bin/gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether /usr/bin/gcc accepts -g... (cached) yes
checking for /usr/bin/gcc option to accept ISO C89... (cached) none needed
checking dependency style of /usr/bin/gcc... (cached) gcc3
checking how to run the C preprocessor... /usr/bin/cpp
checking whether we are using the GNU C++ compiler... yes
checking whether /usr/bin/g++ accepts -g... yes
checking dependency style of /usr/bin/g++... gcc3
checking for gcc... (cached) /usr/bin/gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether /usr/bin/gcc accepts -g... (cached) yes
checking for /usr/bin/gcc option to accept ISO C89... (cached) none needed
checking dependency style of /usr/bin/gcc... (cached) gcc3
checking whether /usr/bin/gcc and cc understand -c and -o together... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for pkg-config... /usr/bin/pkg-config
checking for gawk... (cached) mawk
checking for perl5... no
checking for perl... perl
checking for indent... no
checking for perl... /usr/bin/perl
checking for a Python interpreter with version >= 2.4... python
checking for python... /usr/bin/python
checking for python version... 2.7
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.7/site-packages
checking for python extension module directory... ${exec_prefix}/lib/python2.7/site-packages
checking for iconv_open... yes
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking whether we are using the GNU C Library 2.1 or newer... yes
checking Whether to cache iconv descriptors... no
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for inflate in -lz... yes
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking for LC_MESSAGES... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking for ngettext in libc... yes
checking for dgettext in libc... yes
checking for bind_textdomain_codeset... yes
checking for msgfmt... no
configure: error:
*** You must have either have gettext support in your C library, or use the
*** GNU gettext library. (http://www.gnu.org/software/gettext/gettext.html

[PARSEC] Error: 'env CFLAGS=-I/home/xhc/parsec-benchmark/pkgs/libs/zlib/inst/amd64-linux.gcc/include -DPARSEC_VERSION=3.0-beta-20150206 LDFLAGS=-L/home/xhc/parsec-benchmark/pkgs/libs/zlib/inst/amd64-linux.gcc/lib /home/xhc/parsec-benchmark/pkgs/libs/glib/src/configure --disable-shared --enable-threads --with-threads=posix --build= --host= --prefix=/home/xhc/parsec-benchmark/pkgs/libs/glib/inst/amd64-linux.gcc' failed.

I am working in ubuntu 20.04. No idea why this error happens.

@cirosantilli
Copy link
Owner

Basic question, do you have gettext installed? sudo apt install gettext.

@cirosantilli cirosantilli changed the title gtext support error build fails with "You must have either have gettext support in your C library, or use the GNU gettext library" Aug 13, 2020
@FxPiGaAo
Copy link
Author

Basic question, do you have gettext installed? sudo apt install gettext.

Yes, and my gettext version is 0.19.8.1.

@cirosantilli
Copy link
Owner

BTW, I couldn't reproduce on my Ubuntu 20.04 host. Some ideas: 1) try to find exactly how configure is checking gettext support. I think it's trying to compile a minimal executable that includes the library and makes a trivial call. Then manually run that build command yourself and try to understand what is missing. 2) try Docker to see if it can be reproduced there.

@JuliaLawall
Copy link

I have a minimal debian testing (bullseye) that does not have gettext installed. The configure script does not cause it to be installed. Compilation of vips thus fails and I have to install gettext manually. The configure script of parsec just loads a set of packages. It doesn't check for anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants