From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] "etext/_etext" may be missing, add configure check
Date: Wed, 19 Sep 2007 19:46:00 -0000 [thread overview]
Message-ID: <20070919194644.GA10542@caradoc.them.org> (raw)
In-Reply-To: <20070919193448.GA15629@adacore.com>
On Wed, Sep 19, 2007 at 12:34:48PM -0700, Joel Brobecker wrote:
> I propose to add a check in configure for "etext", and then
> change the above to define TEXTEND only if at least either of
> the etext symbol is defined. Then we can add the definition of
> TEXT to the conditionalization that decides whether or not to
> include the profiling functionality.
Sure.
> On a side-note, I also think that --enable-profiling=no should
> have deactivated this code as well, but that's a different thread.
I don't. That's supposed to disable automatic profiling and compiling
with -pg, not the manual profiling commands.
> 2007-09-19 Joel Brobecker <brobecker@adacore.com>
>
> * configure.ac: Add check for "etext".
> * configure, config.in: Regenerate.
> * maint.c (TEXTEND): Only define if either _etext or etext
> are available.
> Disable the profiling functionality if TEXTEND is not defined.
OK.
> This was tested on x86-linux, without any regressions. On LynxOS, it
> allows me to complete the GDB build (although it's a dummy GDB at this
> point, since my primary interest is in the gdbserver).
You don't need this, by the way. Unlike the gdb subdirectory, the
gdb/gdbserver subdirectory is standalone. You need the whole source
tree but you can run src/gdb/gdbserver/configure directly. This
should be in the manual, or at least the README.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-09-19 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 19:34 Joel Brobecker
2007-09-19 19:46 ` Daniel Jacobowitz [this message]
2007-09-19 22:04 ` Joel Brobecker
2007-09-19 22:29 ` Joel Brobecker
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=20070919194644.GA10542@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@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