On Friday, May 31, 2002, at 10:15 PM, Ben Hines wrote:
> At 7:58 PM -0400 5/31/02, Jeremy Erwin wrote: >> >> Is there a way to get fink to properly expand $(CC) ? i.e >> SetCPP: $(CC) -E -traditional-cpp >> does not seem to work; it's flagged as "not sane" by configure-- the >> shell variable does not correctly expand. > > > CC is really just supposed to be the name of the compiler app.. flags > go in CFLAGS/CPPFLAGS. > CPPFLAGS are not used in the (problematic part of the) build process. Yes, I could add in the appropriate hooks, but I'm trying to keep my patch file small, and understandable. It may be a futile effort... More philosophically: At that stage of the build process, the precompiler is used to construct source code files from script files. On a Next, or on a MacOS machine, "gcc -E" is a more elaborate program than "gcc -E" on linux. To get the same limited functionality as the linux's "gcc -E", macos users have to use "gcc -E -no-cpp-precomp". Since the preprocessor can be called without CPPFLAGS, the most compatible option seems to be CPP="cc -E -no-cpp-precomp". > -traditional-cpp is deprecated, -no-cpp-precomp is its replacement. See > http://fink.sourceforge.net/doc/porting/basics.php > -no-cpp-precomp seems to work ok. Changed. Jeremy _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
