On Sun, Feb 23, 2003 at 08:58:32PM -0500, Fred Heitkamp wrote: >>>Note I know I could just make a symbolic link to get rid of the error, >>>but that's not my question. > >>The top level Makefile refers to $(CC), and I guess your version of >>make defines it to >>"/usr/bin/cc". An alternative to creating the symlink is to run 'make >>CC=<your-cc-command> World', or find out how to change make's default (if >>possible). > >I tried setting CC and BOOTSTRAPCFLAGS and neither gets rid of >the problem completely. I also have a problem with /usr/bin/cpp >being hard coded in various places.
Have you been able to isolate where the references to /usr/bin/cc are coming from then if it isn't from $(CC)? >I complain about this because I often use different compiler >versions. I would rather just set the PATH to point to the >directiry of the compiler in use for cpp, gcc, etc. Traditionally cpp hasn't alwasy been in $PATH (e.g., /lib/cpp). I ran into a problem with a RH 5.2 test build where /lib/cpp exists, but not /usr/bin/cpp (and linux.cf now refers to the latter). >I see in the imake.c and imakemdep.h that /usr/bin/cpp is >being hard-coded into the executables. Also many of the >Makefiles, presumably they are being constructed via imake, >contain this hard-coded path. Maybe someone better informed >than me can comment on this. imakemdep.h hard-codes it for some platforms. For platforms where a suitable cpp can reasonably be exptected to be available in $PATH, the full path doesn't have to be specified there. A lot of platforms use 'cc -E'. David -- David Dawes Release Engineer/Architect The XFree86 Project www.XFree86.org/~dawes _______________________________________________ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
