This brilliant code:
CFLAGS="`echo $(CFLAGS) | sed -e 's/-g//g' -e 's/-W[^ ]*//g'`" \
In the GL and GTK Makefile.in's don't do what you'd want them to do when your directory is named, for example:
/mnt/disk3/src/pike/7.4/build/linux-2.4.20-gaming-r3-i686
What are the reasons for the forced removal of -g and other stuff anyway?
According to the CVS log, it was an "Attempt at fixing a few warnings." I have no idea whether it succeeded. Looks rather strange to me.
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Previous text:
2003-06-01 08:54: Subject: '-g' is forbidden in paths...
This brilliant code:
CFLAGS="`echo $(CFLAGS) | sed -e 's/-g//g' -e 's/-W[^ ]*//g'`" \
In the GL and GTK Makefile.in's don't do what you'd want them to do when your directory is named, for example:
/mnt/disk3/src/pike/7.4/build/linux-2.4.20-gaming-r3-i686
What are the reasons for the forced removal of -g and other stuff anyway?
/ David Hedbor
It took quite a while to figure it out since the Makefile had all the right flags etc. :-) I say, revert it - warnings aren't fixed by surgically removing all warning flags...
/ David Hedbor
Previous text:
2003-06-01 20:05: Subject: '-g' is forbidden in paths...
According to the CVS log, it was an "Attempt at fixing a few warnings." I have no idea whether it succeeded. Looks rather strange to me.
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Agreed.
/ Henrik Grubbström (Lysator)
Previous text:
2003-06-01 20:28: Subject: '-g' is forbidden in paths...
It took quite a while to figure it out since the Makefile had all the right flags etc. :-) I say, revert it - warnings aren't fixed by surgically removing all warning flags...
/ David Hedbor
pike-devel@lists.lysator.liu.se