ports lang/gcc4x fail to build on ia64
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? many thanks -- 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ports lang/gcc4x fail to build on ia64
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=langportname=gcc4wildcard=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. - previous versions of gcc43 built everywhere; the latest version has not yet been tried on amd64 or sparc64, but builds on i386. - previous versions of gcc44 built everywhere; the latest version has not yet been tried on amd64 or sparc64, but builds on i386. - previous versions of gcc45 built everywhere; the latest version has not yet been tried on amd64 or sparc64, but builds on i386. The package building cluster is currently only set up to try builds on 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, 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. Unless a developer with specific interest in ia64 steps up to help, you may be out of luck. Sorry. mcl * yes, I know that portsmon is throwing 'database not connected' errors, but don't have a fix for it yet. It only seems to affect the query for 'show me uploaded packages', and even then not all the time. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ports lang/gcc4x fail to build on ia64
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=langportname=gcc4wildcard=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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ports lang/gcc4x fail to build on ia64
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? many thanks -- Anton Shterenlikht FYI: I mostly ported GCC 4.5 to the BSD Makefiles (svn head sys/gnu/usr.bin/cc) for ARM. Basically, I added the FreeBSD format extension, the __FreeBSD_cc_version built-in define and the PATH changes. I did not make BSD Makefile for the GMP and MPFR libraries. I don't have the FreeBSD-8.0 revision 195697 that eliminates .text relocations in shared libraries compiled with stack protector. Vassilis Laganakos has been working with GCC 4.4 on the ARM. I haven't push the compiler (and newer binutils 2.19) much beyond building the kernel. GCC 4.5 -O option creates new kernel warnings with the conditional locks. Below is a typical error: /mnt/arm64/usr/bin/gcc -mlittle-endian -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I../../.. -I../../../contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcpu=xscale -ffreestanding -Werror ../../../fs/devfs/devfs_vnops.c cc1: warnings being treated as errors ../../../fs/devfs/devfs_vnops.c: In function 'devfs_lookup': ../../../sys/sx.h:165:1: error: inlining failed in call to '__sx_xunlock': call is unlikely and code size would grow ../../../fs/devfs/devfs_vnops.c:809:3: error: called from here ../../../sys/sx.h:165:1: error: inlining failed in call to '__sx_xunlock': call is unlikely and code size would grow ../../../fs/devfs/devfs_vnops.c:817:4: error: called from here ../../../sys/sx.h:165:1: error: inlining failed in call to '__sx_xunlock': call is unlikely and code size would grow ../../../fs/devfs/devfs_vnops.c:828:4: error: called from here *** Error code 1 --Mark Tinguely. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ports lang/gcc4x fail to build on ia64
On Aug 17, 2009, at 7:36 AM, Mark Linimon wrote: The package building cluster is currently only set up to try builds on amd64, i386, and sparc64. Although we have some ia64 machines, the last time I tried to upgrade them I had trouble. Really, you have ia64 machines for ports building? Are you referring to pluto1 and pluto2 or are these entirely different beasts? Unless a developer with specific interest in ia64 steps up to help, you may be out of luck. Sorry. I'll see about fixing it... -- Marcel Moolenaar xcl...@mac.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ports lang/gcc4x fail to build on ia64
That error is gcc oh-so-helpfully telling you that it decided not to inline an function declared inline. Why the gcc devs decided that was deserving of a diagnostic on -Wall is beyond me. I think that you can squelch it by passing -Wno-inline to gcc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ports lang/gcc4x fail to build on ia64
On Mon, Aug 17, 2009 at 03:51:24PM +0100, Anton Shterenlikht wrote: I wonder if they work under ia64 linux? I don't know. A quick check of NetBSD seems to indicate that their ia64 port only runs in emulation mode; OpenBSD doesn't list an ia64 port. mcl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
