public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Kaoru Fukui <k_fukui@highway.ne.jp> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/7045: /usr/bin/ld:libgcc/./libgcc.map:4: parse error in VERSION script Date: Mon, 17 Jun 2002 00:36:00 -0000 [thread overview] Message-ID: <20020617065603.26637.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/7045; it has been noted by GNATS. From: Kaoru Fukui <k_fukui@highway.ne.jp> To: rth@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, k_fukui@highway.ne.jp, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: bootstrap/7045: /usr/bin/ld:libgcc/./libgcc.map:4: parse error in VERSION script Date: Mon, 17 Jun 2002 15:48:25 +0900 (JST) On 16 Jun, rth@gcc.gnu.org wrote: > Synopsis: /usr/bin/ld:libgcc/./libgcc.map:4: parse error in VERSION script > > State-Changed-From-To: open->feedback > State-Changed-By: rth > State-Changed-When: Sun Jun 16 12:59:51 2002 > State-Changed-Why: > CVS binutils broke nm. Revert to, say, 2.12.1 > and everything should work again. thanks Kaoru
next reply other threads:[~2002-06-17 6:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-17 0:36 Kaoru Fukui [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-06-17 1:46 rth 2002-06-16 13:01 rth 2002-06-16 7:16 Andrew Pinski 2002-06-16 2:56 k_fukui
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=20020617065603.26637.qmail@sources.redhat.com \ --to=k_fukui@highway.ne.jp \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).