From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Fri, 27 Jun 2003 14:07:19 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 138 ************************************************** Thursday 26 June 2003 Number 138 ************************************************** Subjects for today 1 Re: [EMX] Re: libc : Andreas Buening **= Email 1 ==========================** Date: Fri, 27 Jun 2003 20:48:35 +0200 From: Andreas Buening Subject: Re: [EMX] Re: libc Ilya Zakharevich wrote: [snip] > I do not see any problem whatsoever. C_LIBRARY_PATH should be > different, that's all. It is easy to write a tiny script which will > sort existing libraries into 2 categories: > > a) compatible with old API only; > b) do not call the changed API; > > The newly compiled libraries may go into "b" or a third category > > c) compatible with the new API only. > > As far as we do not have *many* such forks, the situation is handable. > > [A part that recompiling all libraries will solve all the problems > skipped - as I said, I do not consider this feasible.] Okay, just to summarize: Am I correct that 1) Existing executables and dlls can still use the old API which will be provided by the new libc using the old ordinal numbers, 2) Existing static libraries can still be used if a) either the compilation and linkage is done only with old libraries and the old emx or b) the compilation and linkage is done with old libraries or libraries generated by (-D_OLD_EMX_STYLE) and the new libc, 3) On the long term all old libraries will (hopefully) vanish? Bye, Andreas