public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Jason Merrill <jason@cygnus.com>
Cc: egcs@cygnus.com
Subject: Re: always use collect2
Date: Sun, 22 Feb 1998 20:06:00 -0000	[thread overview]
Message-ID: <6727.888206858@hurl.cygnus.com> (raw)
In-Reply-To: <u9k9anhsq7.fsf@yorick.cygnus.com>

  In message < u9k9anhsq7.fsf@yorick.cygnus.com >you write:
  > >>>>> Jeffrey A Law <law@cygnus.com> writes:
  > 
  > >   In message < 19980222124721.49413@dot.cygnus.com >you write:
  > >> On Sun, Feb 22, 1998 at 12:07:21PM -0700, Jeffrey A Law wrote:
  > >> > It's necessary to deal with some shared library and EH issues.
  > >> 
  > >> No, I'm pretty sure it's just repo for gnu ld on elf.
  > >> But since it isn't doing anything it also shouldn't get
  > >> in the way, so it should be left in the loop.
  > 
  > > Talk to Jason -- he explained the shlib and EH dependencies
  > > to me a while ago (I've forgotten the details).
  > 
  > No, Richard is right.  On ELF targets, it's just for repo and demangling
  > the linker error messages.
I'm obviously confused then :-)  

Thanks for clearing things up.

jeff

      reply	other threads:[~1998-02-22 20:06 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 ` 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 [this message]

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=6727.888206858@hurl.cygnus.com \
    --to=law@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=jason@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).