Follow-up Comment #1, bug #34658 (project gnustep):
This depends on how you configure gnustep-make. gnustep-make's
configure has the --enable-debug-by-default option. From the
configure documentation:
--enable-debug-by-default
Enable building with 'make debug=yes' by default. When you use
gnustep-make to build software, you have a choice of using
debug=yes or debug=no. The debug=no will use the default compiler
flags determined when gnustep-make was configured (usually -g -O2),
while debug=yes will remove the optimization flags and add a
number of debugging compiler flags. If you do not specify the
--enable-debug-by-default option, gnustep-make will default to
building with debug=no when nothing is specified. If you
specify the --enable-debug-by-default option, gnustep-make will
default to building with debug=yes instead, which can be handy if you
always want to compile software with debug=yes and want to avoid
having to type debug=yes each time you compile (an alternative
is to define the variable debug=yes in your shell). If you are
unsure, you should stick with the default and ignore this option.
So, I suppose in your case you have configured gnustep-make with
the wrong option.
Thanks
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?34658>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-gnustep
