public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: AJ <jadeja@cyberspace.org>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Help Needed!
Date: Thu, 27 Jul 2000 21:40:00 -0000	[thread overview]
Message-ID: <or66pqq33r.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: <Pine.SUN.3.96.1000728003103.2631F-100000@grex.cyberspace.org>

On Jul 28, 2000, AJ <jadeja@cyberspace.org> wrote:

>> ../gcc/gcc-2.95.2/configure
> --with-gcc-version-trigger=/home/rcf/test/gcc/gcc-2.95.2/gcc/version.c
> --enable-checking --prefix=.

Are you sure you really need --enable-checking?  It may be detecting
some obscure bug in GCC 2.95.2 that wouldn't affect you in real life,
but that prevents building.

Also, --prefix=. is wrong.  You really want a full pathname here.

> Do i need to have a copy of the assembler and linker in the build
> directory?

No, but, in case you want to use those tools from GNU binutils, you
may follow the procedure in the FAQ to make sure GCC uses them.

> Also do i need to specify with-local-prefix???

Nope.

-- 
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:[~2000-07-27 21:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-27 21:30 AJ
2000-07-27 21:40 ` Alexandre Oliva [this message]
2000-07-27 23:14   ` AJ
2000-07-27 23:37     ` Alexandre Oliva
2000-07-28  0:06       ` AJ
2000-07-28  0:10         ` Alexandre Oliva
2000-07-28 12:36           ` Help Needed!(still stuck..) AJ
2000-07-29 17:54           ` Help Needed! AJ
2000-07-29 19:58             ` Alexandre Oliva
2005-05-02 11:22 Bencio Aristo
2005-05-02 15:57 ` Jeffrey Holle
2005-05-07 15:18 Help Needed!! Dwayne I
2005-05-07 16:17 ` Jeffrey Holle
2005-05-07 19:12 ` Arturas Moskvinas

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=or66pqq33r.fsf@guarana.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jadeja@cyberspace.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).