I found this problem when I tried to use CFLAGS to turn of optimization to help me in debugging during development.
The following works (and is the GNU standard way of doing things, so this is not a very urgent problem to fix): ./configure CFLAGS="-O0 -g"
The output is:
You are compiling MARX with the following compiler configuration:
CC = gcc
CFLAGS = -O0 -g
LDFLAGS =
and indeed I get the code I requested.
However, if I set the CFLAGS enviroment varible, then the output of configure is exactly the same, but the CFLAGS that's actually used in the Makefiles is different (just the default value).
This might not be worth fixing on it's own. Instead it might be more time-efficient to just change the whole installation to use the entire autotools stack instead of hand-writing configure.in.
I found this problem when I tried to use CFLAGS to turn of optimization to help me in debugging during development. The following works (and is the GNU standard way of doing things, so this is not a very urgent problem to fix):
./configure CFLAGS="-O0 -g"
The output is:and indeed I get the code I requested. However, if I set the CFLAGS enviroment varible, then the output of
configure
is exactly the same, but the CFLAGS that's actually used in the Makefiles is different (just the default value).This might not be worth fixing on it's own. Instead it might be more time-efficient to just change the whole installation to use the entire autotools stack instead of hand-writing configure.in.