I've installed the Application Development Libraries and Linker from
the distribution media, and installed the Development tools on the
Skunkworks CD.
That version 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.
I found in the binutils/README a 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".
Does anyone have a suggestion as to how I can get around this
roadblock?
Alternatively, would anyone be able to e-mail me a working "ar"?
Thanks.
Steve Manning
Milwaukee, WI
mann...@tds.net (Steve Manning) wrote in message news:<f4d5ed5.03051...@posting.google.com>...
> I'm trying to bootstrap a GCC development environment on a bare SCO
> OpenServer 5.0.6 system.
...
> 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.
...
Have you loaded the "Linker and Application Development Libraries"
from your 5.0.6 CD-ROM?
--
JP
Hello, JP - thanks for responding.
As I mentioned in my original post, I have loaded those items off the
CD.
I'm able to use the Skunkworks GCC but there doesn't seem to be a
version of "ar" included along with it in the Development Tools
section.
Steve
Well, then I don't recall what's wrong. A few years ago, /bin/as wasn't
included in that suite. I always though /bin/ar was, though. Anyone else
(i.e., Robert Lipe) remember?
--
JP
The only I remember being missing was the simple debugger, adb, which is
there, but hidden as /etc/_fst.
I'm pretty sure everthing else necessary to run gcc is included in the
header and library package on the installation CDrom. Given that
/etc/conf/cf.d/link_unix needs to be able to do rudimentary compiles and
linking to build new kernels.
Bill
--
INTERNET: bi...@Celestial.COM Bill Campbell; Celestial Software LLC
UUCP: camco!bill PO Box 820; 6641 E. Mercer Way
FAX: (206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676
URL: http://www.celestial.com/
When I hear a man applauded by the mob I always feel a pang of pity
for him. All he has to do to be hissed is to live long enough.
-- H.L. Mencken, ``Minority Report''
Yeah, but rudimentary compiles needn't create libraries, and so don't
need /bin/ar.
--
JP
> | I'm able to use the Skunkworks GCC but there doesn't seem to be a
> | version of "ar" included along with it in the Development Tools
> | section.
>
> Well, then I don't recall what's wrong. A few years ago, /bin/as wasn't
> included in that suite. I always though /bin/ar was, though. Anyone else
> (i.e., Robert Lipe) remember?
I seem to have found a way around this now.
I basically installed the DevKit from the media supplied without
licensing it, built BINUTILS (including "ar" -- w00t!) and then used
pkgrm to remove those DevKit packages.
The licensing screen for the DevKit indicated that use of the DevKit
for a significant amount of time required licensing. Since I
basically just used it to compile this one program and then removed
it, I believe that I stayed within the terms of the license.
Now if you run that by SCO's current crop of lawyers... well, who
knows? :-)
Thanks all.
Steve