SEO

<UGH!>

Looks like my whole OS is a mess, I have no idea how it got this way, I
inherited it. I can't compile anything in C, for example, I'm trying to
install Date::Calc and DateTime for Perl, but I get so many missing
header files and compiler errors it's totally crazy. Perl used to be so
simple, at least on other Operating Systems.

Is there a path I can take to fix the compiler on this thing? It's a
total mess!

Everything in /usr/include soft links to
/opt/K/SCO/Unix/5.0.7Hw/usr/include/(something) or
/opt/K/SCO/unixds/5.2.0A/usr/include/(something) or
/opt/K/SCO/xds/5.2.5j/usr/include/(something) or
/opt/K/SCO/gwxlibs/2.1.0Ba/usr/include/(something)

That doesn't sound good; why aren't they all in one directory (or sub
directorys of one)? Also, there are a lot of files missing like
stdio.h, string.h and a many more which I find at /udk/usr/include
(whatever that is) and broken links like crazy!

Can I remove them all and start fresh with something that works right?

</UGH!>

What a nightmare!

Thanks.

Skot.

Skot typed (on Tue, Jan 10, 2006 at 07:50:18PM +0000):
| Looks like my whole OS is a mess, I have no idea how it got this way, I
| inherited it. I can't compile anything in C, for example, I'm trying to
| install Date::Calc and DateTime for Perl, but I get so many missing
| header files and compiler errors it's totally crazy. Perl used to be so
| simple, at least on other Operating Systems.
|
| Is there a path I can take to fix the compiler on this thing? It's a
| total mess!
|
| Everything in /usr/include soft links to
| /opt/K/SCO/Unix/5.0.7Hw/usr/include/(something) or
| /opt/K/SCO/unixds/5.2.0A/usr/include/(something) or
| /opt/K/SCO/xds/5.2.5j/usr/include/(something) or
| /opt/K/SCO/gwxlibs/2.1.0Ba/usr/include/(something)
|
| That doesn't sound good; why aren't they all in one directory (or sub
| directorys of one)? Also, there are a lot of files missing like
| stdio.h, string.h and a many more which I find at /udk/usr/include
| (whatever that is) and broken links like crazy!

All the /usr/include files are in fact installed as symlinks.

The UDK part of the DevKit is to compile files that can run on OpenServer
or UnixWare.

| Can I remove them all and start fresh with something that works right?

Up to you if you want to reinstall the DevSys, but why not first go into
custom and verify the DevSys?

--
JP
==> http://www.frappr.com/cusm <==

Jean-Pierre Radley wrote:

> Skot typed (on Tue, Jan 10, 2006 at 07:50:18PM +0000):
> | Looks like my whole OS is a mess, I have no idea how it got this way, I
> | inherited it. I can't compile anything in C, for example, I'm trying to
> | install Date::Calc and DateTime for Perl, but I get so many missing
> | header files and compiler errors it's totally crazy. Perl used to be so
> | simple, at least on other Operating Systems.
> |
> | Is there a path I can take to fix the compiler on this thing? It's a
> | total mess!
> |
> | Everything in /usr/include soft links to
> | /opt/K/SCO/Unix/5.0.7Hw/usr/include/(something) or
> | /opt/K/SCO/unixds/5.2.0A/usr/include/(something) or
> | /opt/K/SCO/xds/5.2.5j/usr/include/(something) or
> | /opt/K/SCO/gwxlibs/2.1.0Ba/usr/include/(something)
> |
> | That doesn't sound good; why aren't they all in one directory (or sub
> | directorys of one)? Also, there are a lot of files missing like
> | stdio.h, string.h and a many more which I find at /udk/usr/include
> | (whatever that is) and broken links like crazy!
>
> All the /usr/include files are in fact installed as symlinks.

Yes.

> The UDK part of the DevKit is to compile files that can run on OpenServer
> or UnixWare.

Well that is handy. So what about all the missing standard C headers
like stdio and string and there were a whole bunch.

> | Can I remove them all and start fresh with something that works right?
>
> Up to you if you want to reinstall the DevSys, but why not first go into
> custom and verify the DevSys?

That reports:
Files With Discrepancies : 0
Total Discrepancies : 0

Cheers

----- Original Message -----
From: "Skot" <skot@canada.com>
Newsgroups: comp.unix.sco.misc
To: <distro@jpr.com>
Sent: Tuesday, January 10, 2006 2:50 PM
Subject: Compiling C source on OSR5.07


> <UGH!>
>
> Looks like my whole OS is a mess, I have no idea how it got this way, I
> inherited it. I can't compile anything in C, for example, I'm trying to
> install Date::Calc and DateTime for Perl, but I get so many missing header
> files and compiler errors it's totally crazy. Perl used to be so simple,
> at least on other Operating Systems.
>
> Is there a path I can take to fix the compiler on this thing? It's a
> total mess!
>
> Everything in /usr/include soft links to
> /opt/K/SCO/Unix/5.0.7Hw/usr/include/(something) or
> /opt/K/SCO/unixds/5.2.0A/usr/include/(something) or
> /opt/K/SCO/xds/5.2.5j/usr/include/(something) or
> /opt/K/SCO/gwxlibs/2.1.0Ba/usr/include/(something)
>
> That doesn't sound good; why aren't they all in one directory (or sub
> directorys of one)? Also, there are a lot of files missing like stdio.h,
> string.h and a many more which I find at /udk/usr/include (whatever that
> is) and broken links like crazy!
>
> Can I remove them all and start fresh with something that works right?
>
> </UGH!>
>
> What a nightmare!

