David E. O'Brien 7b4716843d Use MD_EXEC_PREFIX now to get us thru `buildworld'. ... The problem is the GCC driver now turns STANDARD_EXEC_PREFIX into a relative path -- "<basename argv[0]>/../../libexec" for our normal install location. However, in the middle of `buildworld' we need "<basename argv[0]>/../../../../libexec" due to the prefix we tell the GCC driver. But either the GCC driver is buggy, or we are confusing it, as it tries to exec "<basename argv[0]>/../../libexec/cpp0" as if it were installed in the normal place (but isn't). MD_EXEC_PREFIX is still absolute, so I'll use that for now. I would like to later make it so MD_EXEC_PREFIX is set only for `buildworld', as MD_EXEC_PREFIX is also in the search path for libraries. Don't ask me why! Another way is to add ${OBJFORMAT_PATH} (as set in CROSSENV) to the PATH in src/Makefile.inc's WMAKEENV.		2002-05-10 08:41:46 +00:00
..
lib	Mostly filled in contents for GCC 3.1.	2002-05-07 01:16:04 +00:00
usr.bin/cc	Use MD_EXEC_PREFIX now to get us thru `buildworld'.	2002-05-10 08:41:46 +00:00
Makefile	Make life a little bit easier with a trimmed down list of bits.	2002-05-06 21:10:08 +00:00