From: SAIFI <saifi@strikr.io>
To: gdb@sourceware.org
Subject: Re: building GDB natively using 'configure' at 'two' levels
Date: Wed, 8 Sep 2021 09:47:12 +0000 (UTC) [thread overview]
Message-ID: <2df2c098-b45b-9f9-face-36ec5384bed@strikr.io> (raw)
In-Reply-To: <20210908081251.GD4124615@embecosm.com>
On Wed, 8 Sep 2021, Andrew Burgess wrote:
>
> Here's how I'd configure and build GDB:
>
> ...
> ../src/configure .... all configure options here ....
>
> ....
> Configure options passed to src/configure will be forwarded to
> src/gdb/configure automatically.
>
Thanks Andrew !
in essence, 'sub'-configure options can be specified to the 'top'-configure
${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 \
--disable-largefile \
--with-gnu-ld \
--with-expat=no \
--with-python=no \
--with-guile=no \
--with-intel-pt=no \
--with-babeltrace=no
in other words,
as an example, given that there are three sub directories with a configure script
sub_dir_01
sub_dir_02
sub_dir_03
if sub_dir_01 'configure' had options
o1
o2
o3
and sub_dir_02 'configure' had options
o4
o5
then top level 'configure' will apply the 'union' of all the options specified
o1
o2
o3
o4
o5
to each sub-directory which has a 'configure' script, ie.
sub_dir_01
sub_dir_02
sub_dir_03
sorry for being pedantic, just making sure that i understood 'the manner of application of options' correctly.
warm regards
Saifi.
next prev parent reply other threads:[~2021-09-08 9:45 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
2021-09-08 9:47 ` SAIFI [this message]
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=2df2c098-b45b-9f9-face-36ec5384bed@strikr.io \
--to=saifi@strikr.io \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).