From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16451 invoked by alias); 18 Feb 2003 04:26:00 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 16438 invoked by uid 71); 18 Feb 2003 04:26:00 -0000 Date: Tue, 18 Feb 2003 04:26:00 -0000 Message-ID: <20030218042600.16437.qmail@sources.redhat.com> To: bje@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Phil Edwards Subject: Re: bootstrap/5634: ../configure --prefix=~/... doesn't work Reply-To: Phil Edwards X-SW-Source: 2003-02/txt/msg00764.txt.bz2 List-Id: The following reply was made to PR other/5634; it has been noted by GNATS. From: Phil Edwards To: bje@gcc.gnu.org, gcc-bugs@gcc.gnu.org, tom@womack.net, gcc-gnats@gcc.gnu.org Cc: Subject: Re: bootstrap/5634: ../configure --prefix=~/... doesn't work Date: Mon, 17 Feb 2003 23:23:56 -0500 On Tue, Feb 18, 2003 at 04:12:02AM -0000, bje@gcc.gnu.org wrote: > This is due to an inconsistent interaction with your shell, viz: > > $ echo prefix=~/install > prefix=/home/bje/install > $ echo --prefix=~/install > --prefix=~/install > > Note that the ~ is expanded correctly in the first, but not the second. > It is unreasonable to expect all underlying GCC configury to handle ~ > as a special case. At the very least, this should be documented in the > installation documentation--do you agree? FYI, bash understands ~ as the first character in sub-words, such as this. But csh and tcsh only understand ~ as the first character in a main word, i.e., after whitespace. This isn't specific to us, so I wouldn't bother documenting it. Anybody who uses a csh-family shell is going to run into these weird features eventually. If you do feel like documenting it, I suggest providing a link to a "here's an introduction to csh" page somewhere. Phil -- I would therefore like to posit that computing's central challenge, viz. "How not to make a mess of it," has /not/ been met. - Edsger Dijkstra, 1930-2002