Age | Commit message (Expand) | Author | Files | Lines |
---|---|---|---|---|
2004-02-02 | If we need a GCC C++ or Fortran compiler, then define USE_GCC_SHLIBS as | jlam | 1 | -1/+6 |
2004-02-02 | Rename _GCC{2,3}_REQD to _NEED_GCC{2,3} which more clearly expresses what | jlam | 1 | -7/+7 |
2004-02-02 | Support a new variable in package Makefiles: | jlam | 1 | -17/+30 |
2004-02-01 | Fix a broken conditional. | jlam | 1 | -3/+3 |
2004-02-01 | Use the gcc3-* packages instead of gcc3. The former are newer, and using | jlam | 1 | -16/+50 |
2004-02-01 | Use _GCC_REQD where we want the strictest value (GCC_REQD can be a list). | jlam | 1 | -2/+2 |
2004-02-01 | Actually, it does matter what _GCC_PKG is set to as it's re-used later as | jlam | 1 | -7/+3 |
2004-02-01 | Prepend the path to the compiler to PATH even if we're using the builtin | jlam | 1 | -1/+6 |
2004-02-01 | We're included by bsd.prefs.mk, so no need to include bsd.prefs.mk for | jlam | 1 | -3/+1 |
2004-02-01 | New compiler specification framework, based on mk/compiler.mk. The | jlam | 1 | -0/+224 |