public inbox for
help / color / mirror / Atom feed
From: "Robert W. Hasker" <>
Subject: Re: bootstrap/7553: install problem on alpha axp with gcc-3.1.1
Date: Tue, 20 May 2003 02:06:00 -0000	[thread overview]
Message-ID: <> (raw)

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

From: "Robert W. Hasker" <>
Subject: Re: bootstrap/7553: install problem on alpha axp with gcc-3.1.1
Date: Mon, 19 May 2003 20:57:41 -0500 (CDT)

    there are/were a number of issues building gcc inside the source  
    directory. Note that this should currently work, but it is not tested  
    very much. Can the submitter of this report please verify if this  
    problem exists with more current versions of gcc (ie 3.2.3). Thanks,
 Yes, the problem with install-sh not being found is still there when
 building version 3.2.3.  I have not tested version 3.3 (which came out
 since I started rebuilding gcc).  I don't believe the problem is related to
 building gcc "inside the source directory" - the structure I used then was
   source files in /usr2/sys/usr/local/src/gcc/gcc-3.2.2
   build directory in /usr2/sys/usr/local/src/gcc/build322
 (as reported by /bin/pwd as opposed to "echo $cwd").  When trying to build
 version 3.2.3, I ran into the path-too-long error (see bootstrap/7555) and
 so moved to a new build directory (with the source directory the same):
 This time I found a different fix: I edited
 and changed the line
 INSTALL = ../../gcc/gcc-3.2.3/gcc/../install-sh -c
 INSTALL = ../../../gcc/gcc-3.2.3/gcc/../install-sh -c
 (note the extra "../" in the front).  "make install" then completed with no
 Let me know if you'd like the output from configure, make bootstrap, or
 make install.

             reply	other threads:[~2003-05-20  2:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-20  2:06 Robert W. Hasker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-08 10:42 giovannibajo
2003-05-08  4:36 Dara Hazeghi
2002-08-09  7:36 Robert W. Hasker

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:

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

  git send-email \ \ \ \ \

* 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).