bug-gnu-utils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Can't bootstrap BINUTILS on SCO 5.0.6


From: Steve Manning
Subject: Can't bootstrap BINUTILS on SCO 5.0.6
Date: Fri, 30 May 2003 16:44:44 -0500

I'm trying to bootstrap a GCC development environment on a bare SCO
OpenServer 5.0.6 system.

I've installed the Application Development Libraries and Linker from
the distribution media, and installed the Development tools on the
Skunkworks CD.

That version (SCO's Skunkworks) of GCC appears to work fine, as I've
successfully compiled a few utilities.

I want to replace all of the Skunkworks stuff with the latest versions
of GCC and everything else.  I can't do a new GCC without BINUTILS since
apparently "ar" wasn't included in the Skunkworks dev tools.

So I snagged the latest BINUTILS release (2.13.2.1) and tried to build
it.  It blew up due to a missing "ar" as well.

In the binutils/README, I found the shell script to build just "ar" so
that the rest of BINUTILS can be built.  When I try to run it, it fails
with the following:
  make[2]: *** No rule to make target `../bfd/libbfd.la', needed by
`size'.  Stop.
  make[2]: Leaving directory
`/usr/local/source/binutils/binutils-2.13.2.1/binutils'

I tried going to the bfd directory and making libbfd.la, but that fails
due to the lack of an "ar".

Would anyone have a suggestion as to how I can get around this
roadblock?

Thanks!

Steve Manning
Roundy's Inc.
phone: (262) 953-6476
fax:   (262) 953-7800
 
 
-----------------------------------------------------
The information transmitted is intended only for the person or entity to which 
it is addressed and may contain confidential and/or privileged material.
 
Any review, retransmission, dissemination or other use of, or taking of any 
action in reliance upon this information by persons or entities other than the 
intended recipient is prohibited.
If you received this in error, please contact the sender and delete the 
material from any computer.
-----------------------------------------------------





reply via email to

[Prev in Thread] Current Thread [Next in Thread]