From: Doug Evans <dje@google.com>
To: Bob Rossi <bob@brasko.net>
Cc: gdb <gdb@sourceware.org>
Subject: Re: building gdb from git
Date: Wed, 09 Apr 2014 21:54:00 -0000 [thread overview]
Message-ID: <CADPb22RouHH4Gqwk6OAHR5DyYmEax-1=Cihy3ex_+L+tTaAW8Q@mail.gmail.com> (raw)
In-Reply-To: <20140409202119.GA1325@linux>
On Wed, Apr 9, 2014 at 1:21 PM, Bob Rossi <bob@brasko.net> wrote:
> Hi,
>
> When I clone git I get quite a few projects.
>
> What's the simplest way to build only gdb?
>
> My first attempt was to do this:
> ../binutils-gdb/gdb/configure --prefix=$PWD/../prefix
> however this failed with a missing bfd.h.
>
> In general, if I only really want to build/modify gdb,
> should I attempt to build everything like,
> ../binutils-gdb/configure --prefix=$PWD/../prefix
> or should I install the dev packages for everything I'm missing?
You need to run configure from the top level.
I.e.
../binutils-gdb/configure ...
not
../binutils-gdb/gdb/configure ...
gdb uses several libraries in the binutils-gdb repo and those must be
built first.
You're probably worried that if you run the top level configure and
then do "make" that will build everything including
gas,ld,binutils,etc. and not just the gdb you want.
One solution to this is to do "make all-gdb" instead of "make".
There are also configure options to disable building of pieces so that
"make" will then build just gdb.
../binutils-gdb/configure --disable-gas --disable-binutils
--disable-ld --disable-gold --disable-gprof
[I think(!) I spelled those right and I think(!) I remembered
everything to disable.]
prev parent reply other threads:[~2014-04-09 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 20:21 Bob Rossi
2014-04-09 21:54 ` Doug Evans [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='CADPb22RouHH4Gqwk6OAHR5DyYmEax-1=Cihy3ex_+L+tTaAW8Q@mail.gmail.com' \
--to=dje@google.com \
--cc=bob@brasko.net \
--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