Bug 11003 - libgcc.map: file format not recognized
Summary: libgcc.map: file format not recognized
Status: RESOLVED INVALID
Alias: None
Product: gcc
Classification: Unclassified
Component: bootstrap (show other bugs)
Version: 3.4.0
: P2 normal
Target Milestone: 3.4.0
Assignee: Not yet assigned to anyone
URL:
Keywords:
: 19136 25641 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-05-27 22:07 UTC by James McKelvey
Modified: 2006-01-02 17:17 UTC (History)
3 users (show)

See Also:
Host: sparc-sun-solaris2.7
Target: sparc-sun-solaris2.7
Build: sparc-sun-solaris2.7
Known to work:
Known to fail:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James McKelvey 2003-05-27 22:07:13 UTC
Failure to bootstrap on Solaris 2.7.1 with error, stage 1:

/mnt/home3/utilities/sparc-sun-solaris2.7/bin/ld:libgcc/./libgcc.map: file
format not recognized; treating as linker script
/mnt/home3/utilities/sparc-sun-solaris2.7/bin/ld:libgcc/./libgcc.map:1: parse error
collect2: ld returned 1 exit status
gmake[3]: *** [libgcc_s.so] Error 1

Configured by:

setenv CC gcc ; /mnt/home3/utilities/gcc/configure --prefix=/mnt/home3/utilities
--verbose --with-gnu-as=/mnt/home3/utilities/bin/as
--with-gnu-ld=/mnt/home3/utilities/bin/ld --enable-languages=c++

Built by:

gmake CFLAGS='-O' LIBCFLAGS='-g -O' CXXFLAGS='-g -O -fno-implicit-templates'
bootstrap

This bug seems to be similar to 4390, which is closed.

I'm using the latest binutils.
Comment 1 Eric Botcazou 2003-05-28 07:34:47 UTC
Not a bug. Please read more carefully http://gcc.gnu.org/install/configure.html.

The correct syntax is:

/mnt/home3/utilities/gcc/configure --prefix=/mnt/home3/utilities
--verbose --with-as=/mnt/home3/utilities/bin/as --with-gnu-as
--with-ld=/mnt/home3/utilities/bin/ld --with-gnu-ld --enable-languages=c++
Comment 2 Eric Botcazou 2004-12-24 06:14:59 UTC
*** Bug 19136 has been marked as a duplicate of this bug. ***
Comment 3 Andrew Pinski 2006-01-02 17:17:10 UTC
*** Bug 25641 has been marked as a duplicate of this bug. ***