From owner-freebsd-current@FreeBSD.ORG Sun Jan 30 00:08:48 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AFA99106564A; Sun, 30 Jan 2011 00:08:48 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 495A58FC17; Sun, 30 Jan 2011 00:08:48 +0000 (UTC) Received: by qyk36 with SMTP id 36so4313678qyk.13 for ; Sat, 29 Jan 2011 16:08:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:date:from:to:cc:subject:message-id:in-reply-to :references:x-mailer:mime-version:content-type; bh=VGCCrbrEBvV5mpbz1GprH9Qd1ReilFwMPnyskmAR4LE=; b=MPlAmEufNHmm54g7HXY2BdjxvWxbZQ8S+MPHmlNsiuXpyn6HFIUypUNRCXNAhDfu/A NNxfqBEZM7q9f7loiMNJgTp8uKsLfEt3Sdb7xhwqcgFmreNrfNS/QdYNXTwN86D/tqB9 yLWiKfxuc9WxTdEeFIod47JTPwVswTVLdI76s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type; b=A7UHLHL/rciFlGZRs0OCzpwp0TUrMKvOUxlIK+htPIFDreYODq6jNAN6QKcIVw75lU BNnBc5ql9v9sx549/ZxO202ZetWKIfJBaksH0xo8l0AnNSP6OIcSpa2xb+kuvqTveVQ1 RLZQ/u9iS1LtZyzLy7aiZ1h77QrdfpEq+8MCU= Received: by 10.224.11.70 with SMTP id s6mr4661190qas.198.1296346126261; Sat, 29 Jan 2011 16:08:46 -0800 (PST) Received: from kan.dnsalias.net (c-24-63-226-98.hsd1.ma.comcast.net [24.63.226.98]) by mx.google.com with ESMTPS id w12sm12599197qco.20.2011.01.29.16.08.44 (version=SSLv3 cipher=RC4-MD5); Sat, 29 Jan 2011 16:08:45 -0800 (PST) Date: Sat, 29 Jan 2011 19:08:39 -0500 From: Alexander Kabaev To: Alexey Shuvaev Message-ID: <20110129190839.38b6e8da@kan.dnsalias.net> In-Reply-To: <20110129202012.GA61135@lexx.ifp.tuwien.ac.at> References: <20110129202012.GA61135@lexx.ifp.tuwien.ac.at> X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/u1O1gzAK6a=EU1Mge5VdG6C"; protocol="application/pgp-signature" Cc: freebsd-gecko@FreeBSD.org, freebsd-ports@freebsd.org, freebsd-current@freebsd.org Subject: Re: [WORKAROUND] www/seamonkey2 on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Jan 2011 00:08:48 -0000 --Sig_/u1O1gzAK6a=EU1Mge5VdG6C Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 29 Jan 2011 21:20:12 +0100 Alexey Shuvaev wrote: > On Fri, Jan 28, 2011 at 05:37:51PM -0800, Garrett Cooper wrote: > > On Fri, Jan 28, 2011 at 3:58 PM, 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 ..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 > > ls /usr/local/lib/libiconv*so* ? > > > ~> ll /usr/local/lib/libiconv*so* > lrwxr-xr-x 1 root wheel 13 Jan 27 > 13:14 /usr/local/lib/libiconv.so -> libiconv.so.3 -r--r--r-- 1 root > wheel 1078567 Jan 27 13:14 /usr/local/lib/libiconv.so.3 >=20 > I'm not so lame :) >=20 > On Sat, Jan 29, 2011 at 01:39:15PM -0500, Alexander Kabaev wrote: > > On Sat, 29 Jan 2011 13:21:44 -0500 > > Alexander Kabaev wrote: > >=20 > > > On Sat, 29 Jan 2011 13:02:24 -0500 (EST) > > > Daniel Eischen wrote: > > >=20 > > > > 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 > > >=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. > > >=20 > > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D20218 > > > --=20 > > > Alexander Kabaev > >=20 > > Follow-up to myself: Nope, the fix to said bug appears in our > > compiler. Can you make amd64 version of nsNativeCharsetUtils. > > --=20 > > Alexander Kabaev > > > ??? (It is already on amd64) Email was sent while not finished. Can you make amd64 version of nsNativeCharsetUtils.o available from somewhere along with corresponding .ii file? To get .ii file you can add -save-temps to GCC invocation used to compile nsNativeCharsetUtils.cpp. --=20 Alexander Kabaev --Sig_/u1O1gzAK6a=EU1Mge5VdG6C Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iD8DBQFNRKwLQ6z1jMm+XZYRAmPMAKDDOAOjbyY9ZfKNTQ5LH8ztCnx+igCg2vtG MhbwU0awgx6qUX1fKR7kkkc= =qC2f -----END PGP SIGNATURE----- --Sig_/u1O1gzAK6a=EU1Mge5VdG6C--