From: Andrew Burgess <andrew.burgess@embecosm.com>
To: SAIFI <saifi@strikr.io>
Cc: gdb@sourceware.org
Subject: Re: building GDB natively using 'configure' at 'two' levels
Date: Wed, 8 Sep 2021 09:12:51 +0100 [thread overview]
Message-ID: <20210908081251.GD4124615@embecosm.com> (raw)
In-Reply-To: <39174ae-8f97-1a1d-23e4-54688976504a@strikr.io>
* SAIFI <saifi@strikr.io> [2021-09-08 07:25:09 +0000]:
> Hi:
>
> git cloned GDB and would like to build GDB natively using 'configure' at 'two' levels.
>
> at the top of the source tree ${SRC}/gdb/, i have
>
> ${SRC}/gdb/configure \
> --prefix=/opt/gdb \
> --datadir=/opt/gdb/data \
> --htmldir=/opt/gdb/doc \
> --disable-binutils \
> --disable-ld \
> --disable-gold \
> --disable-gas \
> --disable-sim \
> --disable-gprof \
>
> and at ${SRC}/gdb/gdb/, i have
>
> ${SRC}/gdb/gdb/configure \
> --prefix=/opt/gdb \
> --datadir=/opt/gdb/data \
> --htmldir=/opt/gdb/doc \
> --disable-largefile \
> --with-gnu-ld \
> --with-expat=no \
> --with-python=no \
> --with-guile=no \
> --with-intel-pt=no \
> --with-babeltrace=no
>
> what is the recommended way to run 'configure' at the top of the
> source tree, so that it will execute the custom configure in
> gdb/gdb/ ?
Here's how I'd configure and build GDB:
mkdir binutils-gdb
cd binutils-gdb
git clone git://sourceware.org/git/binutils-gdb.git src
mkdir build
cd build
../src/configure .... all configure options here ....
make all-gdb
make check-gdb # Optional, if you want to check it's working.
make install-gdb
Configure options passed to src/configure will be forwarded to
src/gdb/configure automatically.
Hope that helps,
Thanks,
Andrew
next prev parent reply other threads:[~2021-09-08 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 7:25 SAIFI
2021-09-08 8:12 ` Andrew Burgess [this message]
2021-09-08 9:47 ` SAIFI
2021-09-08 11:30 ` Andrew Burgess
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=20210908081251.GD4124615@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb@sourceware.org \
--cc=saifi@strikr.io \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).