public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Arvind Sankar <arvind@cse.iitb.ernet.in>
To: egcs@cygnus.com
Subject: always use collect2
Date: Fri, 20 Feb 1998 21:22:00 -0000	[thread overview]
Message-ID: <19980221105411.A26167@kailash.cse.iitb.ernet.in> (raw)

I have a SPARC machine running UNIX SVR4.

Why is USE_COLLECT2 always defined? Doesnt egcs work with the binutils
2.8.1 linker?
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? The binutils ld is earlier in my PATH when collect2 was
built. collect2 calling /usr/ccs/bin/ld causes problems because I want
to pass certain options to binutils-ld which /usr/ccs/bin/ld does not
support.

Mon Aug 11 14:15:02 1997  Jeffrey A Law  (law@cygnus.com)

        * Makefile.in (USE_COLLECT2): Always use collect2.
        (collect2): Depend on and link in hash.o and tlink.o.
        (tlink.o, hash.o): Add dependencies.

-- arvind


             reply	other threads:[~1998-02-20 21:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-20 21:22 Arvind Sankar [this message]
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 ` always use collect2 Alexandre Oliva
1998-02-22  3:16   ` 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=19980221105411.A26167@kailash.cse.iitb.ernet.in \
    --to=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).