On 05 Jul 2003 12:08:25 +0200, Harald Dunkel wrote:
I would suggest to use "cc -E $CFLAGS" instead of "cc -E" during configure. $CFLAGS might contain some -I flags pointing to include directories to search for xpm.h or png.h, for example.
What is the actual problem?
The problem was that configure wasn't smart enough to find xpm.h and some other headers, even though CFLAGS contained "-I/usr/local/include" pointing to the right directory.
I have no time to test it now, but I would think all of these may work:Currently I am using
CFLAGS="-O5 -g" ./configure --something CC="cc -E -O5 -g" ./configure --something ./configure --something CFLAGS="-O5 -g" ./configure --something CC="cc -E -O5 -g"
export IMLIBCONF=/usr/local/bin/imlib-config
export GTK_CONFIG=/usr/local/bin/gtk-config
export CFLAGS=-I/usr/local/include
export LDFLAGS"=-L/usr/local/lib -R/usr/local/lib"
export CC="cc $CFLAGS $LDFLAGS"
export CPP="$CC -E"
./configure --prefix=/usr/local/stow/fvwm-2.5.7
makePlease note that I am _not_ using gcc. Standard gcc looks in /usr/local/include by default, even if you installed it somewhere else.
Regards
Harri
-- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
