Commits : Individual Commit
Analyzed about 1 month
ago based on code collected about 1 month ago.
Commit ID f8a7506473aa7a5a8f1871d5af183ad368d5e9be
|
Contributor: | John Marino | Files Modified: | 1 |
| Date: | 29-October-2012 at 19:59 | Lines Added: | 0 | |
| Repository: | git://git.dragonflybsd.org/dragonfly.git master | Lines Removed: | 0 | |
| Commit Comment: | Fix cross-build The introduction of BTOOLMAKE and BTOOLCONFIG did not work when cross-building. The value of BTOOLSDEST and CTOOLSDEST change when starting stage 2 of the crossworld. This was never detected before because these variables were only used in stage 1. However, the absolute path to these tools aren't needed. The PATH is defined in the environment to ensure the bootstrap tools are used when appropriate. Previous errors leading me to think the host tool was being used may have been caused by other things. At the same time, all the "${MAKE}" variables were replaced with "make". The make program defines "MAKE" as whatever was used to invoke it, including paths. Since we are controlling the path, we don't want any surprises. In any cases, we want "${MAKE}" to equal "make", so just hardcode it that way. Tested on cross-build, bmake-equipped system, and legacy make equipped system. |
|||
Changes by Language
No code was detected in this commit.
Changes by File
Showing page 1 of 1
| File | Language | Code Added | Code Removed | Comments Added | Comment Removed | Blanks Added | Blanks Removed | |
|---|---|---|---|---|---|---|---|---|
| Makefile.inc1 | No source code was detected in this file. | |||||||
Copyright
©
2013
Black Duck Software, Inc.
and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a
Creative Commons Attribution 3.0 Unported License
. Ohloh
®
and the Ohloh logo are trademarks of
Black Duck Software, Inc.
in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.