On Sun, 31 Dec 2000 15:21:13 +0100, Karsten Jensen wrote:
>In lesstif-0.92.6 is some bugs in configure.in and acinclude.m4, which
>gives unexpected values for CFLAGS. My system is Redhat linux 6.1, and
>my compiler i gcc. I ran the configure script and got
>CFLAGS = -g -O2 -I/usr/X11R6/include -g, but what i expected was
>CFLAGS = -g -Wall. The errors i found in configure.in is:
>1) The check for compileflags should be after AC_PROG_CC. If not you
> can't know if you is using gcc.
Well, I have used configure to get builds with non-gcc.
However I often use CFLAGS in environment, etc. so this
is no full-featured test. To my experience the current configure
was much better in keeping my specified CFLAGS than earlier
versions ...
>2) When you saves CFLAGS you uses an variable lt_save_CFLAGS, but the
> same variable is used in several of the macros in acinclude.m4 -
> thus making it impossible to restore CFLAGS again.
>
>In acinclude.m4 is there some errors in LT_HAVE_GETHOSTNAME:
>1) AC_TRY_LINK does only take 4 arguments.
>2) The lines where CFLAGS, CPPFLAGS and LIBS get restored is
> misplaced. If the macro get its value from the cache the variables
> is restored without beeing saved first.
>
>AM_FUNC_VOID_SPRINTF is also broken, as it dumps core on my
>system. The sprintf function is called with only one argument, which
>is wrong.
>
>I have made a new version of AM_PROG_CC_STDC, which may give the right
>compile-flags for SCO-unix.
>
>New version of AM_PROG_CC_STDC:
>
[...]
Thanks!
I will give those a try. Well, not all: the VOID-SPRINTF test will be dropped
completly, we demand an ANSI C environment anyway.
---
Alexander Mai
[EMAIL PROTECTED]
