Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: gcc-patches@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org
Subject: Re: mini-freeze of autotools-governed files in GCC and src
Date: Sat, 22 Aug 2009 19:13:00 -0000	[thread overview]
Message-ID: <20090822191014.GC3689@gmx.de> (raw)
In-Reply-To: <20090822110723.GB18527@gmx.de>

* Ralf Wildenhues wrote on Sat, Aug 22, 2009 at 01:07:23PM CEST:
> Please refrain from committing changes to autotools-governed files

Freeze is over.  Thanks for your patience.

The trees have been updated to Autoconf 2.64 and Automake 1.11.  Please
take a minute to ensure that you use these tools now when changing build
system generated files; and that you have them early in your $PATH if
you build with --enable-maintainer-mode.

You might have to start with a clean build tree if you use
--enable-maintainer-mode, otherwise, you might still at least have to
remove all config.cache files from an existing build tree that was built
before this freeze.

For binutils, you likely have to start off with a clean build tree
(i.e., you need to reconfigure).  If your compiler doesn't allow for
side-effect dependency-tracking, try --enable-dependency-tracking.

Please feel free to Cc: me for all bug reports that are or look like
they could be related to the new autotools versions.

I'll work on patches for the remaining parts of src to get them updated
and finish some of the leftover cleanups.

Thanks,
Ralf


  parent reply	other threads:[~2009-08-22 19:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-22 15:45 Ralf Wildenhues
2009-08-22 19:10 ` NightStrike
2009-08-22 19:13 ` Ralf Wildenhues [this message]
2009-08-23 14:04   ` Kaveh R. GHAZI
2009-08-23 14:22     ` Ralf Wildenhues
2009-08-23 15:48       ` Kaveh R. Ghazi

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=20090822191014.GC3689@gmx.de \
    --to=ralf.wildenhues@gmx.de \
    --cc=binutils@sourceware.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb@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