All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] update configure.ac to autoconf 2.61
Date: Thu, 04 Sep 2008 19:32:25 +0200	[thread overview]
Message-ID: <1220549545.18782.17.camel@fz.local> (raw)
In-Reply-To: <1220546981.16992.35.camel@dv>

Am Donnerstag, den 04.09.2008, 12:49 -0400 schrieb Pavel Roskin:

> I'm fine with the shorter patch, but I'd like you to wait a couple of
> days in case there are any objections.

Vesa said already on IRC to me that it's fine for me to but he suggests
waiting vor Okuji or Marco which I wanted to do anyway (at least with
the 2.61 requirement)

Now 2.59 shouldn't be any problem at all but yeah just in case :)

> By the way, config.h.in is a generated file, so changes to it don't need
> to be published.  The same applies to configure and *.mk files.

Yep Autoheader generates it, I just wanted to show the difference with
the newer `AC_USE_SYSTEM_EXTENSIONS' in case someone is interested :)
I saw it now even in the docs it's only supported with autoconf >= 2.60

and because I just don't know enough if it would be safe for us to just
start using it I downgraded autoconf to 2.61 for `autupdate'.

It would be better if we use for the SVN ./configure only one autoconf
version.

I just noticed that with current SVN and a ./autogen.sh with autoconf
2.62 creates the config.h.in in my 2.62 patch, which is the only
difference.
So this means that AC_GNU_SOURCE will be in the future just an alias to
it.
A little thing we maybe shouldn't forget totally :)
But for now this is really too early to change configure.ac to it.

-- 
Felix Zielcke




  reply	other threads:[~2008-09-04 17:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03 13:27 [PATCH] update configure.ac to autoconf 2.61 Felix Zielcke
2008-09-03 14:51 ` Felix Zielcke
2008-09-03 23:47   ` Pavel Roskin
2008-09-04  7:55     ` Felix Zielcke
2008-09-03 23:43 ` Pavel Roskin
2008-09-04  7:45   ` Felix Zielcke
2008-09-04 16:49     ` Pavel Roskin
2008-09-04 17:32       ` Felix Zielcke [this message]
2008-09-21 17:39     ` Felix Zielcke

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=1220549545.18782.17.camel@fz.local \
    --to=fzielcke@z-51.de \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.