From: Mike Frysinger <vapier@gentoo.org>
To: binutils@sources.redhat.com
Subject: Re: support more sh targets in top level configure
Date: Fri, 06 May 2005 16:04:00 -0000 [thread overview]
Message-ID: <200505061151.47770.vapier@gentoo.org> (raw)
In-Reply-To: <20050506.134603.88489510.kkojima@rr.iij4u.or.jp>
On Friday 06 May 2005 12:46 am, Kaz Kojima wrote:
> The toplevel configure is shared with binutils and gcc.
ah, i was not aware of this ... what else is shared between the projects at
the top level ? is there a README i missed that outlines this or is it just
some common knowledge :)
> I don't qualify to approve it
> because it includes a general SH specific change for gcc, though the
> patch itself looks ok to me except sh64*-*-* matches sh*-*-* pattern
> already.
ok, i talked to Paul and he was going to take care of getting gcc/binutils
fixed for superh, so i'll just stop stepping on his toes
-mike
next prev parent reply other threads:[~2005-05-06 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 4:46 Mike Frysinger
2005-05-06 6:13 ` Kaz Kojima
2005-05-06 16:04 ` Mike Frysinger [this message]
2005-05-06 23:18 ` Kaz Kojima
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=200505061151.47770.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).