Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@redhat.com>
To: tromey@redhat.com
Cc: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
	Paolo Bonzini <bonzini@gnu.org>,
	        gdb@sourceware.org
Subject: Re: Moving to Autoconf 2.64, Automake 1.11
Date: Mon, 17 Aug 2009 18:18:00 -0000	[thread overview]
Message-ID: <m3praupetn.fsf@hase.home> (raw)
In-Reply-To: <m3ocqejv56.fsf@fleche.redhat.com> (Tom Tromey's message of "Mon, 	17 Aug 2009 09:51:49 -0600")

Tom Tromey <tromey@redhat.com> writes:

>>>>>> "Ralf" == Ralf Wildenhues <Ralf.Wildenhues@gmx.de> writes:
>
> Ralf> Why, by the way, do some of the trees in src contains so endlessly many
> Ralf> configure scripts?
>
> I'm not sure there is a reason.

Probably leftover from the cygnus configure times.

Andreas.

-- 
Andreas Schwab, schwab@redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84  5EC7 45C6 250E 6F00 984E
"And now for something completely different."


  reply	other threads:[~2009-08-17 16:48 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-15 11:29 Ralf Wildenhues
2009-08-15 11:31 ` [PATCH 1/N] Update automake-provided files in the toplevel Ralf Wildenhues
2009-08-15 11:33 ` [PATCH 3/N] some minor fixes in sim, gold, gdb Ralf Wildenhues
2009-08-17 16:14   ` Tom Tromey
2009-08-17 16:48   ` Ian Lance Taylor
2009-08-15 11:34 ` Moving to Autoconf 2.64, Automake 1.11 Gerald Pfeifer
2009-08-16  9:49   ` Do not point to sources.redhat.com for autotools tarballs (was: Moving to Autoconf 2.64, Automake 1.11) Ralf Wildenhues
2009-08-16 17:06     ` Eli Zaretskii
2009-08-15 11:34 ` [PATCH 4/N] The big bump Ralf Wildenhues
2009-08-15 11:49   ` Richard Guenther
2009-08-15 12:23     ` Ralf Wildenhues
2009-08-15 12:29       ` Ralf Wildenhues
2009-08-15 16:21         ` Paolo Bonzini
2009-08-17 19:39           ` fix 2.64 fopen glitch, disable option checking (was: [PATCH 4/N] The big bump) Ralf Wildenhues
2009-08-17 19:57             ` fix 2.64 fopen glitch, disable option checking Paolo Bonzini
2009-08-15 14:41   ` [PATCH 4/N] The big bump Dave Korn
2009-08-15 16:04     ` Ralf Wildenhues
2009-08-15 16:36       ` Dave Korn
2009-08-15 16:26     ` Joseph S. Myers
2009-08-17 10:20   ` Nick Clifton
2009-08-23 12:30   ` Andreas Schwab
2009-08-15 11:35 ` [PATCH 5/N] post-update cleanups Ralf Wildenhues
2009-08-15 16:58   ` Paolo Bonzini
2009-08-15 15:31 ` Moving to Autoconf 2.64, Automake 1.11 Joseph S. Myers
2009-08-15 16:07   ` Ralf Wildenhues
2009-08-16 11:48     ` install-{html,pdf} (was: Moving to Autoconf 2.64, Automake 1.11) Ralf Wildenhues
2009-08-17 11:14       ` install-{html,pdf} Paolo Bonzini
2009-08-17 10:34         ` install-{html,pdf} Paolo Bonzini
2009-08-15 18:04 ` Moving to Autoconf 2.64, Automake 1.11 Paolo Bonzini
2009-08-15 23:07   ` Ralf Wildenhues
     [not found]   ` <20090815230654.GA22525__27948.5272862532$1250377656$gmane$org@gmx.de>
2009-08-17 15:57     ` Tom Tromey
2009-08-17 18:18       ` Andreas Schwab [this message]
     [not found] ` <20090815113449.GE20172__4676.41973305053$1250336143$gmane$org@gmx.de>
2009-08-17 16:17   ` [PATCH 5/N] post-update cleanups Tom Tromey
2009-08-23 10:12 ` Moving to Autoconf 2.64, Automake 1.11 Ralf Wildenhues

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=m3praupetn.fsf@hase.home \
    --to=schwab@redhat.com \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=bonzini@gnu.org \
    --cc=gdb@sourceware.org \
    --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