Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!zaphod.mps.ohio-state.edu!rpi!sci.ccny.cuny.edu!phri!cmcl2!adm!news
From: dichter@soleil.sps.mot.com (Carl Dichter)
Newsgroups: comp.unix.internals
Subject: re: Debugging library incompatibilty
Message-ID: <25461@adm.brl.mil>
Date: 10 Jan 91 16:22:27 GMT
Sender: news@adm.brl.mil
Lines: 25

Are there only a few library functions you wish to "fix"?

If so, consider making a separate library to replace those functions.

By have the cc command search your replacement library 
you can pick up your version of the functions instead. You shouldn't
need a new header file because you are writing drop-in replacements.

To use your own libraries: 
	Use the "-L(directory)" of "cc" to tell it the directory your 
	library is in

	Use the "-l(suffix)" to tell it the suffix of your library name.

	For example, if you build a library "libc_new.a" in "/usr/local/lib",
	your "cc" might look like this:

		cc myprog.c -o myprog -L/usr/local/lib -lc_new

Have fun.


Carl R. Dichter 
Staff Software Engineer/Scientist
Email: dichter@soleil.sps.mot.com