Re: Squid on SCO - how to install?

SCO and GNU use identical linker formats, at least they did last time I
looked. You can substitute SCO ld for GNU ld even, if you have to.
Hence, they are also happy with each-other's library and object files.

D

Mike wrote:
>
> When I said I compiled it I meant it used gcc to compile and obviously
> all the files required (headers etc) were found because I installed them
> (or maybe the path was set correctly) when I installed the SCO
> development software.
>
> Obviously, this isn't particularly good. I would've thought that the
> libraries for SCO compiler would've been somewhat different to those
> required by gcc.
>
> Nevertheless it seemed to compile.
>
> Now I don't have any "make" to use. DOH!
>
> Mike
>
> > ----------
> > From: Mike
> > Sent: Friday, March 20, 1998 1:40 PM
> > To: 'Daniel Kiracofe'
> > Cc: 'squid-users@nlanr.net'
> > Subject: RE: Squid on SCO - how to install?
> >
> > OK, this is what I've done.
> >
> > I thought I'd install the SCO development kit which includes the SCO
> > compiler and make, etc etc.
> >
> > I installed it although it's not licenced so I can't actually run a
> > SCO
> > compile or make. In other words I copied all the files but when I try
> > to
> > run cc it fails with a Warning: unlicenced message.
> >
> > I then ran ./configure and the compile took place. From the list of
> > messages I would say it looks OK. If anyone doubts this I will do it
> > again and provide the log to you.
> >
> > Now I need to run make. Unfortunately, the SCO make is unlicenced so
> > it
> > doesn't run either. I can't find make in the gcc files. Does this mean
> > I'm totally stuck now or is there a make somewhere I can use?
> >
> > Thanks
> >
> > Mike
> >
> >
> > > ----------
> > > From: Daniel Kiracofe[SMTP:drk@gurulink.com]
> > > Sent: Friday, March 20, 1998 5:33 AM
> > > To: Mike
> > > Subject: RE: Squid on SCO - how to install?
> > >
> > > > The problem now is, why is gcc not finding the header files like
> > > > stdio.h.
> > > >
> > > > Well, I did a search for stdio.h and found it in, wait for it...
> > > >
> > > > /usr/local/lib/gcc-lib/486-sco3.2v5.0/include/oldstyle/
> > > >
> > > > Why? What do I do now?
> > >
> > > Well, by default, the c compiler will only look for includes in
> > > certain
> > > well know locations, like /usr/include, /usr/local/include, etc.
> > You
> > > have
> > > two options:
> > > 1. Move all the .h files from the above directory to /usr/include
> > > 2. Tell gcc to look in the above directory. I'd recommend this
> > > method.
> > > In the file src/Makefile.in you should see a line reading:
> > >
> > > INCLUDE = -I. -I../include -I$(srcdir)/../include
> > >
> > > add to it:
> > >
> > > -I/usr/local/lib/gcc-lib/486-sco3.2v5.0/include/oldstyle/
> > >
> > > Then run configure again. That should remake the Makefiles to
> > > include
> > > this change...
> > >
> > > /* Daniel */
> > > WWW: http://users.gurulink.com/drk
> > > Linux Consultation Specializing in TCP/IP Networking and Web Caching
> > >
> > > "Fear is only afraid of the absence of itself" - Mediocrates
> > >
> > >
> >

-- 
Did you read the documentation AND the FAQ?
If not, I'll probably still answer your question, but my patience will
be limited, and you take the risk of sarcasm and ridicule.