public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: libc-ports@sourceware.org, patches@linaro.org
Subject: Re: [PATCH][arm] Create ARM unwind records for system call stubs
Date: Wed, 23 Mar 2011 13:56:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1103231354090.26696@digraph.polyomino.org.uk> (raw)
In-Reply-To: <201103231349.p2NDnOQS003216@d06av02.portsmouth.uk.ibm.com>

On Wed, 23 Mar 2011, Ulrich Weigand wrote:

> Joseph S. Myers wrote:
> > On Mon, 21 Mar 2011, Ulrich Weigand wrote:
> > 
> > > I've tested this by running the glibc testsuite on armv7l-linux-gnueabi
> > 
> > Incidentally, does this mean you have a local config.sub patch for this 
> > target?  Because neither the current version in config.git, nor the rather 
> > older version in libc, accepts this target.
> > 
> > $ ./config.sub armv7l-linux-gnueabi
> > Invalid configuration `armv7l-linux-gnueabi': machine `armv7l' not recognized
> 
> No, I just misspelled the triple in the email; the actual triple I used was:
>   armv7l-unknown-linux-gnueabi
> 
> (I would have thought the "unknown" can be omitted, but apparently not.)

That it can't be omitted would be a bug in config.sub (that in one place 
it accepts arm | arm[bl]e | arme[lb] | armv[2345] | armv[345][lb], in 
another arm-*  | armbe-* | armle-* | armeb-* | armv*-*, rather than being 
consistent in the forms of ARM name accepted).

-- 
Joseph S. Myers
joseph@codesourcery.com

      reply	other threads:[~2011-03-23 13:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21 18:29 Ulrich Weigand
2011-03-21 20:46 ` Joseph S. Myers
2011-03-23 13:14 ` Joseph S. Myers
2011-03-23 13:49   ` Ulrich Weigand
2011-03-23 13:56     ` Joseph S. Myers [this message]

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=Pine.LNX.4.64.1103231354090.26696@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=libc-ports@sourceware.org \
    --cc=patches@linaro.org \
    --cc=uweigand@de.ibm.com \
    /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).