public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: boyland@cs.uwm.edu
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/7589: libgcc.map file is empty; ld dies
Date: Fri, 10 Jan 2003 05:06:00 -0000 [thread overview]
Message-ID: <20030110050601.26440.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/7589; it has been noted by GNATS.
>From boyland@cs.uwm.edu Mon Jan 13 00:47:37 2003
From: boyland@cs.uwm.edu
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gaedba@attbi.com,
gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:
Subject: Re: bootstrap/7589: libgcc.map file is empty; ld dies
Date: Thu, 09 Jan 2003 23:01:38 -0600
On Solaris 2.8 while trying to build gcc-3.2.1,
I tried using --with-gnu-as with-as=<binutils> version and the same
for ld but invarianbly got the
...ld:libgcc/./libgcc.map:1: parse error in VERSION script
(I was using binutils 2.13.2).
I was only able to get gcc to build with the Sun /usr/ccs/bin/{as,ld}
binaries. To my untrained eye, the .map file lookd exactly the same
when building with Sun's as,ld. perhaps the code that's creating it uses
Sun's syntax even when --with-gnu-as/ld. In any case, the SFW people
use /usr/ccs/bin/{as,ld} to build gcc.
BTW: I also have other problems trying to build gcc-3.2.1 on Solaris
2.8:
mostly with libstdc++-v3 and libgcc_eh.
Regards,
John Boyland
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7589
next reply other threads:[~2003-01-10 5:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 5:06 boyland [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-15 4:43 bangerth
2003-05-15 0:16 gaedba
2003-05-14 9:26 Dara Hazeghi
2003-01-10 14:46 Jeff Sturm
2002-08-13 14:06 Phil Edwards
2002-08-13 12:06 gaedba
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=20030110050601.26440.qmail@sources.redhat.com \
--to=boyland@cs.uwm.edu \
--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: 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).