Sir Raorn wrote: > On Tue, May 14, 2002 at 12:43:56PM +0400, Markus Hitter wrote: > >>But isn't GNUstep expected to have the name of the compiler >>hardwired somewhere in $GNUSTEP_SYSTEM_ROOT? Then, configure >>should use this name, too, IMHO. >> > If it will set CC, than answer is NO WAY! > > >>As there is a easy workaround, I'll look for a patch later. >> > GNUstep.sh: > export GNUSTEP_CC=gcc3 # (defined at compile time) > > configure[.in]: > if [ -n "$GNUSTEP_CC" ]; then > CC=$GNUSTEP_CC > fi > > For example... > >
Well that would work for CC, but what if the user wanted to set something else? CFLAGS, or LD, or any number of things. In general (and the docs state this), when configuring the gnustep libraries, you need to pass the same configure options to configure for each library. There's no way in general to know which configure options were given to configure. -- Adam Fedor, Digital Optics Corp. | I'm glad I hate spinach, because http://www.doc.com | if I didn't, I'd eat it, and you | know how I hate the stuff. _______________________________________________ Bug-gnustep mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gnustep
