Eric Blake ebb9 at byu.net writes:
The second patch is for something I discovered when trying to fix bison's
usage
of m4sugar [1]. Bison forked m4sugar somewhere in between autoconf 2.59 and
2.59c, then added m4_prepend, and skips the m4_PACKAGE_* macros defined in
autoconf's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ralf Wildenhues on 7/14/2008 1:23 PM:
| Hi Eric,
|
| * Eric Blake wrote on Sun, Jul 13, 2008 at 05:40:51AM CEST:
| In the meantime, I coded up a test; I will probably commit it as
| m4/examples/append.m4 and add it to the m4 testsuite if
Bob Friesenhahn wrote:
On Mon, 14 Jul 2008, Philip Prindeville wrote:
And is there a autoconf-lint to check for using broken names, like
ac_cv_sizeof_long_long_unsigned_int instead of whatever is preferred?
I prefer ac_cv_sizeof_long_long_unsigned_int because it is my nature
to be pedantic
* Philip Prindeville wrote on Tue, Jul 15, 2008 at 01:27:17AM CEST:
I'm looking at sox-12.17.9 and seeing in their configure file (which
claims to be generated via Autoconf 2.59) from their configure.in file
and seeing:
ac_cv_sizeof_x=$ac_cv_sizeof_char:$ac_cv_sizeof_short
Well, for
On Mon, 14 Jul 2008 12:24:31 -0400
Ben Taylor [EMAIL PROTECTED] wrote:
On Mon, Jul 14, 2008 at 11:46 AM, [EMAIL PROTECTED] wrote:
Hi,
On Mon, 14 Jul 2008 08:32:44 -0400
Ben Taylor [EMAIL PROTECTED] wrote:
so i have something like prefix/lib and prefix/lib/sparcv9 for sparc
and prefix/lib and
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Philip Prindeville on 7/14/2008 5:27 PM:
| I'm looking at sox-12.17.9 and seeing in their configure file (which
| claims to be generated via Autoconf 2.59)
Newer autoconf versions are able to accurately determine
On Mon, 2008-07-14 at 19:25 -0500, Bob Friesenhahn wrote:
I prefer ac_cv_sizeof_long_long_unsigned_int because it is my nature
to be pedantic and it sounds bigger. Is that bad?
Refreshingly honest, actually.
If stdint.h and inttypes.h were available everywhere then much of
this gobbly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Philip Prindeville on 7/15/2008 12:22 AM:
|
| Well, it kind of begs the question: if ac_sizeof_long_long_int !=
| ac_sizeof_long_long_unsigned_int, then what happens when you assign a
| LONGLONG_MAX to a signed long long, and then copy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Philip Prindeville on 7/15/2008 1:06 AM:
|
| How hard would it be to parse out the type, and generate a warning for
| anything other than the canonical name for a given intrinsic type?
Because it is not a trivial patch, and no one has
Eric Blake [EMAIL PROTECTED] writes:
C allows for difference in size between unsigned and signed
counterparts
C99 doesn't.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B
Eric Blake [EMAIL PROTECTED] writes:
At one point, I proposed modifying autoconf to require both types, or else
claim that neither type exists, because there was an actual platform
(Tandem/NSK) reported by Matthew Woehlke that actually had 32-bit unsigned
long long and 64-bit long long. Paul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[Please send mails to an appropriate list, rather than a single developer]
According to Takis Psarogiannakopoulos on 7/15/2008 12:48 PM:
| Hi there,
| This may sound a bit naive but I am at a loss with the new autoconf
| 2.62 scrips. First of all
12 matches
Mail list logo