public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Florin Iucha <florin@iucha.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/10736: gcc-3.3 prelease 2 fails to bootstrap using native ld on Solaris 8 32 bit
Date: Sun, 11 May 2003 05:16:00 -0000	[thread overview]
Message-ID: <20030511051601.4378.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/10736; it has been noted by GNATS.

From: Florin Iucha <florin@iucha.net>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, florin@iucha.net,
	nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org
Cc:  
Subject: Re: bootstrap/10736: gcc-3.3 prelease 2 fails to bootstrap using
 native ld on Solaris 8 32 bit
Date: Sun, 11 May 2003 00:13:49 -0500

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10736
 
 I get a similar error using the GNU binutils:
 /usr/local/sparc-sun-solaris2.8/bin/ld:libgcc/./libgcc.map: file format 
 not recognized; treating as linker script
 /usr/local/sparc-sun-solaris2.8/bin/ld:libgcc/./libgcc.map:1: parse error
 collect2: ld returned 1 exit status
 make[3]: *** [libgcc_s.so] Error 1
 make[3]: Leaving directory `/opt/update/src/objdir/gcc'
 make[2]: *** [stmp-multilib] Error 2
 make[2]: Leaving directory `/opt/update/src/objdir/gcc'
 make[1]: *** [stage1_build] Error 2
 make[1]: Leaving directory `/opt/update/src/objdir/gcc'
 make: *** [bootstrap] Error 2
 
 florin
 


             reply	other threads:[~2003-05-11  5:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-11  5:16 Florin Iucha [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-11  8:36 Eric Botcazou
2003-05-11  8:34 ebotcazou
2003-05-11  2:26 florin

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=20030511051601.4378.qmail@sources.redhat.com \
    --to=florin@iucha.net \
    --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).