public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: Arvind Sankar <arvind@cse.iitb.ernet.in>
Cc: egcs@cygnus.com
Subject: Re: always use collect2
Date: Sat, 21 Feb 1998 12:35:00 -0000	[thread overview]
Message-ID: <ord8ggj1sy.fsf@iguacu.dcc.unicamp.br> (raw)
In-Reply-To: <19980221105411.A26167@kailash.cse.iitb.ernet.in>

Arvind Sankar writes:

> Why is USE_COLLECT2 always defined?

Because it is needed in order to implement the C++ template repository
mechanism (-frepo)

> Doesnt egcs work with the binutils 2.8.1 linker?

It does, but it's not enough.

> If I have to use collect2, how do I tell it to call the binutils linker
> rather than the default one on my system, which it seems to find in
> /usr/ccs/bin?

Create a link named `real-ld' to the ld program you wish to use in the
same directory where `cc1' lives.

-- 
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil

  parent reply	other threads:[~1998-02-21 12:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-20 21:22 Arvind Sankar
1998-02-20 22:58 ` Jeffrey A Law
1998-02-21  7:58   ` gcc m68k: pc-relative addressing for code? Michael Schwingen
1998-02-21 21:04     ` Jeffrey A Law
1998-02-21 22:52       ` Philippe De Muyter
1998-02-22 13:03         ` Jeffrey A Law
1998-02-21 12:35 ` Alexandre Oliva [this message]
1998-02-22  3:16   ` always use collect2 Andi Kleen
1998-02-22 11:16     ` Jeffrey A Law
1998-02-22 12:45       ` Richard Henderson
1998-02-22 12:55         ` Jeffrey A Law
1998-02-22 16:39         ` ak
     [not found]         ` <9692.888181043.cygnus.egcs@hurl.cygnus.com>
1998-02-22 20:04           ` Jason Merrill
1998-02-22 20:06             ` Jeffrey A Law

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=ord8ggj1sy.fsf@iguacu.dcc.unicamp.br \
    --to=oliva@dcc.unicamp.br \
    --cc=arvind@cse.iitb.ernet.in \
    --cc=egcs@cygnus.com \
    /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).