Date: Sat, 29 Jan 2011 13:02:24 -0500 (EST) From: Daniel Eischen <deischen@freebsd.org> To: Alexey Shuvaev <shuvaev@physik.uni-wuerzburg.de> Cc: gecko@freebsd.org, freebsd-current@freebsd.org, freebsd-ports@freebsd.org Subject: Re: [WORKAROUND] www/seamonkey2 on CURRENT Message-ID: <Pine.GSO.4.64.1101291247330.16942@sea.ntplx.net> In-Reply-To: <20110128235851.GB95980@lexx.ifp.tuwien.ac.at> References: <20110128235851.GB95980@lexx.ifp.tuwien.ac.at>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 29 Jan 2011, Alexey Shuvaev wrote: > Hello! > > It seems www/seamonkey2 is broken on CURRENT for at least 1 month now [1]. > Examining build log and reproducing it locally, the problem is in the > usage of libiconv in nsNativeCharsetUtils.cpp. The linker fails to > produce libxpcom_core.so although -L/usr/local/lib and -liconv > are specified [2]. Examining this further I found that nsNativeCharsetUtils.o > produced with [3] fails to link with libiconv alone too [4] (note > still unresolved libiconv references). > I'm not a compiler/linker guru and do not understand what is happening > here. As a workaroud I use the attached patch which disables the usage > of libiconv in nsNativeCharsetUtils.cpp. Yes, I had this problem also on -current. Does seamonkey build on recent 8.x? libxpcomio_s.a is a static library that has unresolved references to libiconv. I guess I'd expect those references to be resolved with a later -L/usr/local/lib -liconv when building the shared library (libxpcom_core.so), but they are not. -- DE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.1101291247330.16942>