From: Jeffrey A Law <law@cygnus.com>
To: David Edelsohn <dje@watson.ibm.com>
Cc: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>,
egcs@cygnus.com, Jim Wilson <wilson@cygnus.com>
Subject: Re: pre-build advice
Date: Sun, 10 May 1998 20:57:00 -0000 [thread overview]
Message-ID: <24765.894858981@hurl.cygnus.com> (raw)
In-Reply-To: <9805101810.AA37350@rios1.watson.ibm.com>
In message < 9805101810.AA37350@rios1.watson.ibm.com >you write:
> >>>>> Jeffrey A Law writes:
>
> Jeff> You can also set up a "single tree" build environment which can
> Jeff> be used to build egcs, gdb, binutils and other tools from a
> Jeff> single source tree with a single "make" command. This kind of
> Jeff> setup is easier for folks building cross compilers.
>
> While it is possible to combine egcs, binutils, newlib, gdb,
> etc. into a single tree. Including gdb seems to be discouraged because
> both it and binutils rely upon bfd in subtle ways. One can run into
> problems because of source skew between binutils and gdb as only one
> package can be the source for the bfd library. binutils is more integral
> in the toolchain, so it usually is better to include binutils in the
> "single tree" and build gdb separately.
This is certainly an issue. And I agree about the "solution" to
kick gdb out if there are bfd incompatibilties.
> Cygnus does not have this problem because they can access their
> development tree in which bfd is not forked for a particular package.
Yup.
Another solution is to pick up gdb & binutils snapshots to avoid bfd
version skew, but that's pretty high maintenance.
jeff
prev parent reply other threads:[~1998-05-10 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-04 18:07 Daniel Karipides
1998-05-05 13:33 ` H.J. Lu
1998-05-05 16:32 ` Horst von Brand
1998-05-06 2:02 ` Jim Wilson
1998-05-07 16:19 ` Alexandre Oliva
1998-05-08 15:42 ` Gerald Pfeifer
1998-05-09 23:12 ` Jeffrey A Law
1998-05-10 11:10 ` David Edelsohn
1998-05-10 20:57 ` Jeffrey A Law [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=24765.894858981@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=dje@watson.ibm.com \
--cc=egcs@cygnus.com \
--cc=pfeifer@dbai.tuwien.ac.at \
--cc=wilson@cygnus.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).