public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/17684] [3.4/4.0 Regression] /usr/ccs/bin/ld: Can't create libgcc_s.sl
Date: Mon, 27 Sep 2004 02:54:00 -0000 [thread overview]
Message-ID: <20040927025409.17278.qmail@sourceware.org> (raw)
In-Reply-To: <20040927000621.17684.danglin@gcc.gnu.org>
------- Additional Comments From dave at hiauly1 dot hia dot nrc dot ca 2004-09-27 02:54 -------
Subject: Re: [3.4/4.0 Regression] /usr/ccs/bin/ld: Can't
> This is also a 3.4 regression also because that patch was applied to the 3.4
> branch.
Confirmed as 3.4 regression as well.
Dave
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17684
next prev parent reply other threads:[~2004-09-27 2:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 0:06 [Bug bootstrap/17684] New: [4.0.0 " danglin at gcc dot gnu dot org
2004-09-27 0:13 ` [Bug bootstrap/17684] [3.4/4.0 " pinskia at gcc dot gnu dot org
2004-09-27 2:54 ` dave at hiauly1 dot hia dot nrc dot ca [this message]
2004-09-27 11:42 ` pinskia at gcc dot gnu dot org
2004-09-27 17:08 ` hjl at lucon dot org
2004-09-27 20:54 ` danglin at gcc dot gnu dot org
2004-09-27 21:23 ` hjl at lucon dot org
2004-09-27 21:43 ` dave at hiauly1 dot hia dot nrc dot ca
2004-09-27 23:07 ` hjl at lucon dot org
2004-09-28 0:33 ` hjl at lucon dot org
2004-09-28 1:44 ` dave at hiauly1 dot hia dot nrc dot ca
2004-09-28 13:15 ` dave at hiauly1 dot hia dot nrc dot ca
2004-09-28 18:39 ` hjl at lucon dot org
2004-09-30 20:39 ` dave at hiauly1 dot hia dot nrc dot ca
2004-10-01 2:38 ` hjl at lucon dot org
2004-10-02 18:43 ` dave at hiauly1 dot hia dot nrc dot ca
2004-10-18 15:53 ` cvs-commit at gcc dot gnu dot org
2004-10-18 16:01 ` cvs-commit at gcc dot gnu dot org
2004-10-18 17:00 ` pinskia at gcc dot gnu dot org
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=20040927025409.17278.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).