Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 May 2002 01:41:47 -0700 (PDT)
From:      "David E. O'Brien" <obrien@FreeBSD.org>
To:        cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   cvs commit: src/gnu/usr.bin/cc/cc_tools freebsd-native.h
Message-ID:  <200205100841.g4A8flG31979@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
obrien      2002/05/10 01:41:46 PDT

  Modified files:        (Branch: WIP_GCC31)
    gnu/usr.bin/cc/cc_tools freebsd-native.h 
  Log:
  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.
  
  Revision  Changes    Path
  1.9.2.7   +1 -1      src/gnu/usr.bin/cc/cc_tools/freebsd-native.h

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200205100841.g4A8flG31979>