Re: bootstrap/5634: ../configure --prefix=~/... doesn't work

Re: bootstrap/5634: ../configure --prefix=~/... doesn't work

[bje]

Synopsis: ../configure --prefix=~/... doesn't work

Responsible-Changed-From-To: unassigned->bje
Responsible-Changed-By: bje
Responsible-Changed-When: Tue Feb 18 03:09:53 2003
Responsible-Changed-Why:
    Got it.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5634

Re: bootstrap/5634: ../configure --prefix=~/... doesn't work

[Phil Edwards]

The following reply was made to PR other/5634; it has been noted by GNATS.

From: Phil Edwards <phil@jaj.com>
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

Re: bootstrap/5634: ../configure --prefix=~/... doesn't work

[bje]

Synopsis: ../configure --prefix=~/... doesn't work

State-Changed-From-To: open->analyzed
State-Changed-By: bje
State-Changed-When: Tue Feb 18 04:12:02 2003
State-Changed-Why:
    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?
    
    I tend to use --prefix=$HOME/install with success.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5634

bootstrap/5634: ../configure --prefix=~/... doesn't work

[tom]

>Number:         5634
>Category:       bootstrap
>Synopsis:       ../configure --prefix=~/... doesn't work
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Feb 08 04:06:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Thomas Womack
>Release:        gcc-3.1-{20011231, 20020204} at least
>Organization:
>Environment:
SuSE 7.3; bash 2.05 as shipped by SuSE
>Description:
Configuring with --prefix=~/somewhere --program-suffix=something gives a built version which does not install properly.

Specifically, "make install" fails with an error in installing libiberty.a, and leaves directories called "~" lying around.
>How-To-Repeat:
make two copies of the gcc distribution, configure one with --prefix=~/foo and one with --prefix=/home/twomack/foo, build both; the first won't install, the second will.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: