From: DJ Delorie <dj@redhat.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gcc@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org,
newlib@sourceware.org
Subject: Re: On the toplevel configure and build system
Date: Wed, 30 Mar 2011 15:34:00 -0000 [thread overview]
Message-ID: <201103301534.p2UFYDTE010954@greed.delorie.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1103301502310.20285@digraph.polyomino.org.uk> (joseph@codesourcery.com)
> > (h) utils - I don't know what to do with this directory or where it best
> > goes.
>
> relates to the other bits of src and where it would best go if src is
> split up.
For example, the MeP utils is used to reconfigure gcc, binutils, cgen,
sid, and a few other places (libgloss) according to the templates
provided by the chip fab (MeP is a synthetic chip) so as to match the
specific cpu configurations in your chip (how many cores, which
options each core has, memory layout, etc).
(for the lawyers: we were careful to make the resulting files just as
editable as one would expect, you do not *need* these utils to
build/hack/use the gnu tools, only if you want an easier way to
customize them for specific hardware)
next prev parent reply other threads:[~2011-03-30 15:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 21:52 Joseph S. Myers
2011-03-29 22:28 ` DJ Delorie
2011-03-29 23:29 ` Joseph S. Myers
2011-03-29 23:41 ` Frank Ch. Eigler
2011-03-29 23:48 ` DJ Delorie
2011-03-29 23:52 ` Joseph S. Myers
2011-03-29 22:50 ` Geoffrey Keating
2011-03-30 0:07 ` Ian Lance Taylor
2011-03-29 23:45 ` Joseph S. Myers
2011-03-30 13:37 ` Tom Tromey
2011-03-30 15:16 ` Joseph S. Myers
2011-03-30 15:34 ` DJ Delorie [this message]
2011-03-30 15:54 ` Joseph S. Myers
2011-03-31 7:44 ` Paolo Bonzini
2011-03-31 12:09 ` Joseph S. Myers
2011-03-31 7:46 ` Paolo Bonzini
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=201103301534.p2UFYDTE010954@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=joseph@codesourcery.com \
--cc=newlib@sourceware.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