ports lang/gcc4x fail to build on ia64
Anton Shterenlikht
mexas at bristol.ac.uk
Mon Aug 17 14:51:46 UTC 2009
On Mon, Aug 17, 2009 at 09:36:02AM -0500, Mark Linimon wrote:
> On Mon, Aug 17, 2009 at 02:57:52PM +0100, Anton Shterenlikht wrote:
> > Ports lang/gcc43, 44 and 45 fail to build on 8.0-beta2 ia64:
> > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40959
> >
> > I know they build fine on 6.4-stable alpha, but what about sparc64?
> > amd64? mips?
>
> You can check things like this using the Ports Monitoring tool:
> http://portsmon.freebsd.org/portoverview.py?category=lang&portname=gcc4&wildcard=yes
>
> According to that, for 8.0:
>
> - gcc4* are set to "not for ia64". From a commit log for gcc43/Makefile:
>
> Add ia64 to NOT_FOR_ARCHS. This has been broken for ages, it is not clear
> whether it is our kernel/userland, the hardware, or something else at fault
> and nobody on our side nor upstream seems to have any interest.
yes, I understand.. Unfortunately a FBSD system without gcc4x is of little
use to me, because I need fortran OMP compiler, and many other ports
which depend on gcc4x.
I wonder if they work under ia64 linux?
> amd64, i386, and sparc64. Although we have some ia64 machines, the last
> time I tried to upgrade them I had trouble. We do not yet have any arm,
I volunteer to build gcc4x ports on my rx2600 SMP ia64 current.
> mips, or powerpc machines. Our alphas have been deinstalled (sorry),
> after the alpha src code had fallen too far behind the main 3 archs, and
> no one was keeping it up.
yes, I gave up on alpha because of this.
> Unless a developer with specific interest in ia64 steps up to help,
> you may be out of luck. Sorry.
well.. unfortunately I've no relevant skills to offer, only testing.
--
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 928 8233
Fax: +44 (0)117 929 4423
More information about the freebsd-current
mailing list