Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: dave.korn@artimi.com
Cc: bdubbs@linuxfromscratch.org, gdb@sourceware.org
Subject: Re: Building gdb from source
Date: Fri, 07 Apr 2006 20:01:00 -0000	[thread overview]
Message-ID: <200604071627.k37GR8hd006086@greed.delorie.com> (raw)
In-Reply-To: <000801c65a55$21ffa580$a501a8c0@CAM.ARTIMI.COM> 	(dave.korn@artimi.com)


>   The point is, that a distro should have a consistent set of gcc,
> binutils and gdb.

Since gcc, binutils, and gdb do not coordinate their release cycles,
it's impossible to do so.

As a side note, libiberty was never intended to be *installed* as a
library.  It exists to help port projects within their build tree, and
we DO NOT guarantee any usefulness outside a build tree (although we
try to avoid gratuitously breaking binary compatibility).

I suspect that the installation of libiberty bits has "just happened"
over time, and probably should be disabled by default anyway.


  parent reply	other threads:[~2006-04-07 16:27 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
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 [this message]
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=200604071627.k37GR8hd006086@greed.delorie.com \
    --to=dj@redhat.com \
    --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