[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug in autoconf deb v 2.13-25?
From: |
Christopher Gorman |
Subject: |
bug in autoconf deb v 2.13-25? |
Date: |
Wed, 28 Feb 2001 18:15:31 -0500 (EST) |
Hey,
I have found what I think to be a bug in the debian autoconf package
v2.13-25.
The problem that I have occurs when I use the AC_C_CONST macro. I've
attached the code that both 2.13-23 and 2.13-25 generated when the
AC_C_CONST macro was defined in my configure.in. The following is a diff
between the two pieces of generated C code.
phantom:~$ diff -uN conftest-2.13-23.C conftest-2.13-25.C
--- conftest-2.13-23.C Wed Feb 28 14:43:28 2001
+++ conftest-2.13-25.C Wed Feb 28 17:22:48 2001
@@ -3,7 +3,7 @@
int main() {
/* Ultrix mips cc rejects this. */
-typedef int charset[2]; const charset x = {0,0};
+typedef int charset[2]; const charset x;
/* SunOS 4.1.1 cc rejects this. */
char const *const *ccp;
char **p;
This syntax error causes gcc to fail, with
phantom:~$ gcc -c conftest-2.13-25.C
conftest-2.13-25.C: In function `int main()':
conftest-2.13-25.C:6: uninitialized const `x'
which causes the config.status file to add a -Dconst to the
address@hidden@%-Dconst= %g
regexp which causes all the const(s) in the build to be redefined as
nothing.
Thanks
Chris
-----------------------------------------------------------------------------
Chris Gorman
Software Developer - Corel Corporation
--
Boundless power to create. Anytime. Anywhere. Share Corel's vision.
Visit our Web site at http://www.corel.com.
conftest-2.13-25.C
Description: Text document
conftest-2.13-23.C
Description: Text document
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug in autoconf deb v 2.13-25?,
Christopher Gorman <=