Question Re: make bootstrap failure -> file format..

Andy Gabor
Thu Sep 12 20:53:00 GMT 2002

This this probably more than anyone wants to know but it seems...

1. binutil populates both /usr/local/bin and
/usr/local/sparc-sun-solaris2.9/bin with ld and such.  Files in both
directories are identical as are their creation date and time (hard link).

2. Sun ld is in /usr/ccs/bin.

3. Build works so long as configure is used with --with-ld=(any of the
above files).  If this option is *not* set, build dies although it seems
it is using the correct files based on the build output.

A bit mysterious - but I guess if the world made any sense men would
ride side-saddle.


*****Original message*****
Platform=UltraSparc 250
GCC ver. 3.1
binutils ver. 2.13 (by the way, according to the output from ls -i the
                     /usr/local/bin utilities are hard links to
                     the utilities in /usr/local/sparc-sun-solaris2.7/bin
                     because inode numbers are identical)
Gnu make ver. 3.79.1

Using configure with no options and then make bootstrap would fail with
the following messages:

/usr/local/sparc-sun-solaris2.7/bin/ld:libgcc/./ file format
not recognized; treating as linker script
/usr/local/sparc-sun-solaris2.7/bin/ld:libgcc/./ parse error
collect2: ld returned 1 exit status

Did a "make distclean" then a "../configure --with-ld=/usr/local/bin/ld
--with-as=/usr/local/bin/as" in my objdir. When I did a "make bootstrap"
the build process made it through the libgcc build with no problem.

Now my question is:
If the utilities in /usr/local/bin are hard links to the binutils in
/usr/local/sparc-sun-solaris2.7/bin, why did the first compile fail while
the second did it's thing with no problem?

Clif Redding

More information about the Gcc-help mailing list