Re: PowerPC port broken?
- From: Ruslan Ermilov <ru@xxxxxxxxxxx>
- Date: Tue, 30 Jan 2007 16:28:39 +0300
On Fri, Jan 26, 2007 at 03:13:04PM +0800, LI Xin wrote:
Marcel Moolenaar wrote:We've a fix for this problem since last summer.
On Jan 25, 2007, at 10:15 PM, LI Xin wrote:
Latest build shows this:
(What does Assembler messages:
FATAL: can't create crtbegin.o: Invalid bfd target
mean for me, by the way?)
This probably means that the wrong compiler driver or
assembler is being picked up. One that doesn't isn't
targeting powerpc.
I'll fire-up a cross-build on my amd64 and get back
to you...
Stop in /usr/src.
[1] Exit 1 make buildworld TARGET=powerpc
__MAKE_CONF=/dev/null > _.powerpc.buildworld
What happens if you set TARGET_ARCH instead of TARGET?
Still same problem... Do we have a public reference PowerPC box for
committers to test changes? This is the only platform I have not tested
my gzip related changes :-)
See PR amd64/102996 for details and the patch.
Please don't ask me about committing it into
our Binutils. :-)
Cheers,
--
Ruslan Ermilov
ru@xxxxxxxxxxx
FreeBSD committer
Attachment:
pgp5DVVQyoU8d.pgp
Description: PGP signature
- Follow-Ups:
- Re: PowerPC port broken?
- From: Marcel Moolenaar
- Re: PowerPC port broken?
- References:
- PowerPC port broken?
- From: LI Xin
- Re: PowerPC port broken?
- From: Marcel Moolenaar
- Re: PowerPC port broken?
- From: LI Xin
- Re: PowerPC port broken?
- From: LI Xin
- Re: PowerPC port broken?
- From: Marcel Moolenaar
- Re: PowerPC port broken?
- From: LI Xin
- PowerPC port broken?
- Prev by Date: [head tinderbox] failure on i386/i386
- Next by Date: restoring PCI config space
- Previous by thread: Re: PowerPC port broken?
- Next by thread: Re: PowerPC port broken?
- Index(es):