Date: Sat, 02 Oct 1999 03:55:11 +0900 From: Makoto MATSUSHITA <matusita@jp.FreeBSD.org> To: FreeBSD-gnats-submit@freebsd.org Cc: jkh@freebsd.org Subject: bin/14078: -stable 'make release' does not work on -current environment Message-ID: <19991002035511U.matusita@jp.FreeBSD.org>
next in thread | raw e-mail | index | archive | help
>Number: 14078
>Category: bin
>Synopsis: -stable 'make release' does not work on -current environment
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Fri Oct 1 12:00:01 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator: Makoto MATSUSHITA
>Release: FreeBSD 4.0-CURRENT i386
>Organization:
Japan FreeBSD Users' Group
>Environment:
current 4.0-CURRENT
>Description:
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.
>How-To-Repeat:
try to 'make release' to build -stable on -current machine.
>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.
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991002035511U.matusita>