I have been using "pcloverlay" for some time now, under SCO. Now, I
need to "move" this over to linux. Where do I find it for linux or
how do I compile it for linux?

On Dec 14 2007, 10:56*am, smlunatick <yves...@gmail.com> wrote:
> I have been using "pcloverlay" for some time now, under SCO. *Now, I
> need to "move" this over to linux. *Where do I find it for linux or
> how do I compile it for linux?

Anyone????

----- Original Message -----
From: "smlunatick" <yveslec@gmail.com>
Newsgroups: comp.unix.sco.misc
To: <distro@jpr.com>
Sent: Friday, January 11, 2008 2:31 PM
Subject: Re: pcloverlay (going to Linux)


On Dec 14 2007, 10:56 am, smlunatick <yves...@gmail.com> wrote:
> I have been using "pcloverlay" for some time now, under SCO. Now, I
> need to "move" this over to linux. Where do I find it for linux or
> how do I compile it for linux?

Anyone????

-------------------

Anyone what?
You want a Linux binary you just compile it.

On SCO it was practical to build and distribute binaries because there was
only one platform,
All osr5 boxes hav the same cpu type, the same kernel, the same set of
libraries, the same set of userspace utils, the same directory structure,
the same everything, with only few, small, and generally backwards
compatible changes between versions, and an easy ability to patch any old
version up to be like the latest version with one or two big patches. Only
one "distribution".
If it works on mine, I know it works on yours and everyone elses with very
few possible variations and those easy to test for.

On Linux any binary might not work on any other linux box. So your options
are this:
a) learn to compile stuff
or
b) only use programs that are so popular that someone makes a binary package
just for your exact distribution, version, & platform. (which implies
yourself only using one distribution & platform, choose carefully)

I happen to be using the very latest SUSE 10.3 x86_64 on one box.
Any binary I build there will not work on many other linux boxes, and may or
may not work on your unknown distribution, version of that distribution, and
platform (cpu type basically).
Actually I also have a PPC box running the latest suse and the latest
ubuntu, but why be gratuitously difficult?
It's true that this particular app has very few and basic library
dependancies, and I could build a static version, and I could build a i386
version, and most boxes would be able to run that. Only _most_ even then.
There are movements, which you may join and contribute to, which try to get
all linux distribution makers and all gnu application authors to agree on
more standards to help reduce this kind of problem, but, this is so perfect,
there are at least a few different such movements each with their own idea
of how best to alleviate the problem.

Basically, welcome to Linux.
One of the required skillsets for administering Linux is basic ability to
compile apps.

slosh:~ # mkdir -p /usr/local/src/pcloverlay
slosh:/usr/local/src # cd /usr/local/src/pcloverlay
slosh:/usr/local/src/pcloverlay # wget
http://aplawrence.com/KevinSmith/pcoverlays/README
slosh:/usr/local/src/pcloverlay # wget
http://aplawrence.com/KevinSmith/pcoverlays/Makefile
slosh:/usr/local/src/pcloverlay # wget
http://aplawrence.com/KevinSmith/pco...s/pcloverlay.c
slosh:/usr/local/src/pcloverlay # wget
http://aplawrence.com/KevinSmith/pcoverlays/test.pcl
slosh:/usr/local/src/pcloverlay # vi Makefile
(change CFLAGS from "-belf -g" to "-O2")
slosh:/usr/local/src/pcloverlay # make
cc -O2 pcloverlay.c -o pcloverlay
pcloverlay.c: In function 'ProcessEscapes':
pcloverlay.c:373: warning: incompatible implicit declaration of built-in
function 'strncpy'
pcloverlay.c:394: warning: incompatible implicit declaration of built-in
function 'strncpy'
pcloverlay.c: In function 'PclWrite':
pcloverlay.c:532: warning: incompatible implicit declaration of built-in
function 'memcpy'
(hmm, warnings but it didn't error and did produce a binary, lets
test...)
slosh:/usr/local/src/pcloverlay # make test
[lots of stuff...]
26971 bytes in, 26962 bytes out
slosh:/usr/local/src/pcloverlay #

And indeed the test.ovl looks good.

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

