From: Thomas Schwinge <thomas@schwinge.name>
To: binutils@sourceware.org, debian-bsd@lists.debian.org, rmh@debian.org
Subject: Re: [PATCH] Improve binutils testsuite coverage for GNU/Hurd (and kFreeBSD?)
Date: Tue, 02 Nov 2010 08:28:00 -0000 [thread overview]
Message-ID: <20101102082803.GB8107@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <20101102031451.GH26513@bubble.grove.modra.org>
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
Hello!
On Tue, Nov 02, 2010 at 01:44:51PM +1030, Alan Modra wrote:
> On Thu, Oct 28, 2010 at 12:38:23PM +0200, Thomas Schwinge wrote:
> > +proc setup_xfail_gnu_hurd {} {
> > + global target_triplet
> > + switch -regexp $target_triplet {
> > + ^\[^-\]*-\[^-\]*-gnu.*$ {
> > + setup_xfail "*-*-*"
> > + }
> > + }
> > +}
>
> What am I missing? Why not just
> setup_xfail "*-*-gnu*"
That'd mach *-*-linux-gnu*, *-*-kfreebsd-gnu*, etc., turning them into
XPASSes. As Robert suggested, we could instead add support in the
testsuite framework for considering $target_os (as opposed to
$target_triplet).
Robert, can I get access to a Debian GNU/kFreeBSD machine in order to
test that my patch doesn't break anything for you?
Regards,
Thomas
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-11-02 8:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 10:39 Thomas Schwinge
2010-10-28 13:40 ` Robert Millan
2010-10-29 5:53 ` Thomas Schwinge
2010-11-02 3:15 ` Alan Modra
2010-11-02 8:28 ` Thomas Schwinge [this message]
2010-11-02 11:45 ` Alan Modra
2010-11-04 13:20 ` Account on Debian GNU/KFreeBSD systems (was: [PATCH] Improve binutils testsuite coverage for GNU/Hurd (and kFreeBSD?)) Thomas Schwinge
2014-02-16 8:02 ` [PATCH] Improve binutils testsuite coverage for GNU/Hurd (and kFreeBSD?) Thomas Schwinge
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=20101102082803.GB8107@kepler.schwinge.homeip.net \
--to=thomas@schwinge.name \
--cc=binutils@sourceware.org \
--cc=debian-bsd@lists.debian.org \
--cc=rmh@debian.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).