From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Sat, 30 Mar 2002 04:20:51 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 179 ************************************************** Friday 29 March 2002 Number 179 ************************************************** Subjects for today 1 Re: Re: Building Perl.exe as a test of manhood ;-) : John Poltorak 2 Re: iconv.a : John Poltorak 3 Re: iconv.a : Andreas Buening 4 Re: Re: Building Perl.exe as a test of manhood ;-) : John Poltorak **= Email 1 ==========================** Date: Sat, 30 Mar 2002 11:03:10 +0000 From: John Poltorak Subject: Re: Re: Building Perl.exe as a test of manhood ;-) On Fri, Mar 29, 2002 at 11:13:12PM -0800, mlaitio wrote: > > > > > >Depends on what you want to do... > >If you want to build apps, you will need:- > > > I would just like to help for verifying that the tools in UnixOS2 works > and builds ok. I know that you have also done similar kind of work, > but I thought that I could be some kind of "double-checker" or verifier > for the basic stuff. Some degree of 'quality control' is something that we've been hoping to incorporate at some point so your offer is very welcome. However, please read my notes below. > Ie, if you have installation instructions for some tools, then I could > try to follow them, and if I found some mistakes, I could try to correct > them. > If I have understood, I should maybe start things in this order... > > 1) Install some UnixOS2 base packages > 2) Install/integrate gcc 3.03 to Unixos2-distribution > 3) Install "newest" autoconf > 4) Build and bash/pdksh from the UnixOS2-sources and install them to > UnixOS2-distribution > 5) Build and install some other basic libraries > - regex > - intl > - zlib > - ncurses > - gzip > - tar > - sed > - grep > - awk > - patch > 6) Build and install perl > 7) Build and install ??? At the moment almost all the current packages in the UnixOS/2 distro are assembled from existing ports simply by creating a new archive based on the one which exists in SlackWare. The components are simply copied rather than rebuilt. This is done for the sake of expediency as much as anything else. The primary goal is to provide a 'one stop shop' for OS/2 ports of Unix apps rather than having to scour ten Internet sites or more, never knowing which is the most recent version of an app. Currently, there are very few programs that have been built specifically for UnixOS/2. What I'd like to do before long is to rebuild all the packages from the scratch for a number of reasons including establishing a slightly different directory structure, one which is more FHS compliant. Also I'd like to be able to quickly incorporate LIBEMU when it becomes available. However before any rebuilding is done I would like to have and integrated build system in place which would allow every package to be built automatically without the need for any manual tweaking here and there. This is not going to be easy, but I think it's something which will save a lot of time in the long run. So, by all means see if you can rebuild perl, ncurses, etc. It will help to establish a robust build system which should work for everyone. > >There are actually a number of old apps which require an 'owner'. Ie. > >an OS/2 port was made a long time ago but the maintainer has disappeared > >or left the OS/2 scene. Often these apps have remained without any major > >changes anyway so we are not missing out, but it's always useful to have > >someone looking after them in case an update does arrive. I'm thinking > >specifically about apps such as DIFF, FIND, CPIO, FLEX, ASH etc. > > > At least for now I can not promise for begin to be an "owner" of any of > the ports, because I wont have that much time. But as I said, I would > like to help in checking that things which are included are supposed to > be easily buildable are really doing so and that correct versions of > each tool is included to the distribution. (According to the discussion > in this list during the last few weeks, there are lot of things like > whether to use IconV from Andrew Zabolotny or from GNU, and how to build > that from source in UnixOS2 distribution...) The iconv discussion has really been because of INTL.DLL. INTL is one of the DLLs shared by many apps and is included in the OS2LIBS package. I wanted to create an updated version, which is done by building GETTEXT, but to do that you also need ICONV, and I had difficulty locating it. > Mika -- John **= Email 2 ==========================** Date: Sat, 30 Mar 2002 16:56:55 +0000 From: John Poltorak Subject: Re: iconv.a On Sat, Mar 30, 2002 at 05:51:37PM +0100, Andreas Buening wrote: > John Poltorak wrote: > > > > On Fri, Mar 29, 2002 at 05:10:29PM +0100, Andreas Buening wrote: > > [snip] > > > > Btw. do you already have a unixos2-check script that tests > > > your build environment? > > > > Not at present, because I don't think we have established all the > > essential parts of that build environment. There are too many duplicates > > of REGEX and INTL as yet, and the behavior of various SHELLs is still > > unpredicatable. > > > > > I have some ideas how this could be implemented. > > > > Let's hear them then... > > I've written some autoconf code but I cannot upload these file > to ftp.unixos2.com/incoming (no permission) Dump it here:- ftp://www.eyup.org > bye, > Andreas -- John **= Email 3 ==========================** Date: Sat, 30 Mar 2002 17:51:37 +0100 From: Andreas Buening Subject: Re: iconv.a John Poltorak wrote: > > On Fri, Mar 29, 2002 at 05:10:29PM +0100, Andreas Buening wrote: [snip] > > Btw. do you already have a unixos2-check script that tests > > your build environment? > > Not at present, because I don't think we have established all the > essential parts of that build environment. There are too many duplicates > of REGEX and INTL as yet, and the behavior of various SHELLs is still > unpredicatable. > > > I have some ideas how this could be implemented. > > Let's hear them then... I've written some autoconf code but I cannot upload these file to ftp.unixos2.com/incoming (no permission) bye, Andreas -- One OS to rule them all, One OS to find them, One OS to bring them all and in the darkness bind them In the Land of Redmond where the Shadows lie. **= Email 4 ==========================** Date: Sat, 30 Mar 2002 20:22:13 +0000 From: John Poltorak Subject: Re: Re: Building Perl.exe as a test of manhood ;-) On Fri, Mar 29, 2002 at 11:13:12PM -0800, mlaitio wrote: > If I have understood, I should maybe start things in this order... > > 1) Install some UnixOS2 base packages > 2) Install/integrate gcc 3.03 to Unixos2-distribution > 3) Install "newest" autoconf > 4) Build and bash/pdksh from the UnixOS2-sources and install them to > UnixOS2-distribution > 5) Build and install some other basic libraries > - intl It would be great if you could build this. I'm getting hopelessly lost with it... From what I have read these two archives should be all you need:- http://195.131.97.220:9000/zap/os2/gettext%2dos2%2d0.11.1%2dbin.zip http://195.131.97.220:9000/zap/os2/iconv%2d0.1.0.zip You even get a Makefile specially built for OS/2, so you only need to run make... > Mika -- John