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.
This commit is contained in:
David E. O'Brien
2002-05-10 08:41:46 +00:00
parent dd7731cf37
commit 7b4716843d
+1 -1
View File
@@ -32,7 +32,7 @@
*/
#undef TOOLDIR_BASE_PREFIX /* Old?? This is not documented. */
#define STANDARD_EXEC_PREFIX PREFIX"/libexec/"
#undef MD_EXEC_PREFIX /* We don't want one. */
#define MD_EXEC_PREFIX PREFIX"/libexec/"
/* Under FreeBSD, the normal location of the various *crt*.o files is the
/usr/lib directory. */