Richard Lynch writes: > Direct replies most welcome :-) Presently the easiest way to insure this is to put yourself into Cc: > > /usr/bin/cpp -Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L > -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE > -D_GNU_SOURCE -D__ELF__ -DMALLOC_0_RETURNS_NULL -DGLXEXT -DXF86DRI > -DGLX_DIRECT_RENDERING -DGLX_USE_DLOPEN -DGLX_USE_MESA -DUSE_X86_ASM > -DUSE_MMX_ASM -DUSE_3DNOW_ASM -I../../../../../exports/include > -I../../../../../include/extensions -I../../../../../extras/Mesa/src > -I../../../../../extras/Mesa/src/X86 -I../../../include > common_x86_asm.S | \ > grep -v '^\#' > common_x86_asm.i > /bin/sh: /usr/bin/cpp: No such file or directory
This is surprising. You've been compiling for hours and then you stumble over this. cpp should have been used much earlier. Anyway, I have changed this in the current CVS. It is not a good idea to have the cpp path hard coded. If cpp is installed it should be in the search path. As /usr/bin is in the path anyway it makes no sense having /usr/bin/cpp at all. Try # which cpp If it doesn't come back with anything you don't have your development tools installed - in which case I would be surprised even more that you have been compiling for hours. > > Now is this /bin/sh complaining that there is no /usr/bin/cpp file? > Or is it /usr/bin/cpp complaining that some other un-named file is missing? > Or what? > It's not real clear in the error message. The first option/ > > Since there is no /usr/bin/cpp on this box, I'm betting on the first > interpretation. But error messages should not be subject to > interpretation :-) > Hm, then cpp must be some other place. > > I tried some obvious things, such as just doing "make" in that > directory, and starting all over with "make clean" and "make > distclean" and got the same results. > > Tried it with the WORLDOPTS= thing, and I think I may have tried > "Everything" instead of "World"... No, wait. I didn't try that yet. > Sorry. > > > I even did a Hail Mary and sym-linked the non-existent /usr/bin/cpp > (?) to my /usr/bin/gcc, since, like, GCC is a c-plus-plus compiler, > right? and I can use it instead, right?... cpp is the preprocessor. gcc is the compiler. Calling gcc -E just does preprocessing. However I suppose there is a difference as gcc -E knows about the compiler predefines while cpp shouldn't. To solve your problem you can add: #define CppCmd cpp to your host.def. Egbert. _______________________________________________ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
