public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andy Gabor <ajgabor@ucdavis.edu>
To: gcc-help@gcc.gnu.org
Subject: RE: make bootstrap failure -> libgcc.map: file format...
Date: Mon, 09 Sep 2002 15:19:00 -0000	[thread overview]
Message-ID: <15741.7763.433276.174171@nova.ucdavis.edu> (raw)


Turns out the answer for me was *not* to use GNU ld (binutils-2.13).

Configuring with:

setenv CC /opt/SUNWspro/bin/cc
../configure --enable-languages=c,c++ --with-ld=/usr/ccs/bin/ld

Solved this problem.

Andy



On 9/9/2002 Andy Gabor wrote:
>
>Hi,
>
>Installed current binutils.
>
>Tried to build gcc-3.2 of ss u10 running solaris 9.
>
>Configured with:
>
>setenv CC /opt/SUNWspro/bin/cc
>./configure --enable-languages=c,c++
>
>
>Build error:
>gcc/./_udivdi3.o libgcc/./_umoddi3.o libgcc/./_udiv_w_sdiv.o libgcc/./_udivmoddi4.o  libgcc/./unwind-dw2.o libgcc/./unwind-dw2-fde.o libgcc/./unwind-sjlj.o -lc && rm -f libgcc_s.so && ln -s libgcc_s.so.1 libgcc_s.so
>/usr/local/sparc-sun-solaris2.9/bin/ld:libgcc/./libgcc.map: file format not recognized; treating as linker script
>/usr/local/sparc-sun-solaris2.9/bin/ld:libgcc/./libgcc.map:1: parse error
>collect2: ld returned 1 exit status
>
>There have been reports of other problems with libgcc.map but slightly
>different error reports.
>
>Any insights appreciated
>
>Andy
>=====================================================================
>Andy Gabor - Department of Neurology, University of California, Davis
>ajgabor@ucdavis.edu (530)754-5036 (FAX)

             reply	other threads:[~2002-09-09 22:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-09 15:19 Andy Gabor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-09 14:19 Andy Gabor
2002-09-10  2:16 ` Hugh Sasse Staff Elec Eng

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=15741.7763.433276.174171@nova.ucdavis.edu \
    --to=ajgabor@ucdavis.edu \
    --cc=gcc-help@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).