| Summary: | sys-devel/gettext-0.14.1 test fails (cannot find -lrpathy) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | nate grady <nate> |
| Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | Erik.Curtis, langthang, rhill, smithj |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
nate grady
2004-11-07 08:20:06 UTC
confirming on gettext-0.12.1-r2. (although the error is "cannot find -lrpathx", not "-lrpathy") ;). might want to change that, i almost missed this bug when searching. :) my log is a bit different, but i'm assuming that's because of the version difference. i'll include part of it for completeness sake. make check-TESTS make[3]: Entering directory `/var/tmp/portage/gettext-0.12.1-r2/work/gettext-0.12.1/autoconf-lib-link/tests' PASS: rpath-1a PASS: rpath-1b PASS: rpath-2aaa PASS: rpath-2aab PASS: rpath-2aac PASS: rpath-2aad /usr/lib/gcc/i686-pc-linux-gnu/3.4.3/../../../../i686-pc-linux-gnu/bin/ld: cannot find -lrpathx collect2: ld returned 1 exit status make[4]: *** [usey] Error 1 FAIL: rpath-2aba /usr/lib/gcc/i686-pc-linux-gnu/3.4.3/../../../../i686-pc-linux-gnu/bin/ld: cannot find -lrpathx collect2: ld returned 1 exit status make[4]: *** [usey] Error 1 FAIL: rpath-2abb PASS: rpath-2abc /usr/lib/gcc/i686-pc-linux-gnu/3.4.3/../../../../i686-pc-linux-gnu/bin/ld: cannot find -lrpathx collect2: ld returned 1 exit status make[4]: *** [usey] Error 1 FAIL: rpath-2abd PASS: rpath-2baa PASS: rpath-2bab PASS: rpath-2bac PASS: rpath-2bad PASS: rpath-2bba PASS: rpath-2bbb PASS: rpath-2bbc PASS: rpath-2bbd PASS: rpath-3aaa ...that's as far as it's gotten - it's still emerging. portage info: Portage 2.0.51-r3 (default-linux/x86/2004.3, gcc-3.4.3, glibc-2.3.4.20040808-r1, 2.6.9-ck3 i686) ================================================================= System uname: 2.6.9-ck3 i686 Pentium III (Katmai) Gentoo Base System version 1.4.16 ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.14.90.0.8-r1 Headers: sys-kernel/linux26-headers-2.6.8.1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-Os -march=pentium3 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-Os -march=pentium3 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distlocks maketest nodoc noinfo sandbox sfperms" GENTOO_MIRRORS="ftp://sunsite.ualberta.ca/pub/unix/Linux/gentoo/ ftp://gentoo.agsn.ca/ http://gentoo.mirrored.ca/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X alsa bash-completion berkdb cdr crypt divx4linux eds fortran gdbm gif gnome gnutls gstreamer gtk gtk2 gtkhtml hal imlib java jpeg libcaca matroska mmx mozilla moznoxft mpeg ncurses no_wxgtk1 nptl odbc oggvorbis opengl oss pam pcre perl pic png pwdb python quicktime readline real rtc ruby sdl sse ssl tcpd truetype unicode userlocales xml xml2 xv xvid zlib" one question: do you use LDFLAGS? they don't show up in 'emerge info'. i'm using 'Wl,-O1' my apologies, i see now that it fails to find BOTH -lrpathx and -lrpathy. sorry bout the bugspam as well. ah, here we go.. http://www.haible.de/bruno/gettext-FAQ.html#building_rpath_check ... "If only a few among the many rpath tests fail, you can probably ignore the problem. The rpath tests are sensitive to incomplete shared library support in the system, and to bugs in libtool that creates the shared libraries. Some known failures are listed in autoconf-lib-link/tests/rpath.README." ... here's what autoconf-lib-link/tests/rpath.README has to say: ... "The rpath-2* tests are sensitive to - incomplete shared library support in the system, - bugs in libtool that creates the shared libraries, - bugs in lib-link.m4. The rpath-3* tests are sensitive to - incomplete shared library support in the system, - bugs in libtool that creates the shared libraries. * On all platforms supporting shared libraries, rpath-3aae rpath-3aag rpath-3abe rpath-3abg fail. This is a libtool 1.4.2 bug: When a shared library depends on a static library indirectly through two different dependency paths, libtool attempts to link together invalid sets of object files. * OSF/1 4.0: the tests rpath-2bbd rpath-3bbd rpath-3bbf rpath-3bbg rpath-3bbh fail, because -rpath options are not cumulative: The last -rpath option overrides all previous ones. One would need to pass all directories, separated by colons, in a single -rpath option." ... so looks like there's not much we can do about it except remove maketest from make.conf. core-devs, is it possible to make a package skip the check phase even if maketest is in FEATURES? it looks like it's unfixable and therefore make check will _always_ fail and kill the emerge. i checked the configure --help and it doesn't seem to have the needed option, but i'm clueless about it so maybe there's a universal switch i don't know about. there is --disable-rpath, but i have no idea what 'do not hardcode runtime library paths' means. ;] I have the same kind of problems with 0.12.1-r2. i have a similar problem with 0.14.1
>>> Source unpacked.
* econf: updating gettext-0.14.1/config/config.guess with /usr/share/gnuconfig/config.guess
* econf: updating gettext-0.14.1/config/config.sub with /usr/share/gnuconfig/config.sub
* econf: updating gettext-0.14.1/gettext-tools/examples/hello-c++-kde/admin/config.guess with /usr/share/gnuconfig/config.guess
* econf: updating gettext-0.14.1/gettext-tools/examples/hello-c++-kde/admin/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --without-java --without-included-gettext --enable-nls
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-pc-linux-gnu-strip... no
checking for strip... strip
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
configure: creating ./config.status
config.status: creating Makefile
configure: configuring in autoconf-lib-link
configure: running /bin/sh './configure' --prefix=/usr '--prefix=/usr' '--host=i686-pc-linux-gnu' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--datadir=/usr/share' '--sysconfdir=/etc' '--localstatedir=/var/lib' '--without-java' '--without-included-gettext' '--enable-nls' 'CC=gcc' 'CFLAGS=-O2 -march=pentium-m -fomit-frame-pointer -pipe' 'CXXFLAGS=-O2 -march=pentium-m -fomit-frame-pointer -pipe' 'CXX=gcc' 'host_alias=i686-pc-linux-gnu' --cache-file=/dev/null --srcdir=.
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-pc-linux-gnu-strip... no
checking for strip... strip
checking for i686-pc-linux-gnu-gcc... gcc
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.
configure: error: /bin/sh './configure' failed for autoconf-lib-link
!!! Please attach the config.log to your bug report:
!!! /var/tmp/portage/gettext-0.14.1/work/gettext-0.14.1/config.log
!!! ERROR: sys-devel/gettext-0.14.1 failed.
!!! Function econf, Line 483, Exitcode 0
!!! econf failed
!!! If you need support, post the topmost build error, NOT this status message.
it would be good to note that i am trying to compile from stage1 for a march=pentium-m with a celeron (i don't have the M quite yet, so i wanted to get a headstart)
oh, and the file it asked me to attach didn't seem to be there seems to be a sandbox issue ... tests run outside of it took the lazy way out and disabled the sandbox for testing This is a bit confusing, this bug has been resolved as RESOLVED/FIXED, but why? On yesterdays portage tree on amd64 (about a dozen ~, but only where necessary) gettext still failed on the test. I'd suggest the the following files as solutions. Some are not quite for this bug, but would extend the options to users. Yes I know: I should make that myself. But: I can't anytime soon, and if you don't do it I won't complain. So here we go: /etc/portage/ package.features package.cflags package.cxxflags But apart from that, why has this bug been flagged as resolved by vapier? It's still there on stable amd64, so probably on stable x86 or other archs as well. Yes, there is an easy workaround. But that's not exactly what a proper bugfix is ;) Thanks for pointing out the sandbox tip tho, will try that later. damn. confirming here as well. i'm getting the same errors in the same places as my previous log above. i don't know if this was even fixed in the first place since i never happened to actually test if it worked after it was marked resolved. =P i still stand by the comment #3. there's just no possible way that this can pass on a Gentoo system IMHO. documented examples to cause gettext test failures include: - building it with --disable-nls http://lists.gnu.org/archive/html/bug-gnu-utils/2004-08/msg00074.html - having a java compiler installed on the system http://www.linuxfromscratch.org/lfs/view/development/chapter05/gettext.html - building it on a platform that supports shared libraries autoconf-lib-link/tests/rpath.README nor do i think this is a Gentoo or sandbox issue. LFS and DiY-Linux mention the test failures as well, and either ignore them or work around them in their own way. even the gettext FAQ states that some tests will fail, and advises the user to just disregard it. http://www.haible.de/bruno/gettext-FAQ.html#building_rpath_check solutions that i did see mentioned are: 1) make -C gettext-tools check. 2) cd gettext-tools; make check; cd .. both are the same thing, i know, but i don't know which would be more practical in an ebuild, or if it works at all. |
