From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24957 invoked by alias); 7 Apr 2006 16:27:37 -0000 Received: (qmail 24947 invoked by uid 22791); 7 Apr 2006 16:27:36 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 07 Apr 2006 16:27:30 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k37GRPBK009705; Fri, 7 Apr 2006 12:27:25 -0400 Received: from post-office.corp.redhat.com (post-office.corp.redhat.com [172.16.52.227]) by int-mx1.corp.redhat.com (8.12.11.20060308/8.11.6) with ESMTP id k37GRFsL028648; Fri, 7 Apr 2006 12:27:15 -0400 Received: from greed.delorie.com (dj.cipe.redhat.com [10.0.0.222]) by post-office.corp.redhat.com (8.11.6/8.11.6) with ESMTP id k37GRE528173; Fri, 7 Apr 2006 12:27:14 -0400 Received: from greed.delorie.com (greed.delorie.com [127.0.0.1]) by greed.delorie.com (8.13.1/8.13.1) with ESMTP id k37GRDco006089; Fri, 7 Apr 2006 12:27:13 -0400 Received: (from dj@localhost) by greed.delorie.com (8.13.1/8.13.1/Submit) id k37GR8hd006086; Fri, 7 Apr 2006 12:27:08 -0400 Date: Fri, 07 Apr 2006 20:01:00 -0000 Message-Id: <200604071627.k37GR8hd006086@greed.delorie.com> From: DJ Delorie To: dave.korn@artimi.com CC: bdubbs@linuxfromscratch.org, gdb@sourceware.org In-reply-to: <000801c65a55$21ffa580$a501a8c0@CAM.ARTIMI.COM> (dave.korn@artimi.com) Subject: Re: Building gdb from source References: <000801c65a55$21ffa580$a501a8c0@CAM.ARTIMI.COM> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-04/txt/msg00106.txt.bz2 > 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.