Follow-up Comment #3, bug #45081 (project gnustep):
I'm inclined to agree with Riccardo.
I'd call it a request for improvement rather than a bug report though.
What base does (I hope) when you run configure:
1. see if you explicitly specified what compiler to use
2. see what compiler gnustep-make was configured to use
3. see what compiler standard autoconf macros can find
That means, if you just run configure for base, it should use the same
compiler that was used when configuring gnustep-make, so all the correct
compiler flags should be found automatically.
If you explicitly specified a compiler that's NOT what gnustep-make was
configured to use, then theres a high chance that incompatibilities will
occur, so it should bomb out with an error message, giving you a chance to
fixup your environment and/or reconfigure gnustep-make for the new compiler.
I guess it's not unreasonable that we might want to put similar
intelligence/error-checking into the gui and back configure scripts.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?45081>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
Bug-gnustep@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gnustep
