gcc compiling notes
Brian K. White
free apps on OS 5.0.5 using gcc?
I've compiled some things fine, and some things have me quite
frustrated. especially when I can look at the skunkware binary for some
item and see that clearly it can be compiled, and further, at least one
person has done so.
example. I got zlib and libpng to compile, and spit out .so libraries
however libjpeg is laughing at me. :)
I didn't include detailed make error messages because I'm not really
looking for help with libjpeg. I'm looking for help with 'stuff' the
general points to see to in any random makefile for super whiz-bang gnu
app XXXX
I don't imagine some definitive thorough recipe for libjpeg is
subsequently going to help me a lot with ghostscript, X, gtk, etc...and
I hate to be one of those guys that aks everything he doesn't know and
seems to want you to do the work of figuring out their life. I much
prefer receiving finger pointing which of the 360 directions to look,
and I can most take it from there just fine, thus requesting a minimum
of effort from the pointer, and yet saving me from truckloads of effort
going in circles and never getting anything done.
--
Brian~
Jean-Pierre Radley
| Is there a repository of porting/compiling notes for compiling various
| free apps on OS 5.0.5 using gcc?
Try posting in the comp.unix.sco.programmer newsgroup.
And also join the polecats mailing list, where the contrinutors to
skunkware discuss just this sort of thing. Just this morning, that list
had a discussion of compiling the latest perl on UW7.
You can get subscribed by dropping a note to Ron record <r...@sco.com>
--
Jean-Pierre Radley <j...@jpr.com> XC/XT Custodian Sysop, CompuServe SCOForum
Andrew Smallshaw
> Is there a repository of porting/compiling notes for compiling various
> free apps on OS 5.0.5 using gcc?
> I didn't include detailed make error messages because I'm not really
> looking for help with libjpeg. I'm looking for help with 'stuff' the
> general points to see to in any random makefile for super whiz-bang gnu
> app XXXX
When it comes to porting, it's helpful to know APIs of various Unix systems
inside out and back to front, but the best way of doing this is probably by
porting. It appears you want general pointers on porting so a few tips:
1) Link errors
If you successfully compile an application but get errors on linking,
do a 'man function-name' for the missing function. In the syntax section,
you'll see a line 'cc ... -l(library)'. You need to add the -l bit to
get the required library linked in.
2) Apparently missing functions
It's possible that what is needed is there, but defined in a place
other than where the program expects it. 'man function-name' will
tell you what headers you need to pick up the function declaration.
3) Apparently missing #defines and/or variables
Again, these may be present, but in a non-standard location. Try
searching scohelp for the term you're looking for, and include
the relevant headers. Alternatively you can find and grep on
/usr/include, /usr/local/include, etc.
4) Really missing functions, #defines, or variables
These fall into two categories: those that are included in other Unix
systems, and those that belong to third party libraries.
Third party libraries first: find out which library you need, get it
and port that. This can get a bit demoralising when you have to port
several libraries before you can get on with what you're trying to do.
Other systems: read up on what the function in question does (most
Unixes have on-line docs somewhere on the net), and assess how tricky
it will be to implement. Some times you can create a simple wrapper
around facilities you do have, or you may have to re-write the
problematic code to use your system's facilities.
5) #ifdefs
These are your friends. You may have done a './configure', but the
#defines still may not be quite right. Look around the problematic
code and see if there are any #ifdefs that look like they could solve
your problem. If so this is likely to prove the path of least
resistance.
This isn't exhaustive, of course. Feel free to add extra points here.
--
Andrew Smallshaw
smal...@cs.man.ac.uk
Brian K. White
>
> Brian K. White opined (on Fri, Sep 24, 1999 at 01:00:30AM -0400):
> | free apps on OS 5.0.5 using gcc?
>
>
> And also join the polecats mailing list, where the contrinutors to
> skunkware discuss just this sort of thing. Just this morning, that list
> had a discussion of compiling the latest perl on UW7.
>
> You can get subscribed by dropping a note to Ron record <r...@sco.com>
>
> --
> Jean-Pierre Radley <j...@jpr.com> XC/XT Custodian Sysop, CompuServe SCOForum
I'm on the list...of course I should have asked there. I have no clever
and focus diverting excuse as to why I didn't think to, other than that
from reading the other posts there, I've decided my level of questions
are not interesting to that community and plan to avoid babbling there.
though this question sounds reasonable enough.
--
Brian~