Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: tromey@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: Which autoheader?
Date: Tue, 09 Jul 2002 07:16:00 -0000	[thread overview]
Message-ID: <3D2AEFE7.2090605@ges.redhat.com> (raw)
In-Reply-To: <87ptxxfpsh.fsf@fleche.redhat.com>

> "Andrew" == Andrew Cagney <ac131313@ges.redhat.com> writes:
> 
> 
> Andrew> Which version of autoheader did you use when re-generating
> Andrew> config.in?  I'm finding that, using 000227, I can't reproduce
> Andrew> config.in.
> 
> fleche. autoheader --version
> Autoconf version 2.13
> 
> This is the autoconf in Red Hat Linux 7.3.
> One hopes it hasn't been modified from the net release very heavily.


> What is 000227?

Both GDB and BINUTILS are regenerated using auto ``000227'' which can be 
found in:
	ftp://sources.redhat.com/~ftp/pub/binutils/
there are also automake, gettext and libtool.  How applicable the latter 
ones are to GDB I don't know.
(this confusion is normal :-)

> I've never heard of an autoconf release named that way.
> 
> What does your autoheader generate for config.in?

Re-generating both configure.in and configure had the attached effect.

> Looking more closely, I see I checked in a config.in that includes
> PACKAGE -- but the configure.in patch hasn't yet been accepted for
> gdb.  This definition is bogus but harmless.  Is that what you're
> seeing?  If so I can revert that patch easily.

No the <sys/stat.h> et.al. checks.

I'll re-generate both and check the result in.

enjoy,
Andrew



  reply	other threads:[~2002-07-09 14:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-08 22:04 Andrew Cagney
2002-07-08 22:10 ` Tom Tromey
2002-07-09  7:16   ` Andrew Cagney [this message]
2002-07-09  8:59     ` Joel Brobecker
2002-07-09 14:14       ` Andrew Cagney
2002-07-09 21:58         ` Joel Brobecker
2002-07-10  2:25           ` Eli Zaretskii
2002-07-10  9:18             ` 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=3D2AEFE7.2090605@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=tromey@redhat.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