[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


From: Ralf Wildenhues
Date: Tue, 18 Nov 2008 08:07:23 +0100
User-agent: Mutt/1.5.18 (2008-05-17)


* Eric Blake wrote on Tue, Nov 18, 2008 at 03:59:34AM CET:
> According to Alfred de Wijn on 11/17/2008 6:44 PM:
> > I now just do some checks early to see which *FLAGS environment
> > variables are set.  This way I'm independent of autoconf internals, and
> > so it's probably a good idea anyway,
> Yep, that is the portable solution that should work across all autoconf
> versions.  In general, if you want to test if a variable was in use, then
> it is safest to add shell code to do that check right after AC_INIT and
> prior to calling any macros that might also care about the variable (a
> similar case is using $@ within configure.ac - a user that wants to save
> the original command-line arguments must grab them immediately after
> AC_INIT, since many other autoconf macros liberally use 'set').

Good advice.

> > A test is attached, for what it's worth.  mutt should behave better than
> > Mail.app when it comes to attachments.
> Yep, the patch came through much nicer.

However, that mail seems to not have come through to the list.

> So, a plea to all bug-autoconf readers - any preferences on whether I
> should apply 0, 1, or 2 of Alfred's patches?  If I don't hear anything by
> Friday, then I'll apply just the first patch, for the sake of consistency
> with C/C++.

Not having seen any but version 0, I'd say apply that but don't document
it.  Judging would be easier with the other mail.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]