| Summary: | -stable 'make release' does not work on -current environment | ||
|---|---|---|---|
| Product: | Base System | Reporter: | Makoto Matsushita <matusita> |
| Component: | bin | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | CC: | jkh |
| Priority: | Normal | ||
| Version: | 4.0-CURRENT | ||
| Hardware: | Any | ||
| OS: | Any | ||
GNATS admin, please close this PR. I was a young boy when I sent this PR. There is a very way to solve the problem. That is, "write your own shell script to adapt such situations." No helps are needed :-) -- - Makoto `MAR' MATSUSHITA State Changed From-To: open->closed If this problem still exists, please use the freebsd-current@freebsd.org mailing list to discuss these matters. PRs should be used only for STABLE and RELEASE (i.e. non-current) problems. |
src/release/Makefile (both -stable and -current) says: DISTRIBUTIONS?= ${BIN_DISTS} ${OTHER_DISTS} ${COMPAT_DISTS} ${CRYPTO_DISTS} and environment variable 'DISTRIBUTIONS' is defined before running make under chroot-ed environment. However, this situation isn't happy for building a -stable on -current environment. 'DISTRIBUTIONS' definition is different each other (krb4 and compat3x is only for -current, and krb is only for -stable), so such 'make release' should be failed. I want to build both -stable/-current in a same host, and I think it is reasonable if building environment is -current. Fix: I don't know it is the right fix, but a proposal: Stop defining 'DISTRIBUTIONS' environment variable in a shell script for release engineering. Both -stable/-current of src/release/Makefile should be modified to do so. How-To-Repeat: try to 'make release' to build -stable on -current machine.