From: Daniel Jacobowitz <drow@false.org>
To: Steve Ellcey <sje@cup.hp.com>
Cc: gdb@sourceware.org
Subject: Re: gdb autoconf question (gdb/nlm subdirectory)
Date: Tue, 21 Mar 2006 04:36:00 -0000 [thread overview]
Message-ID: <20060320231148.GA9035@nevyn.them.org> (raw)
In-Reply-To: <200603202304.PAA13729@hpsje.cup.hp.com>
On Mon, Mar 20, 2006 at 03:04:53PM -0800, Steve Ellcey wrote:
>
> I am looking at what version of autoconf parts of the src tree are using
> because I want to update libtool and that requires that everything use a
> autoconf 2.5 or later.
>
> Almost all of gdb is using autoconf 2.59, but the gdb/nlm directory, for
> some reason, is still configured with autoconf 2.13. Does anyone know
> why?
>
> I ran autoconf 2.59 on the current configure.in file in gdb/nlm and it
> seemed to work OK. I didn't get any errors or warnings from autoconf.
> The resulting configure file is quite different due to changes between
> autoconf 2.13 and 2.59 but it looked OK and I didn't do anymore testing
> because it looks like this subdirectory is only used by netware targets
> and I don't have one of those.
>
> Does anyone know why the gdb/nlm subdirectory couldn't be changed to use
> autoconf 2.59?
Not I. But, in fact, I know no reason why it couldn't be removed,
either - I don't have any idea if that code still works and I haven't
heard of anyone using it.
In the mean time, we can probably just upgrade it, but let's wait a
little bit to see if anyone else has an opinion.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-20 23:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 23:14 Steve Ellcey
2006-03-21 4:36 ` Daniel Jacobowitz [this message]
2006-03-21 5:12 ` Stan Shebs
2006-03-21 14:20 ` Ian Lance Taylor
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=20060320231148.GA9035@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=sje@cup.hp.com \
/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