On Jan 11, 9:09*pm, "Brian K. White" <br...@aljex.com> wrote:
> ----- Original Message -----
> From: "smlunatick" <yves...@gmail.com>
>
> Newsgroups: comp.unix.sco.misc
> To: <dis...@jpr.com>
> Sent: Friday, January 11, 2008 2:31 PM
> Subject: Re: pcloverlay (going to Linux)
>
> On Dec 14 2007, 10:56 am, smlunatick <yves...@gmail.com> wrote:
> > I have been using "pcloverlay" for some time now, under SCO. Now, I
> > need to "move" this over to linux. Where do I find it for linux or
> > how do I compile it for linux?
>
> Anyone????
>
> -------------------
>
> Anyone what?
> You want a Linux binary you just compile it.
>
> On SCO it was practical to build and distribute binaries because there was
> only one platform,
> All osr5 boxes hav the same cpu type, the same kernel, the same set of
> libraries, the same set of userspace utils, the same directory structure,
> the same everything, with only few, small, and generally backwards
> compatible changes between versions, and an easy ability to patch any old
> version up to be like the latest version with one or two big patches. Only
> one "distribution".
> If it works on mine, I know it works on yours and everyone elses with very
> few possible variations and those easy to test for.
>
> On Linux any binary might not work on any other linux box. So your options
> are this:
> a) learn to compile stuff
> or
> b) only use programs that are so popular that someone makes a binary package
> just for your exact distribution, version, & platform. (which implies
> yourself only using one distribution & platform, choose carefully)
>
> I happen to be using the very latest SUSE 10.3 x86_64 on one box.
> Any binary I build there will not work on many other linux boxes, and may or
> may not work on your unknown distribution, version of that distribution, and
> platform (cpu type basically).
> Actually I also have a PPC box running the latest suse and the latest
> ubuntu, but why be gratuitously difficult?
> It's true that this particular app has very few and basic library
> dependancies, and I could build a static version, and I could build a i386
> version, and most boxes would be able to run that. Only _most_ even then.
> There are movements, which you may join and contribute to, which try to get
> all linux distribution makers and all gnu application authors to agree on
> more standards to help reduce this kind of problem, but, this is so perfect,
> there are at least a few different such movements each with their own idea
> of how best to alleviate the problem.
>
> Basically, welcome to Linux.
> One of the required skillsets for administering Linux is basic ability to
> compile apps.
>
> slosh:~ # mkdir -p /usr/local/src/pcloverlay
> slosh:/usr/local/src # cd /usr/local/src/pcloverlay
> slosh:/usr/local/src/pcloverlay # wgethttp://aplawrence.com/KevinSmith/pcoverlays/README
> slosh:/usr/local/src/pcloverlay # wgethttp://aplawrence.com/KevinSmith/pcoverlays/Makefile
> slosh:/usr/local/src/pcloverlay # wgethttp://aplawrence.com/KevinSmith/pcoverlays/pcloverlay.c
> slosh:/usr/local/src/pcloverlay # wgethttp://aplawrence.com/KevinSmith/pcoverlays/test.pcl
> slosh:/usr/local/src/pcloverlay # vi Makefile
> * * (change CFLAGS from "-belf -g" to "-O2")
> slosh:/usr/local/src/pcloverlay # make
> cc -O2 * *pcloverlay.c * -o pcloverlay
> pcloverlay.c: In function 'ProcessEscapes':
> pcloverlay.c:373: warning: incompatible implicit declaration of built-in
> function 'strncpy'
> pcloverlay.c:394: warning: incompatible implicit declaration of built-in
> function 'strncpy'
> pcloverlay.c: In function 'PclWrite':
> pcloverlay.c:532: warning: incompatible implicit declaration of built-in
> function 'memcpy'
> * * (hmm, warnings but it didn't error and did produce a binary, lets
> test...)
> slosh:/usr/local/src/pcloverlay # make test
> [lots of stuff...]
> 26971 bytes in, 26962 bytes out
> slosh:/usr/local/src/pcloverlay #
>
> And indeed the test.ovl looks good.
>
> Brian K. White * *br...@aljex.com * *http://www.myspace.com/KEYofR
> +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
> filePro *BBx * *Linux *SCO *FreeBSD * *#callahans *Satriani *Filk!- Hide quoted text -
>
> - Show quoted text -

That's just it, it does not compile. The Makefile seems to be a dud.