Date: Sat, 1 Nov 2003 02:54:31 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [Ux2bs_Archive] No. 219 ************************************************** Friday 31 October 2003 Number 219 ************************************************** Subjects for today 1 Re: UX2BS : Dave and Natalie" 2 Re: UX2BS : John Poltorak **= Email 1 ==========================** Date: Sat, 01 Nov 2003 17:39:47 -0800 From: "Dave and Natalie" Subject: Re: UX2BS On Fri, 31 Oct 2003 22:50:58 -0700 (MST), James Moe wrote: >On Fri, 31 Oct 2003 19:08:09 -0800, Dave and Natalie wrote: > >>I have >>gnurx.dll 40469 02-08-96 5:34p >>in e:/emx/dll. No idea where I got this >> > That is the same as what is here lurking is a dusty corner. It is *not* on my ux2bs >drive. It is not clear why sed would call it since your ux2 system is G:. It hsould be >using gnuregex.dll (3/31/98 6:52a 27284 G:\USR\lib\gnuregex.dll) or possibly >regex012.dll (6/16/99 3:40p 29993 G:\USR\lib\regex012.dll). > What version of sed are you using? IIRC it is Andrea Buening port of 4.05. Actually looking at sed with pmdll the only DLL sed is calling besides EMX & GCC321M is INTL.DLL which according to pmdll is unloadable due to ICONV.DLL. This is what we were talking about the other day, AZs little iconv while IIRC intl.dll is linked against GNU iconv. Still its funny because sed seems to work fine even though according to pmdll it shouldn't > Is this the ux2bs version that does not zap the existing environment before >rebuilding it? I found that to cause a lot of trouble because of libpath and path >conflicts. There was no way to get to all play together. Well it sure seems to be picking up stuff from the existing enviroment and yes it is creating conflicts. Hopefully have more time soon to look at it in depth Dave _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 2 ==========================** Date: Sat, 1 Nov 2003 17:42:22 +0000 From: John Poltorak Subject: Re: UX2BS On Fri, Oct 31, 2003 at 07:08:09PM -0800, Dave and Natalie wrote: > >> Everything went fine until it came time to build perl > > > >In that case you now have the basic UX2BS in place and should be capable > >of building certain programs. In fact you should already have built PDKSH, > >UNZIP, CRYPT and REGEX in the process. There should be seperate logs for > >each of these in \unixos2\logs. > > Ok, all these did build. Question, shouldn't unzip be built with > OS2_EAS and USE_UNSHRINK (which I believe the patent recently > expired).IIRC IBM uses unshrink in some archives. I'm not sure what the correct settings are for UNZIP, I just used the defaults. If you think some others are more appropriate then I'll change them. What exactly would you suggest as the right options for building it? How should your suggestions be implemented? > >> GNURX.DLL 0001:000009e2 > > > >Just wondered if you have a different GNURX.DLL which has crept in > >somewhere... This one should be 37672 bytes from 20/05/95 in \unixos2\dll. > > Yes, sorry for not debugging but the script ended after midnight and I > had to get up to work. This morning I just quickly wrote the email and > left for work. > I have > gnurx.dll ³ 40469³02-08-96³ 5:34p > in e:/emx/dll. No idea where I got this It may be from a newer version of SED, but I thought it would have been ignored by the BEGINLIBPATH setting... Maybe it was already in memory for some reason. > >Can you post a little snippet from around where it started looping? > > sure, from log > > Process terminated by SIGSEGV > .g:/unixos2/emx/bin/nm didn't seem to work right. Trying emxomfar > instead... > emxomfar didn't seem to work right. > Maybe this is a Cray...trying bld instead... Nothing specific comes to mind at the moment, but I'll check it against one of my logs. > >build perl > > > > > >by starting a new session from \unixos2\lib after removing the directory > >\unixos2\workdir\perl-5.8.0 > Everything went OK until the power failed Started over again > Perl built but got a lot of failures > Failed 74/726 test scripts, 89.81% okay. 644/67684 subtests failed, > 99.05% okay. > I had about 8 failures with my own build. > Alot of the failures seem related to this > f:/USR/BIN/sh.exe: G:/UNIXOS2/WORKDIR/PERL-5.8.0/T/PERL.EXE: cannot > execute binary file > Not sure why it is using f:/usr/bin/sh instead of G: > g:/uxixos2/workdir/perl-5.8.0/t/perl.exe is only 18128 bytes which is > actually pretty close to my old build size. Have you set UXRT and BLDRT to different drives? I haven't tested that myself > After perl I get this error > gzip: stdin: unexpected end of file > tar: "gzip" exit status 1 > The archive make-3.76.1.tar.gz does not appear to have extracted > correctly > so the build of make-3.76.1 is unable to continue. > Press any key to EXIT > make-3.76.1.tar.gz is only 6500 bytes so I guess the download failed. > Should be using wget. > > Then similar problems with autoconf-2.50.tar.gz. Shouldn't we be using > ver 2.57? UX2BS uses three different versions of Autoconf. Some versions work better with some apps than others! > Then automake is not even there so the script dies. > > Sorry I don't have more time right now to debug but I've been busy Since there seem to be some problems with the Perl build, it may be better to delete everything and start from sratch, making sure that all your archives are in a safe place so you don't need to download everything again. > Dave -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs