From: Rob Savoye <rob@welcomehome.org>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: gdb-patches@sources.redhat.com, bug-dejagnu@gnu.org
Subject: Re: [Bug-dejagnu] Re: AM33/2.0 support for mn10300-elf
Date: Wed, 16 Jul 2003 16:05:00 -0000 [thread overview]
Message-ID: <20030716095605.G20162@welcomehome.org> (raw)
In-Reply-To: <or1xwzyo1n.fsf@free.redhat.lsd.ic.unicamp.br>; from Alexandre Oliva on Thu, Jul 10, 2003 at 01:59:48AM -0300
On Thu, Jul 10, 2003 at 01:59:48AM -0300, Alexandre Oliva wrote:
> > These are the dejagnu bits, posted separately for convenience of the
> > DejaGNU maintainer :-) Ok for the GDB repository?
>
> And here's a patch for am33_2.0-unknown-linux-gnu. It seems to be
> lacking some love (setting compiler the way it does is odd, but I'm no
> expert in this kind of file), and I'm not entirely sure we actually
> use it any longer, but I thought I'd post it anyway. Should I put it
> in?
Well, the compiler name *should* really be gotten by transforming the
target name, but I assume there was some reason for hardcoding it ? It looks
like am33_2.0-linux-gnu isn't a standard target-triplet. What does
config.guess return on this target ? find_gcc should have worked.
As I'm guessing almost nobody uses this target, I'll check this into
Savannah 'as is".
- rob -
next prev parent reply other threads:[~2003-07-16 16:05 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 ` Rob Savoye [this message]
2003-07-22 20:02 ` [Bug-dejagnu] " Alexandre Oliva
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=20030716095605.G20162@welcomehome.org \
--to=rob@welcomehome.org \
--cc=aoliva@redhat.com \
--cc=bug-dejagnu@gnu.org \
--cc=gdb-patches@sources.redhat.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