Date: Wed, 29 Dec 2004 02:28:21 +0100 From: girgen@FreeBSD.org To: Michel Gravey <michel.gravey@optogone.com>, freebsd-ports@freebsd.org Subject: Re: Problem with unresolved symbols in libintl.so.6 (gettext) Message-ID: <2F3392EEC0E77AE16E235E05@palle.girgensohn.se> In-Reply-To: <1ceb01c4ed3f$ea8edbd0$d601a8c0@acer> References: <1ceb01c4ed3f$ea8edbd0$d601a8c0@acer>
next in thread | previous in thread | raw e-mail | index | archive | help
stpycpy is in libc.so.5... $ nm -D /lib/libc.so.5 |grep stpcpy 0001ed60 T stpcpy So, I doubt it is gettext itself that is the problem... Sounds like the ports that don't work are linked to old libc.so.4? After 4.10->5.3 upgrade, more or less *all* ports should be rebuilt, aka portupgrade -fa... if not, your bound to get problems with different library versions, and for C++ code the mess is even worse. Are the problems just arising for not recently installed ports? /Palle --On onsdag, december 29, 2004 01.47.03 +0100 Michel Gravey <michel.gravey@optogone.com> wrote: > Hello, > > Environnement: 5.3 security branch updated from 4.10 > After a fresh upgrade of devel/gettext to latest version (0.14.1), when > trying to compile some other ports, I get the following error msg: > /usr/libexec/lib-elf.so Unresolved symbols "stpcpy" in libintl.so.6 > (try many ports which rely on gettext to compile, like netpbm or ezm3) > The bison utility was broken after the update (same error message). > A recompile did fix the problem (for bison only). > I already recompile expat2 and libiconv from ports, and fetching a > precompiled binary of gettext didn't fix the problem. > The gettext binary is maybe not the problem but it's quite annoying since > many packages rely on gettext to compile or run. An other server updated > from 4.10 to 5.3-release doesn't have the problem. > The output of nm -B /usr/local/lib/libintl.so.6 | grep stpcpy is the same > on this 2 machines (the ones with the problem and the other, same ports > tree, and updated gettext to latest version) : > U stpcpy > > If you have any ideas or suggestions... > Thanks in advance, > > Michel Gravey > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2F3392EEC0E77AE16E235E05>