From owner-freebsd-current@FreeBSD.ORG Sat Jan 29 18:39:28 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 3D873106566B; Sat, 29 Jan 2011 18:39:28 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id BB9CB8FC12; Sat, 29 Jan 2011 18:39:27 +0000 (UTC) Received: by qyk8 with SMTP id 8so1727948qyk.13 for ; Sat, 29 Jan 2011 10:39:26 -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=bM0AEks10hWMA0XJB7WBBGA5zO6HEBB9DaujaE7KnmU=; b=H9OeR8s5IO0pOhDipvHF95RNHGioDewWSft8hrRso5EJnvFL3W8xBh2uswMgviWoqC a0XGEWw4fe0o/fi3ccd/KlXsV0q282Qfb9TTdxFPaaloktsGa0fSMnH9bZMAo+XUm8C3 zH9fqaTOXP7DMA3au6fRiErtrjC6OdwMfrZZ8= 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=PrXF56M09B5JylmwQkGg6Gh0cGtpH/QdGLGUhLuFTeF9Sy+lTeBZW90yfcutWESp2d oilirVj7eCs7gkX+m2R9rvpKg8IiSUlqycfkMGyyfzgz/6CVIxNnSzxWMaYEN7W512sI /ThNwST6ERShU4zKK7DY1zn9ihNzaVUNppNdI= Received: by 10.224.47.75 with SMTP id m11mr4339972qaf.249.1296326366820; Sat, 29 Jan 2011 10:39:26 -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 nb15sm13534928qcb.26.2011.01.29.10.39.25 (version=SSLv3 cipher=RC4-MD5); Sat, 29 Jan 2011 10:39:25 -0800 (PST) Date: Sat, 29 Jan 2011 13:39:15 -0500 From: Alexander Kabaev To: Alexey Shuvaev Message-ID: <20110129133915.40a04c67@kan.dnsalias.net> In-Reply-To: <20110129132144.57c42924@kan.dnsalias.net> References: <20110128235851.GB95980@lexx.ifp.tuwien.ac.at> <20110129132144.57c42924@kan.dnsalias.net> 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_/9.UhzPohKV_F_.YANr6N0+A"; protocol="application/pgp-signature" Cc: gecko@freebsd.org, freebsd-current@freebsd.org, freebsd-ports@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: Sat, 29 Jan 2011 18:39:28 -0000 --Sig_/9.UhzPohKV_F_.YANr6N0+A Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 29 Jan 2011 13:21:44 -0500 Alexander Kabaev wrote: > 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 Follow-up to myself: Nope, the fix to said bug appears in our compiler. Can you make amd64 version of nsNativeCharsetUtils. --=20 Alexander Kabaev --Sig_/9.UhzPohKV_F_.YANr6N0+A Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iD8DBQFNRF7cQ6z1jMm+XZYRAmmzAJ0fem/0x8JEQmlDQozcSDP8YZAY5gCglEDR 7q/WlyE8puJiZDfuBdOXOsQ= =JhMI -----END PGP SIGNATURE----- --Sig_/9.UhzPohKV_F_.YANr6N0+A--