From: Daniel Jacobowitz <drow@false.org>
To: Dave Korn <dave.korn@artimi.com>
Cc: 'Bruce Dubbs' <bdubbs@linuxfromscratch.org>, gdb@sourceware.org
Subject: Re: Building gdb from source
Date: Fri, 07 Apr 2006 15:32:00 -0000 [thread overview]
Message-ID: <20060407151854.GA23220@nevyn.them.org> (raw)
In-Reply-To: <000801c65a55$21ffa580$a501a8c0@CAM.ARTIMI.COM>
On Fri, Apr 07, 2006 at 04:08:31PM +0100, Dave Korn wrote:
> The point is, that a distro should have a consistent set of gcc, binutils
> and gdb. Since binutils and gdb live in the same repository, if you either
> take a consistent snapshot of the cvs, or if you take gdb and binutils
> releases that are roughly-contemporary, they're bound to be 'in-sync' FAPP.
This is not true. There's no reason to believe that "roughly
contemporary" is good enough.
But it completely fails to matter. Very little uses these libraries
and most of what does will work with both. If you install binutils
with shared libraries, then you should use the binutils copy; otherwise
use either.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-07 15:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 1:16 Bruce Dubbs
2006-04-07 6:39 ` Daniel Jacobowitz
2006-04-07 15:02 ` Dave Korn
2006-04-07 15:19 ` Bruce Dubbs
2006-04-07 15:26 ` Dave Korn
2006-04-07 15:32 ` Daniel Jacobowitz [this message]
2006-04-07 15:39 ` Dave Korn
2006-04-07 15:40 ` 'Daniel Jacobowitz'
2006-04-07 15:49 ` Dave Korn
2006-04-07 15:58 ` 'Daniel Jacobowitz'
2006-04-07 16:27 ` Dave Korn
2006-04-07 15:54 ` Bruce Dubbs
2006-04-07 20:01 ` DJ Delorie
2006-04-14 6:10 ` "Program received signal SIG33" error yinglcs2
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=20060407151854.GA23220@nevyn.them.org \
--to=drow@false.org \
--cc=bdubbs@linuxfromscratch.org \
--cc=dave.korn@artimi.com \
--cc=gdb@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