From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Thu, 21 Aug 2003 14:10:10 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 173 ************************************************** Wednesday 20 August 2003 Number 173 ************************************************** Subjects for today 1 Re: Innotek libc license & release issues (was Re: [EMX] Re: : Andreas Buening 2 [Ux2bs] Doesn't get any better than this! : T.Sikora" 3 Doesn't get any better than this! : T.Sikora" **= Email 1 ==========================** Date: Thu, 21 Aug 2003 00:15:00 +0200 From: Andreas Buening Subject: Re: Innotek libc license & release issues (was Re: [EMX] Re: Stefan Neis wrote: > > On Tue, 19 Aug 2003, Andreas Buening wrote: > > > > jep, I would say so. Can you give feedback to the list when you got > > > something from Knut? > > > > Sure. Here it is: > > Thanks for finding out some facts! Some other questions: ----------------------- Knut: > I've no idea, for building it all, it requires the CVS version > of GCC 3.2.2 usually. At least for OMF mode 3.2.2 is required. Me: Why? If it's based on emx and you use the same file names it should even link with gcc 2.7. Knut: Aout, probably, OMF probably not. We changed the ABI for OMF, there may also be header changes (_System) which isn't backward compatible. To be honest I don't really care supporting anything but the latest GCC build. If we reverse the question, if GCC 3.2.2 works with old EMX stuff. With a bit of work on both environment setup, libraries, headers, and compiler spec file, yes. Only I'm not going to do that. Me: But this is only related to the import libraries and the emx dlls themselves, normal dlls written in C are compatible upward and backward? Knut: They are, only you'll have to regenerate the OMF libraries. Explanation: void foo(); -> .globl _foo Previosly emxomf stripped the underscore. For ABI compatability reasons (VAC/Watcom/Watever OS/2 compiler) we have made that underscore-removing feature non default. This means that symbols in a.out and OMF object formats are identical. Import libraries can easily be regenerated from the a.out library or from .def or .imp file (which you may have to modify a bit). ----------------------- Hope, this helps. > > >This libc is based on glibc/bsd libc/emx/written from scratch. > > It's based on the sys library of emx (license reasons). > > That sys library originally was rather incomplete... > I'm wondering what's going to happen to e.g. fork(). Does "sys" mean the -Zsys library? That one without fork() and SIGCHLD? [snip] Bye, Andreas **= Email 2 ==========================** Date: Thu, 21 Aug 2003 22:59:33 -0400 From: "T.Sikora" Subject: [Ux2bs] Doesn't get any better than this! It's done. My vision of how it should be anyways. All the pkgs install the ux2 way. After it's done try lspkg in the ux2bs shell to view the ones installed. It's fully integrated and yet seperate. That FreeBSD style ports directory is so cool. Now we need port maintainers and README's on all this stuff. The package tools and a port maintainer HowTo for starters. ftp://os2ports.com/pub/unixos2/ux2bs/build_system/install/ux2bs_inst.cmd Just set your drive letters in the script and go. -- T.Sikora tsikora at ntplx dot net _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 3 ==========================** Date: Thu, 21 Aug 2003 22:59:33 -0400 From: "T.Sikora" Subject: Doesn't get any better than this! It's done. My vision of how it should be anyways. All the pkgs install the ux2 way. After it's done try lspkg in the ux2bs shell to view the ones installed. It's fully integrated and yet seperate. That FreeBSD style ports directory is so cool. Now we need port maintainers and README's on all this stuff. The package tools and a port maintainer HowTo for starters. ftp://os2ports.com/pub/unixos2/ux2bs/build_system/install/ux2bs_inst.cmd Just set your drive letters in the script and go. -- T.Sikora tsikora at ntplx dot net