From owner-freebsd-ports Thu Jun 14 0:11:23 2001 Delivered-To: freebsd-ports@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id 833B937B408 for ; Thu, 14 Jun 2001 00:11:15 -0700 (PDT) (envelope-from pfeifer@dbai.tuwien.ac.at) Received: from deneb (deneb [128.130.111.2]) by vexpert.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f5E7BAL22923 for ; Thu, 14 Jun 2001 09:11:13 +0200 (MET DST) Date: Thu, 14 Jun 2001 09:11:10 +0200 (CEST) From: Gerald Pfeifer To: Subject: Port build machinery, ${.CURDIR}, and AMD Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The Makefiles of the the port build machinery use ${.CURDIR} when deriving the pathname used for temporary files. This is fine, but causes undesired effects on systems where the port sources reside on a server mounted by AMD: /sw/FreeBSD/ports (logical path) then becomes /.amd_mnt/spica/work/pfeifer/FreeBSD/ports (physical path) and the build stuff is put into $WRKDIRPREFIX/.amd_mnt/spica/work/pfeifer/FreeBSD/ports which I consider rather bad from a user's point of view (especially given the directory name starting with a leading dot). In a shell script I'd just use `pawd' instead of `pwd', but is there something equivalent for ${.CURDIR}? Other possible fixes? Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message