public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: "Capuano, Al" <capuano@rowan.edu>
Cc: "'gcc-help@gcc.gnu.org'" <gcc-help@gcc.gnu.org>
Subject: Re: GCC installation
Date: Sat, 29 Sep 2001 10:30:00 -0000	[thread overview]
Message-ID: <or7kuhlxh6.fsf@localhost.localdomain> (raw)
In-Reply-To: <F6188F0E7871D51192AB0002A56B8A4C08C278@exchange55.rowan.edu>

On Sep 27, 2001, "Capuano, Al" <capuano@rowan.edu> wrote:

> 				run ./configure - -prefix=/usr/local/gcc301 
                                    ^

The installation instructions recommend using a separate build
directory.  Create build and run /path/to/configure ..., and it will
work.  But use a full pathname when running configure.

The problem you've encountered is a symptom of a bug that is already
fixed for 3.0.2.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

  reply	other threads:[~2001-09-29 10:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-27 11:02 Capuano, Al
2001-09-29 10:30 ` Alexandre Oliva [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-04 16:35 GCC Installation Fan, Fenghui 
2006-07-04 16:52 ` Marco Trudel
2003-12-15 18:40 gcc installation lrtaylor
2003-12-15 18:31 Pranav Sharma, Noida
2003-12-16  4:19 ` Bharathi S
2001-02-01  6:08 GCC installation jsauerborn
2001-01-20  8:30 gcc installation winimuell
2000-03-20  5:50 Premson P R
2000-03-20 11:22 ` Alexandre Oliva
2000-04-01  0:00   ` Alexandre Oliva
2000-04-01  0:00 ` Premson P R

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=or7kuhlxh6.fsf@localhost.localdomain \
    --to=aoliva@redhat.com \
    --cc=capuano@rowan.edu \
    --cc=gcc-help@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).