Follow-up Comment #9, bug #45081 (project gnustep):
let's separate two issues
1) all the libraries (but all programs) should be compiled consistently. make
remembers your compiler usually, it is configure that needs to be hinted. That
is just correct or you end up with a mess. I fixed that in gui, back and
GWorkspace now
2) you may provide an alternate CC and it takes precedence, thus what you pass
as variables gets respected, we just set a more sensible default!
3) there is a check in base, which I copied to the other projects too which
checks that the current compiler is the same as of make.
MAKECC=`gnustep-config --variable=CC`
if test "$CC" != "$MAKECC"; then
AC_MSG_ERROR([You are running configure with the compiler ($CC) set to a
different value from that used by gnustep-make ($MAKECC). Please run
configure again with your environment set to match your gnustep-make])
exit 1
fi
I think 1) and 2) are just sensible points. 3) is actually helping not to
shoot in your feet but it is a hinderance to power users like Matt. You might
be running "gcc" vs "gcc-beta" knowing yourself that they generate compatible
code.
should the check be removed? or perhaps it can be made a warning? We can
change it to AC_MSG_WARN what do you think?
for the average user everything should be fine, but Matt can do his special
tricks too.
_______________________________________________________
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
