[Top][All Lists]

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

Re: Environment variable $U

From: Eric Blake
Subject: Re: Environment variable $U
Date: Tue, 09 Feb 2010 06:26:34 -0700
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20090812 Thunderbird/ Mnenhy/

According to Ralf Wildenhues on 2/8/2010 11:32 PM:
> Sounds like a bug to me, $U should be initialized somewhere, or removed
> from the LIBOBJS/LTLIBOBJS variables if ansi2knr is not used.

Aha.  In many projects, U _is_ initialized, but by automake during
AM_C_PROTOTYPES, and not by autoconf.  IIUC, the problem can only occur if
you are using autoconf but not automake.  So one real fix would be to quit
using U in autoconf, and to teach automake how to override
_AC_LIBOBJS_NORMALIZE to re-support U; but that has the drawback of
requiring upgrades in both automake and autoconf simultaneously.  Here's a
less-invasive fix, that only affects autoconf.

tests/ also uses $U, so we could see a
spurious test failure; I'm not sure what to do there.  Thoughts before I
apply this to autoconf?

>  Or we
> could also go ahead and remove ansi2knr support (after deprecating it
> suitably).

It's always been a desire of mine to switch to C89 as default and require
extra effort on the part of people still wanting K&R, rather than the
current situation of trying to support both by default.  But it takes lots
of time and energy to implement, and hasn't been a high priority for me.

Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden

Attachment: autoconf.patch251
Description: Text document

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

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