Date: Mon, 16 Jul 2012 10:16:38 +1000 From: Peter Jeremy <peter@rulingia.com> To: Gerald Pfeifer <gerald@pfeifer.com> Cc: freebsd-sparc64@freebsd.org Subject: Re: lang/gcc46 build failure on sparc64 Message-ID: <20120716001638.GB49069@server.rulingia.com> In-Reply-To: <alpine.LNX.2.00.1207151533410.5035@gerinyyl.fvgr> References: <20120621081705.GA41013@mech-cluster241.men.bris.ac.uk> <20120714121820.GA84132@server.rulingia.com> <alpine.LNX.2.00.1207151533410.5035@gerinyyl.fvgr>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
On 2012-Jul-15 15:57:13 +0200, Gerald Pfeifer <gerald@pfeifer.com> wrote:
>On Sat, 14 Jul 2012, Peter Jeremy wrote:
>> As a work-around, I'd suggest using ports/lang/gcc - which is the
>> stable branch of gcc-4.6
>
>Are you saying that on the same machine and base system, lang/gcc46
>fails to build whereas lang/gcc succeeds?
Hmmm.... It looks like I was wrong. I _had_ lang/gcc installed
on my sparc64 so I was able to build it in the past but I've just
re-checked and I can't build it any longer. Working out when it
broke would be quite time consuming given the speed of my sparc.
Sorry for the misleading suggestion.
>I was starting to feel this might be related to base systems built
>with WITH_ICONV=YES (in /etc/src.conf); can you check whether that
>is on, and if so, does make a difference?
I don't have WITH{OUT}_ICONV specified in my base system.
--
Peter Jeremy
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)
iEYEARECAAYFAlADXWYACgkQ/opHv/APuIdeWQCeO9vRa3Kza2Bg4LcbVHMuP2uM
0wkAoLvprncoOXqWbG6OodDu1K2vMboo
=TrzK
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120716001638.GB49069>