Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 29 Jan 2011 13:21:44 -0500
From:      Alexander Kabaev <kabaev@gmail.com>
To:        Daniel Eischen <deischen@freebsd.org>
Cc:        Alexey Shuvaev <shuvaev@physik.uni-wuerzburg.de>, gecko@freebsd.org, freebsd-current@freebsd.org, freebsd-ports@freebsd.org
Subject:   Re: [WORKAROUND] www/seamonkey2 on CURRENT
Message-ID:  <20110129132144.57c42924@kan.dnsalias.net>
In-Reply-To: <Pine.GSO.4.64.1101291247330.16942@sea.ntplx.net>
References:  <20110128235851.GB95980@lexx.ifp.tuwien.ac.at> <Pine.GSO.4.64.1101291247330.16942@sea.ntplx.net>

next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/t/awCm+FPVGD0Ib2HyUw6MH
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Sat, 29 Jan 2011 13:02:24 -0500 (EST)
Daniel Eischen <deischen@freebsd.org> wrote:

> On Sat, 29 Jan 2011, Alexey Shuvaev wrote:
>=20
> > 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.
>=20
> Yes, I had this problem also on -current.  Does seamonkey build
> on recent 8.x?
>=20
> 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.
>=20

My wild guess: seamonkey tries to hide symbols that are coming from
different .o file (this time one from libiconv.a) and that fails with
our toolchain.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D20218
--=20
Alexander Kabaev

--Sig_/t/awCm+FPVGD0Ib2HyUw6MH
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (FreeBSD)

iD8DBQFNRFq9Q6z1jMm+XZYRAobmAJwNgHvAe0S7dDry3nXlLn14cCHV/gCfZULY
oMsEz+uk3NjG8tvJfj0rhcI=
=D59k
-----END PGP SIGNATURE-----

--Sig_/t/awCm+FPVGD0Ib2HyUw6MH--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110129132144.57c42924>