Date: Fri, 28 Feb 2003 17:37:15 +1000 From: Peter Grehan <grehan@freebsd.org> To: obrien@freebsd.org Cc: freebsd-powerpc@freebsd.org Subject: Re: Patch to allow buildworld for powerpc Message-ID: <3E5F11AB.BE6725A5@freebsd.org> References: <1045782782.618.48.camel@localhost> <3E556D95.37339AF0@freebsd.org> <20030225170134.GA94451@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Rather than dicking around with cross-builds (which I've *NEVER* gotten > to work), when can we get a tarball that I can lay down and do NFS > booting? http://people.freebsd.org/~grehan/root_current.tar.bz2 but, use the more recent kernel from http://people.freebsd.org/~grehan/kernel The loader in the tarball is fine. I will fix all toolchain problems and push the changes back to > the FSF repo when that happens. The toolchain in the tarball is built with default-signed-chars, mainly since it avoided the 50 or so compile warnings from code that isn't unsigned-char safe. This was laziness on my part, and should really be fixed. ARM/S390 are also unsigned-char arch's, and NetBSD/PPC & Linux/PPC used unsigned chars. The gcc mods used in the build are Benno's combined sysv4.h/freebsd.h, up at http://people.freebsd.org/~grehan/gcc_freebsd_benno.diff. One toolchain problem is that there really needs to be a shared libgcc. The static one generates non-PIC relocations e.g. try running vmstat. There are also non-PIC relocations in libstdc++, but I haven't investigated enough to see if it is the static libgcc causing these. later, Peter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ppc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E5F11AB.BE6725A5>