From: Nick Clifton <nickc@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: binutils@sourceware.org
Subject: Re: make check failures with binutils-2.17
Date: Fri, 07 Jul 2006 09:22:00 -0000 [thread overview]
Message-ID: <44AE27C5.6030302@redhat.com> (raw)
In-Reply-To: <200607031717.52358.vapier@gentoo.org>
Hi Mike,
> cross compile targets that failed:
> alpha-linux-gnu
> armeb-linux-gnu
> avr
Do you mean "avr-elf" here ?
> hppa-linux-gnu
> hppa64-linux-gnu
> mips64-linux-gnu
> mips64el-linux-gnu
Do all these targets fail in the same way ?
Were you able to build other targets that do not fail the make check ?
Anyway to answer your question, I do not have access to a ppc machine,
but I do have an amd64 machine (running a 64-bit OS) and on that machine
I get these results:
The alpha-linux-gnu toolchain fails the LD check with:
FAIL: TLS -fpic -shared
FAIL: TLS -fpic and -fno-pic exec
FAIL: TLS -fpic and -fno-pic exec -relax
FAIL: ld-elf/64ksec
The armeb-linux-gnu toolchain fails the GAS check with:
FAIL: Unwind table generation
The avr-elf toolchain fails the GAS check with:
FAIL: lns-common-1
The hppa-linux-gnu and hppa64-linux-gnu toolchains fail the GAS check with:
XPASS: Check min/max values for .block
The mips64-linux-gnu and mips64el-linux-gnu toolchains fail the LD check
with:
FAIL: ld-elf/orphan2
FAIL: ld-mips-elf/reloc-1-n64
FAIL: MIPS eh-frame 1, n32
FAIL: MIPS eh-frame 1, n64
FAIL: MIPS eh-frame 2, n32
FAIL: MIPS eh-frame 2, n64
Does this match your own findings ?
Cheers
Nick
next prev parent reply other threads:[~2006-07-07 9:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 21:17 Mike Frysinger
2006-07-06 9:24 ` Nick Clifton
2006-07-06 19:03 ` Mike Frysinger
2006-07-06 20:31 ` Thiemo Seufer
2006-07-06 22:15 ` Mike Frysinger
2006-07-07 9:22 ` Nick Clifton [this message]
2006-07-07 18:22 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44AE27C5.6030302@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=vapier@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).