From: Teemu Torma <tot@trema.com>
To: Neal Becker <neal@ctd.comsat.com>
Cc: egcs@cygnus.com
Subject: A patch for hppa1.1-hp-hpux10.20 w/ --enable-shared
Date: Wed, 03 Dec 1997 10:32:00 -0000 [thread overview]
Message-ID: <199712031633.RAA04897@baht.labs.trema.com> (raw)
In-Reply-To: <u967p6o0ot.fsf@neal.ctd.comsat.com>
From: Neal Becker <neal@ctd.comsat.com>
Date: 03 Dec 1997 11:23:30 -0500
Actually, gcc-2.7.2.2 has this in the specs:
*libgcc:
%{!shared:-lgcc}
which I guess is the same thing change you're recommending to egcs.
Well it's been working fine for gcc-2.7.2.2, so I guess this is the
Right Thing To Do.
Yes, that was the default in 2.7.2, and seems to have been changed
at Dec 4 1995 according to ChangeLog.10.
Teemu
next prev parent reply other threads:[~1997-12-03 10:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-03 4:08 Teemu Torma
1997-12-03 6:21 ` Neal Becker
1997-12-03 8:23 ` Neal Becker
1997-12-03 10:32 ` Teemu Torma [this message]
1997-12-03 15:32 ` Jeffrey A Law
1997-12-03 12:54 ` Neal Becker
1997-12-03 12:54 ` Jeffrey A Law
1997-12-04 1:30 ` Teemu Torma
[not found] ` <u967p6o0ot.fsf.cygnus.egcs@neal.ctd.comsat.com>
1997-12-03 12:54 ` Jason Merrill
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=199712031633.RAA04897@baht.labs.trema.com \
--to=tot@trema.com \
--cc=egcs@cygnus.com \
--cc=neal@ctd.comsat.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).