From: Kaz Kojima <kkojima@rr.iij4u.or.jp>
To: vapier@gentoo.org
Cc: binutils@sources.redhat.com
Subject: Re: support more sh targets in top level configure
Date: Fri, 06 May 2005 23:18:00 -0000 [thread overview]
Message-ID: <20050507.081751.23027194.kkojima@rr.iij4u.or.jp> (raw)
In-Reply-To: <200505061151.47770.vapier@gentoo.org>
Mike Frysinger <vapier@gentoo.org> wrote:
> 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 :)
Ah, I completely forget where this knowledge came from to me :-)
I'm not sure about the complete lists, though it's shared also
between the projects in src repository of sourceware.org.
Your patch added libgcj, newlib and libgross to noconfigdirs
as default and skiped gprof on some hosts for more sh targets.
It'll affect gcc, binutils and newlib in theory.
Regards,
kaz
prev parent reply other threads:[~2005-05-06 23:18 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
2005-05-06 23:18 ` Kaz Kojima [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=20050507.081751.23027194.kkojima@rr.iij4u.or.jp \
--to=kkojima@rr.iij4u.or.jp \
--cc=binutils@sources.redhat.com \
--cc=vapier@gentoo.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).