Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Rob Savoye <rob@welcomehome.org>
Cc: gdb-patches@sources.redhat.com, bug-dejagnu@gnu.org
Subject: Re: [Bug-dejagnu] Re: AM33/2.0 support for mn10300-elf
Date: Tue, 22 Jul 2003 20:02:00 -0000	[thread overview]
Message-ID: <or3cgyz5wf.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20030716095605.G20162@welcomehome.org>

On Jul 16, 2003, Rob Savoye <rob@welcomehome.org> wrote:

>   Well, the compiler name *should* really be gotten by transforming the
> target name

Yup.

> but I assume there was some reason for hardcoding it?

I've no idea :-(

> It looks like am33_2.0-linux-gnu isn't a standard
> target-triplet. What does config.guess return on this target?

Err...  I'm not sure config.guess supports it at all (we have mostly
only cross-built to it), but config.sub (as in ftp.gnu.org)
recognizes am33_2.0-unkwnon-linux-gnu as a canonical form.

>   As I'm guessing almost nobody uses this target, I'll check this into
> Savannah 'as is".

Thanks.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer


  reply	other threads:[~2003-07-22 20:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-10  3:10 Alexandre Oliva
2003-07-10  3:31 ` Alexandre Oliva
2003-07-10  4:59   ` Alexandre Oliva
2003-07-16 16:05     ` [Bug-dejagnu] " Rob Savoye
2003-07-22 20:02       ` Alexandre Oliva [this message]
2003-07-10  4:57 ` Alexandre Oliva
2003-08-02 14:26 ` Andrew Cagney
2004-06-21 13:59   ` Alexandre Oliva
2004-06-25 21:41     ` Andrew Cagney
2004-06-26 22:00     ` Alexandre Oliva
2004-06-26 22:00   ` Alexandre Oliva
2004-06-26 22:18   ` Alexandre Oliva

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=or3cgyz5wf.fsf@free.redhat.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=bug-dejagnu@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=rob@welcomehome.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