public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Vic Abell" <abe@purdue.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: other/9105: gcc-3.2.1/gcc/intl/Makefile gets incorrect INSTALL variable path
Date: Mon, 19 May 2003 13:56:00 -0000	[thread overview]
Message-ID: <20030519135601.13407.qmail@sources.redhat.com> (raw)

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

From: "Vic Abell" <abe@purdue.edu>
To: "Dara Hazeghi" <dhazeghi@yahoo.com>
Cc: <gcc-gnats@gcc.gnu.org>, <nobody@gcc.gnu.org>,
   "vicabell" <abe@vic.cc.purdue.edu>
Subject: RE: other/9105: gcc-3.2.1/gcc/intl/Makefile gets incorrect INSTALL variable path
Date: Mon, 19 May 2003 08:50:49 -0500

 Dara,
 
 You write:
 >
 > as previously noted, in source builds have had problems in the past.  
 > However, I have yet to experience any with gcc 3.3. Would it be  
 > possible for you to test under gcc 3.3, and determine if this problem  
 > is still present? Thanks,
 
 I configured gcc 3.3 three ways and can't see any difference
 in the results when compared to gcc 3.2.1 configuration.
 
 In my three gcc 3.3 configure runs only one that used an absolute
 path to the configure script in the gcc 3.3 source subdirectory
 from a subdirectory outside gcc-3.3 properly set the INSTALL string
 of .../gcc/intl/Makefile.
 
 The two relative path configure runs I made, in-source and
 relative-to-source, both produced the same incorrect path in the
 INSTALL string of .../gcc/intl/Makefile.
 
 More specifically, here's what I tried:
 
 1. I downloaded gcc-3.3.tar.gz on Thursday May 15.  It has
    these ls and md5 footprints:
 
    -rw-r--r-- 1 abe pucc 31046469 May 15 10:55 gcc-3.3.tar.gz
    MD5 (gcc-3.3.tar.gz) = 59a99a15c24a1519d057a7b94f00e8f2
 
 2. I gunzip'd and extracted the 3.3 archive, changed to the
    extracted directory and ran `./configure ...`.  Here is
    the incorrect INSTALL string from gcc-3.3/gcc/intl/Makefile:
 
 	$ grep "^INSTALL = " gcc/intl/Makefile
 	INSTALL = ./../install-sh -c
 	$ (cd gcc/intl; ls -l ./../install-sh) 
 	./../install-sh: No such file or directory
 
    Note: in addition to `./configure ...` I also tried simply
          `configure ...` and there was no difference in the
          INSTALL string of gcc/intl/Makefile.
 
 3. I gunzip'd and extracted the 3.3 archive again, made a
    gcc-3.3-exrel subdirectory ("exrel" for outside the source
    directory, relative path to configure) and ran
    `./gcc-3.3/configure ...`.  Here is the incorrect INSTALL
    string from gcc-3.3-exrel/gcc/intl/Makefile:
 
 	$ grep "^INSTALL = " gcc/intl/Makefile
 	INSTALL = ../../gcc-3.3/gcc/../install-sh -c
 	$ (cd gcc/intl; ls -l ../../gcc-3.3/gcc/../install-sh)
 	../../gcc-3.3/gcc/../install-sh: No such file or directory
 
 4. I gunzip'd and extracted the 3.3 archive again, made a
    gcc-3.3-exabs subdirectory ("exabs" for outside the source
    directory, absolute path to configure) and ran
    `/export/home/abe/gnu/gcc-3.3/configure ...`.  Here is the
    correct INSTALL string from
    /export/home/abe/gnu/gcc-3.3-exabs/intl/Makefile:
 
 	$ grep "^INSTALL = " gcc/intl/Makefile
 	INSTALL = /export/home/abe/gnu/gcc-3.3/gcc/../install-sh -c
 	$ ls -l /export/home/abe/gnu/gcc-3.3/gcc/../install-sh
 	-rwxr-xr-x 1 abe pucc 5598 Jan 25  2002 \
 	/export/home/abe/gnu/gcc-3.3/gcc/../install-sh*
 
 I have script(1) output for each configure attempt, should you
 want it.
 
 What other information can I supply?
 
 Vic


             reply	other threads:[~2003-05-19 13:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-19 13:56 Vic Abell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-21 11:28 Vic Abell
2003-05-21 10:48 Eric Botcazou
2003-05-21 10:19 Vic Abell
2003-05-21  9:36 Christian Ehrhardt
2003-05-15  4:36 bangerth
2003-05-14 22:06 Dara Hazeghi
2003-05-14 19:46 Dara Hazeghi
2002-12-30  7:16 Phil Edwards
2002-12-30  7:06 Vic Abell
2002-12-30  6:36 Phil Edwards
2002-12-30  5:06 abe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030519135601.13407.qmail@sources.redhat.com \
    --to=abe@purdue.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).