Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Bruce Dubbs <bdubbs@linuxfromscratch.org>
Cc: gdb@sourceware.org
Subject: Re: Building gdb from source
Date: Fri, 07 Apr 2006 06:39:00 -0000	[thread overview]
Message-ID: <20060407011629.GA8902@nevyn.them.org> (raw)
In-Reply-To: <4435BB43.1030804@linuxfromscratch.org>

On Thu, Apr 06, 2006 at 08:07:15PM -0500, Bruce Dubbs wrote:
> I like to build packages from source.  When I build gdb-6.4:
> 
> ./configure  --prefix=/usr
> make
> make install
> 
> gdb's Makefile places the following files in /usr/lib:
> 
> libbfd.a  libbfd.la  libiberty.a  libopcodes.a  libopcodes.la
> 
> The problem is that these files already exist from binutils-2.16.1.

Binutils and GDB are maintained in the same CVS repository.  In
general, you should use whichever copy of the shared libraries is
newer, but it's rarely a big deal.  For all these I would just stick
with the copy from binutils.

> Is there any reason to prefer the libraries from binutils over gdb or
> vice versa?  I believe this could be a problem as the binutils libraries
> include dynamic libraries that could be out of sync with the gdb static
> libraries and that the gdb .la files do not recognize the dynamic
> libraries at all.

GDB will never use the shared versions anyway; it always uses its own
copies.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-04-07  1:16 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 [this message]
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
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=20060407011629.GA8902@nevyn.them.org \
    --to=drow@false.org \
    --cc=bdubbs@linuxfromscratch.org \
    --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