You've posted here before, Which leads on to assume you are familiar with
sco systems, and thus it should be no surprise that you need to install
either the development system or at least the linker & libraries package and
gnutools before you can compile anything.

Further details you might not be aware of:
if the development system or at least the linker & app development libraries
package wasn't installed from the beginning, then you need to roll back any
patches that have been installed that would have modified those packages had
they been installed when the patch was applied. This effectively means
rolling back all patches since the first patch you probably installed was
MP1 and that modifid the devsys and most other packages further modify MP1.

Today, on 507, you would do this in this order:
* roll back all patches
* install the linker & app devel package from the install CD
* touch /tmp/gnutools.nocheck & /tmp/nocheck.gnutools (it's only one of them
but I don't remember which)
* install gnutools-5.0.7Kj (ignore warnings)
* install MP4 (choose "leave components loaded" when it shows the packages
that will be replaced)
* add /usr/gnu/bin:/usr/gnu/sbin to PATH by whatever means you like. I
define a full path in /etc/profile that includes
/usr/local/bin:/usr/local/sbin:/usr/gnu/bin:/usr/gnu/sbin, and edit roots
profile to say PATH=${PATH}:/etc:/tcb/bin

After all that, you should be able to compile most things with only a small
amount of manual ./configure --options... or makefile editing, but you will
probaly still have a hard time with perl modules because perl is very picky
and the modules need to be built with the same environment that built perl
itself, and the above directions create a working, free gcc environment,
whereas perl was built with the native development system, which costs $$$

It's possible they switched to building perl with gcc since the time I
figured this out the hard way, it's also possible perl became less picky, so
go ahead any give it a try anyways.

There was also a glitch in MP3 where the MP3 patch didn't update the linker
(ld) in the linker & libraries package but it did update the same binary in
the full development system. I'm assuming this was fixed in mp4, but if you
can't build things after doing the above then there is a couple ways to get
the updated ld binary out of the devsys part of mp4 but I won't go into it
unless it turns out to be necessary.

Also, be on the lookout for problems after installing MP4, be ready to roll
it back and install MP3 instead.
MP4 breaks perfect compatibility with a few things and I don't think all the
breakages have been found yet since it's still very new and most sco
installations only receive updates under duress, not just because the update
bacame available. So most 507 boxes probably do not have mp4 yet. many
probably don't even have mp1 yet!.
Example 1: BackupEdge would break after installing MP4, but, Microlite has
updated BackupEdge and all you need to do is install the latest version and
it's fine.
Example 2: If you have even the latest version of Olympus TuneUp in your
kernel, then after applying MP4 you can't build kernels any more. There is
no update from Pacific Code Works that fixes this yet. It doesn't leave you
dangerously broken though, it's easy to uninstall tuneup from custom and
after that kernels build fine.

This is the first I've mentioned the tuneup problem to anyone so if anyone
else out there has both tuneup and mp4 and can still link new kernels
without error I would like to hear about it.

Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!

Skot typed (on Tue, Jan 10, 2006 at 08:43:05PM +0000):
| Jean-Pierre Radley wrote:
|
| >Skot typed (on Tue, Jan 10, 2006 at 07:50:18PM +0000):
| >| Looks like my whole OS is a mess, I have no idea how it got this way, I
| >| inherited it. I can't compile anything in C, for example, I'm trying to
| >| install Date::Calc and DateTime for Perl, but I get so many missing
| >| header files and compiler errors it's totally crazy. Perl used to be so
| >| simple, at least on other Operating Systems.
| >|
| >| Is there a path I can take to fix the compiler on this thing? It's a
| >| total mess!
| >|
| >| Everything in /usr/include soft links to
| >| /opt/K/SCO/Unix/5.0.7Hw/usr/include/(something) or
| >| /opt/K/SCO/unixds/5.2.0A/usr/include/(something) or
| >| /opt/K/SCO/xds/5.2.5j/usr/include/(something) or
| >| /opt/K/SCO/gwxlibs/2.1.0Ba/usr/include/(something)
| >|
| >| That doesn't sound good; why aren't they all in one directory (or sub
| >| directorys of one)? Also, there are a lot of files missing like
| >| stdio.h, string.h and a many more which I find at /udk/usr/include
| >| (whatever that is) and broken links like crazy!
| >
| >All the /usr/include files are in fact installed as symlinks.
|
| Yes.
|
| >The UDK part of the DevKit is to compile files that can run on OpenServer
| >or UnixWare.
|
| Well that is handy. So what about all the missing standard C headers
| like stdio and string and there were a whole bunch.
|
| >| Can I remove them all and start fresh with something that works right?
| >
| >Up to you if you want to reinstall the DevSys, but why not first go into
| >custom and verify the DevSys?
|
| That reports:
| Files With Discrepancies : 0
| Total Discrepancies : 0

Sorry, Skot. If the DevSys verification says everything is OK,
then usr/include/stdio.h exists. What, BTW, is the licensing status of
the DevKit?


--
JP
==> http://www.frappr.com/cusm <==