Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!howland.reston.ans.net!noc.near.net!das-news.harvard.edu!ogicse!netnews.nwnet.net!serval!hlu From: hlu@eecs.wsu.edu (HJ Lu) Newsgroups: comp.os.386bsd.development Subject: Re: Shared libraries Message-ID: <1993May19.194601.25557@serval.net.wsu.edu> Date: 19 May 93 19:46:01 GMT Article-I.D.: serval.1993May19.194601.25557 References: <PC123.93May14232156@bootes.cus.cam.ac.uk> <1tau5kINNq52@scarecrow.mke.ab.com> <PC123.93May19192011@apus.cus.cam.ac.uk> Sender: news@serval.net.wsu.edu (USENET News System) Organization: School of EECS, Washington State University Lines: 37 In article <PC123.93May19192011@apus.cus.cam.ac.uk>, pc123@cus.cam.ac.uk (Pete Chown) writes: |> Huh? What do you mean "move the data symbols to other files"? |> I had int foo; in foo.c. Later, I have it to foo1.c which may be an existing file or a new file. |> If you add a new function to the library which has only static scope, |> you don't have to. I don't know if this is what you meant. |> I meant I filled a missing function foo () to the shared library. It is not static. |> Indeed so. I see no reason why shared libraries compiled with gcc 2.4 |> should be incompatible with those produced with gcc 1.39. The code |> will be different, but the jump table will take care of that. |> Similarly with fixing a bug in the library - most likely the only |> thing you'll change is the code. |> What if the new gcc rearranges the order of data symbols in one file? |> Oh, and welcome to BSD, by the way. I do remember you from Linux, I am open to all possibilties. |> don't I? I think you flamed me back then as well... :-) |> -- H.J.