Matching contrib/gcc/gcc.c commit of rev 1.23, remove misleading comment

about 'STANDARD_EXEC_PREFIX'.  It is used now and is needed if one does not
set 'MD_EXEC_PREFIX'.

Do not define a 'MD_EXEC_PREFIX'.  It is not needed, not used in the
cross case, and just ends up causing "/usr/libexec" being added to the
library search path.
This commit is contained in:
David E. O'Brien 2002-03-05 00:39:29 +00:00
parent a370115d7d
commit e4753251f7

View File

@ -28,17 +28,12 @@
``cc --print-search-dirs'' gives:
install: STANDARD_EXEC_PREFIX/(null)
programs: /usr/libexec/<OBJFORMAT>/:MD_EXEC_PREFIX
programs: /usr/libexec/<OBJFORMAT>/:STANDARD_EXEC_PREFIX:MD_EXEC_PREFIX
libraries: MD_EXEC_PREFIX:MD_STARTFILE_PREFIX:STANDARD_STARTFILE_PREFIX
We really don't need a "STANDARD_EXEC_PREFIX". However w/o it,
"--print-search-dirs" reports "install: /usr/local/lib/gcc-lib/(null)".
It is not harmful, but is just plain wrong. So we define a
"STANDARD_EXEC_PREFIX" to not be misleading. */
*/
#undef TOOLDIR_BASE_PREFIX /* Old?? This is not documented. */
#define STANDARD_EXEC_PREFIX PREFIX"/libexec/"
#define MD_EXEC_PREFIX PREFIX"/libexec/"
#define MD_EXEC_PREFIX /* We don't want one. */
/* Under FreeBSD, the normal location of the various *crt*.o files is the
/usr/lib directory. */