I went back to recover from a hdd failure and am recoving from a ~July snapshot of gentoo and I still find that i'm getting the following error. emerging -U gnome-extra/gal -- (gnome-extra/gal-1.99.8) ... checking for iconv in -liconv... no checking for iconv... yes checking for gnu_get_libc_version... yes checking if iconv() handles UTF-8... no configure: error: You need to install a working iconv implementation, such as ftp://ftp.gnu.org/pub/gnu/libiconv !!! ERROR: gnome-extra/gal-1.99.8 failed. !!! Function econf, Line 324, Exitcode 1 !!! econf failed I documented the fix on bugs.gentoo.org but the report has mysteriously disappeared and the problem still exists! ...and it's a valid bug. (Are people just clearing bugs from this database without fixing them?) Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: emerge -U failure
please post the output of emerge info
i apologize if i am not somewhat correct in this, but here goes: dmt. i found the stupid solution *again* due to my stupid devotion/desire to fix something. dam me. so please fix/make note of this bug! /etc/ld.so.conf requires the following addition for iconv/gconv: /usr/lib/gconv as such, users can temporarily fix by adding the following file: /etc/env.d/06gconv LDPATH=/usr/lib/gconv (just be aware that the 06gconv is a temp file name and in no way corresponds to gentoo's configs... it is per-say, a user hack) ...interesting. i *know* i filed a report on this issue. if it didn't include a search phrase of iconv, it def included this fix notation with a word within th e fix "gconv"! arrrggghhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh! i will not spend time finding the fix again (eh.. as it's prob' hack-fixed in gentoo-1.4?)
here's emerge info anyways: Portage 2.0.49-r3 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.4.20-gaming-r3) ================================================================= System uname: 2.4.20-gaming-r3 i686 Intel(R) Pentium(R) III Mobile CPU 1000MHz ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-mcpu=pentium3 -march=pentium3 -O3 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /var/bind /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-mcpu=pentium3 -march=pentium3 -O3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="ccache autoaddcvs sandbox userpriv usersandbox fixpackages" GENTOO_MIRRORS="ftp://mirror.iawnet.sandia.gov/pub/gentoo ftp://ftp.ussg.iu.edu/pub/linux/gentoo ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo ftp://ftp.ucsb.edu/pub/mirrors/linux/gentoo/ http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="x86 oss apm avi crypt encode foomaticdb jpeg kde libg++ mad mikmod nls pdflib xml2 zlib gtkhtml gdbm berkdb slang readline arts tetex bonobo svga tcltk java guile X sdl tcpd pam libwww perl python esd imlib gnome gtk qt motif opengl alsa cdr cups dvd dvdr gif gpm gtk2 mbox mmx mozilla mpeg ncurses oggvorbis pcmcia png pnp quicktime scanner spell sse ssl sasl tiff truetype trusted usb xmms xv" I have two boxes that displayed the same error/bug. I believe both were built from stage1 (from source).
it is not 'fixed' since you are the only one seeing this problem. So unless you can figure out _why_ this happens, we can't do much with it. I don't know why it happens to you, but on a normal system this doesn't happen. Since you see it on two systems, maybe it's the install cd you used (?) Is it recent ?
i installed it from source. a stage one install. believe it was from gentoo-1.4c? however, does everybody else have a /usr/lib/gonv addition to their /etc/ld.so.conf file? if they don't, then I believe gal will fail to compile with this error.
well, I'm sorta weirded out on this as libiconv is an integral part of glibc, and where that is concerned something missing from glibc is a bad thing. can you run : qpkg -v -c -nc glibc ; and see if you have a modified glibc installation?
# qpkg -v -c -nc glibc sys-libs/glibc-2.3.2-r1 0/3004 And: qpkg -f /usr/lib/gconv sys-libs/glibc ...and it's not being list in /etc/ld.so.conf
on a normal system it doesn't have to be in ld.so.conf dunno why it happens here, but i'm afraid we can't do much about this. So unless you can find out exactly _why_ it happens for you, we're at an impasse here. Closing it as WORKSFORUS for now.
