From owner-freebsd-ports-bugs@FreeBSD.ORG Tue Apr 22 10:20:04 2003 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB95437B401 for ; Tue, 22 Apr 2003 10:20:04 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 406D743F85 for ; Tue, 22 Apr 2003 10:20:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h3MHK3Up032260 for ; Tue, 22 Apr 2003 10:20:03 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h3MHK3kd032256; Tue, 22 Apr 2003 10:20:03 -0700 (PDT) Date: Tue, 22 Apr 2003 10:20:03 -0700 (PDT) Message-Id: <200304221720.h3MHK3kd032256@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Anton Berezin Subject: Re: ports/51283: expat2 port fails to configure X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Anton Berezin List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Apr 2003 17:20:05 -0000 The following reply was made to PR ports/51283; it has been noted by GNATS. From: Anton Berezin To: Charles Swiger Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: ports/51283: expat2 port fails to configure Date: Tue, 22 Apr 2003 19:16:33 +0200 On Tue, Apr 22, 2003 at 09:40:16AM -0700, Charles Swiger wrote: > Good call, Anton: I don't define $UNAME in /etc/make, but I do have > it set in my shell startup scripts-- unsetting it is a valid > workaround to the bug. > > That being said, I've been setting $UNAME to `uname -s` for about > fifteen years for reasons which continue to be valid to me. > ./configure should unset $UNAME if it can't deal with that being set > to a reasonable value, or at least issue a warning. I am not quite sure it is feasible. Configure script of a particular port has very little to do with it. The actual culprit is the line UNAME?= /usr/bin/uname at /usr/ports/Mk/bsd.port.mk. ${UNAME} is being used by the ports collection infrastructure to determine several important variables, among them, ARCH and OSREL. Both of those are used by the textproc/expat2 port, as well as by many other ports. In particular, expat2 uses them to construct certain parameters then passed to the configure script. The majority (hopefully, all) of the binaries used by the ports collection has corresponding make variables, for example LS, ID, FIND, and so on. I am not sure that changing this practice to adjust to habits of a single FreeBSD user is a good idea. That said, there are several possible solutions for you. One is to actually *define* a UNAME make variable to be /usr/bin/uname in your /etc/make.conf. Due to the way make(1) operates, it will ignore your shell UNAME variable in this case. In this way you will still have UNAME to be whatever it is you like it to be in the SHELL, but not inside makefiles. Another possibility, which I do not personally like, is to modify bsd.port.mk to use, for instance, UNAME_CMD instead of UNAME. Please tell me whether the first solution is good enough for you, I'll close this PR is this case. Otherwise, it should be assigned to portmgr, and though I cannot speak for them, I am pretty sure that it will be closed after a brief period without actually modifying bsd.port.mk. Cheers, +Anton. -- Perl is strongly typed, it just has very few types. -- Dan Sugalski