From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Luc Teirlinck Newsgroups: gmane.emacs.devel Subject: Re: make bootstrap fails. Date: Wed, 4 Feb 2004 13:36:53 -0600 (CST) Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <200402041936.i14Jaru03370@raven.dms.auburn.edu> References: <200401301902.16714.hattons@speakeasy.net> <87isirsx88.fsf@emptyhost.emptydomain.de> <200402012052.i11Kq6525375@raven.dms.auburn.edu> <87n0825vic.fsf@emptyhost.emptydomain.de> <200402012208.i11M8OI25458@raven.dms.auburn.edu> <200402032205.i13M58V01271@raven.dms.auburn.edu> <200402041521.i14FL5x02633@raven.dms.auburn.edu> NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1075924519 17588 80.91.224.253 (4 Feb 2004 19:55:19 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 4 Feb 2004 19:55:19 +0000 (UTC) Cc: kai@emptydomain.de, rms@gnu.org, storm@cua.dk, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Wed Feb 04 20:55:09 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AoT76-0005U3-00 for ; Wed, 04 Feb 2004 20:55:08 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AoT76-0000Xj-00 for ; Wed, 04 Feb 2004 20:55:08 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AoSwX-0000S5-0G for emacs-devel@quimby.gnus.org; Wed, 04 Feb 2004 14:44:13 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AoSr4-0007XS-Uv for emacs-devel@gnu.org; Wed, 04 Feb 2004 14:38:34 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AoSqY-0007Je-0M for emacs-devel@gnu.org; Wed, 04 Feb 2004 14:38:33 -0500 Original-Received: from [131.204.53.104] (helo=manatee.dms.auburn.edu) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AoSq1-00076o-Ew; Wed, 04 Feb 2004 14:37:29 -0500 Original-Received: from raven.dms.auburn.edu (raven.dms.auburn.edu [131.204.53.29]) by manatee.dms.auburn.edu (8.12.10/8.12.10) with ESMTP id i14JbCKt000419; Wed, 4 Feb 2004 13:37:12 -0600 (CST) Original-Received: (from teirllm@localhost) by raven.dms.auburn.edu (8.11.6+Sun/8.11.6) id i14Jaru03370; Wed, 4 Feb 2004 13:36:53 -0600 (CST) X-Authentication-Warning: raven.dms.auburn.edu: teirllm set sender to teirllm@dms.auburn.edu using -f Original-To: jan.h.d@swipnet.se In-reply-to: (jan.h.d@swipnet.se) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:19713 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:19713 There would seem to be four possibilities: 1. CDPATH= 2. export CDPATH= 3. use the shell command `unset CDPATH' at various places all over Makefile.in. 4. systematically do `cd ./dir' rather than `cd dir' at every single occurrence of cd in all Makefiles. That includes the case where dir is a variable expanding to a relative name. Clearly, 3 and 4 require both some initial work and carefulness when subsequently making changes to the Makefile. So I believe they should only be considered if we agreed that both 1 and 2 are too simplistic. Note also that, even without any change, problems only develop with a user CDPATH _not starting with a colon_. Personally, I would not want to be using such a CDPATH and certainly not export it, because it seems like a dangerous thing to do. Richard has already stated that he does not believe that the problem is worth a substantial amount of work. There are currently no instances of use of the make `export' directive in Makefile.in. Maybe it was avoided because some make's do not understand it. Hence I am afraid that (2) might break some make's even if CDPATH is unset. Maybe somebody can assure me that this fear is groundless. (1) definitely seems to work for GNU make and might work for other makes, maybe even all makes. Importantly, it will not make the situation _worse_ for _any_ make. On the other hand (3) is used at some (but not enough) places in Makefile.in already, so maybe (1) will not solve the problem for _all_ makes. What if I just go ahead and install my trivial "CDPATH=" change, which as already said, at least will do no harm and at least some good? Then we can always decide what to do if problems persist for some non GNU make's, say maybe clearmake. (Maybe add `export' or maybe go for (3).) People with possibly problematic make's can always experiment by making directories, say ~/cdpath and ~/cdpath/src and doing `export CDPATH=~/cdpath" before bootstrapping or using other instances of make. (Of course, do not forget to set CDPATH back afterwards.) Sincerely, Luc.