Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] "etext/_etext" may be missing, add configure check
Date: Wed, 19 Sep 2007 22:04:00 -0000	[thread overview]
Message-ID: <20070919220441.GF742@adacore.com> (raw)
In-Reply-To: <20070919194644.GA10542@caradoc.them.org>

> > 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.

Oh, I see, I misunderstood the purpose of that switch... Thanks for
pointing this out.

> > 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.

Thanks. I just checked this change in.

> 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.

I just double checked and it is indeed in the README (I read it too
quickly it appears). All this time I have spent watching our little
board build GDB, when it wasn't necessary :-/... Oh well, there is
still a little bit of a gain, since GDB now builds on LynxOS too.
Adding the native part shouldn't be too hard if anyone is interested.

Thanks again,
-- 
Joel


  reply	other threads:[~2007-09-19 22:04 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
2007-09-19 22:04   ` Joel Brobecker [this message]
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=20070919220441.GF742@adacore.com \
    --to=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