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, 30 Dec 2002 07:06:00 -0000 [thread overview] Message-ID: <20021230150601.17084.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: "Phil Edwards" <phil@jaj.com> Cc: <gcc-gnats@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, 30 Dec 2002 10:02:26 -0500 Phil, You write: > > Did you see the installation instructions regarding > > 1) strongly recommending building in a seperate directory, and I'm not sure what you mean. I built gcc-3.2.1 in a separate directory. Do you mean I should have built only gcc/intl in a separate directory? Where are those instructions? > 2) special steps for Solaris systems? I read everything I could find under Solaris (any case) in the configure.html and build.html files. Where else should I have looked? > If you didn't, please try again after doing so, and let us know > whether you > still experience problems. I don't find anything I should change in the way I built gcc-3.2.1, but I may be missing some references. Could you please identify those? Vic
next reply other threads:[~2002-12-30 15:06 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-30 7:06 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-19 13:56 Vic Abell 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 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=20021230150601.17084.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: linkBe 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).