Date: Sun, 26 Jan 2003 02:28:38 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [Ux2bs_Archive] No. 58 ************************************************** Saturday 25 January 2003 Number 58 ************************************************** Subjects for today 1 Re: install.exe : Maynard" 2 Re: Help Getting Perl to Run : Maynard" 3 Re: Using Posix/2 headers to build Perl : John Poltorak 4 Re: Starting from scratch : John Poltorak 5 Re: Help Getting Perl to Run : John Poltorak 6 Re: Starting from scratch : Maynard" 7 Re: Starting from scratch : Maynard" 8 UX2BS Webpage : Ted Sikora 9 Re: [Fwd: UX2BS Webpage] : Ted Sikora 10 Re: Starting from scratch : Dave Saville" 11 Re: Starting from scratch : Dave Saville" 12 Apps to try : John Poltorak 13 Re: UX2BS Webpage : Maynard" 14 Re: Apps to try : Maynard" 15 Re: Help Getting Perl to Run : Maynard" 16 Re: Re: install.exe : Hakan" 17 Re: Help Getting Perl to Run : Hakan" 18 Re: Building perl-5.8.0 : Henry Sobotka 19 Info-ZIP : Maynard" 20 Re: Starting from scratch : Maynard" 21 Re: Help Getting Perl to Run : Hakan" 22 RECODE built : John Poltorak 23 Re: Apps to try : Maynard" 24 Re: Help Getting Perl to Run : Hakan" 25 Re: [Fwd: UX2BS Webpage] : John Poltorak 26 Building perl-5.8.0 : Stefan.Neis at t-online.de 27 Re: Help Getting Perl to Run : John Poltorak 28 Re: Starting from scratch : John Poltorak 29 Re: Apps to try : John Poltorak 30 Re: Help Getting Perl to Run : John Poltorak 31 Impressive! : Ted Sikora 32 MAN pages : John Poltorak 33 Re: Impressive! : Ted Sikora 34 Re: Impressive! : Maynard" 35 Re: Help Getting Perl to Run : Stefan.Neis at t-online.de 36 Re: Impressive! : Ted Sikora 37 Re: Apps to try : John Poltorak 38 Re: Apps to try : Stefan.Neis at t-online.de **= Email 1 ==========================** Date: Sun, 26 Jan 2003 00:07:49 -0600 (CST) From: "Maynard" Subject: Re: install.exe On Sat, 25 Jan 2003 23:46:54 -0500 (EST), Hakan wrote: >Thank you for looking. I made a mistake, though. The program is >called install.exe, not installer.exe, and Henry Sobotka has explained >that it was part of an earlier distribution (the documentation is thus >not up-to-date.) None-the-less, I find one in \usr\bin: install.exe 7190 3-31-1998 1:22a I'm not sure what put it there, but I am sure that \usr was deleted earlier today. -- Maynard _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 2 ==========================** Date: Sun, 26 Jan 2003 00:31:34 -0600 (CST) From: "Maynard" Subject: Re: Help Getting Perl to Run Hakan, >More comments on the process: Thank you. >* I suggest the script check for the presence of all required >components *before* it begins it efforts. For instance, if LINK386.EXE >is required and needs to be in the path, that should be checked before >the first file is downloaded. Yes. I'll work on this. >* One should not have to download all files again if the process >fails. You're correct of course; however there are challenges to this which include factors of not knowing what you have already downloaded to where, and ensuring that your version is most current. Until you run 'build', the downloads aren't very big. I've been pondering the idea of identifying a local archive source outside of \unixos2\ because those are the real big ones, and some of us maintain multiple build environments which should each be able to reference the same local repository. I need sleep, -- Maynard _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 3 ==========================** Date: Sun, 26 Jan 2003 08:46:07 +0000 From: John Poltorak Subject: Re: Using Posix/2 headers to build Perl On Sat, Jan 25, 2003 at 10:40:25PM -0500, Marty wrote: > On Sat, 25 Jan 2003 21:21:35 +0000, John Poltorak wrote: > > > Marty, > > > > I'm pleased to see you having a go at this, and hope you make some > > progress. > > > > Can you send any patches for the files you change? > > I could, but I don't know if this is how things should be. Basically, I'm just > hacking together what I have to in order to get it going. There are probably more > appropriate places for these additions, so I'll talk to the Posix/2 folks about it. > If we put things in the *right* place then other projects have a better chance of > working. Sure, but as far as the patches go I just meant having patches available for people on this so that they could try following your progress and maybe help speed up the process. > > BTW I forwarded your email to the posix2 mailing list - maybe you should > > join that... > > > > You can easily find it if you do a Google search for 'posix/2'. > > Grumble... *another* mailing list. I guess I must if I want to do this right. Yes, I know it's a pain. I've tried to get some of the principle posix/2 protagonists onto this list, but the have been reluctant to sign up so far. -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 4 ==========================** Date: Sun, 26 Jan 2003 09:11:55 +0000 From: John Poltorak Subject: Re: Starting from scratch On Sat, Jan 25, 2003 at 06:40:06PM -0600, Maynard wrote: > On Sat, 25 Jan 2003 21:32:36 +0000, John Poltorak wrote: > > >What you could do is an RSYNC with my system and carry on after changing > >make_distro.cmd to start from the point of failure. > > I deleted all of workdir and ran the complete make_distro.cmd > > Judging from .... > [P:\UNIXOS2\LIB]sh > # autoconf --version > autoconf (GNU Autoconf) 2.57 (release for OS/2) > > I take it that the third autoconf was successful. If you've reached this point you are at an important milestone and things should be more straightforward. We can concentrate on getting individual apps working now. > But that looks like the end. > > gettext.log tails with: > P:/usr/bin/install.exe: msguniq.exe: No such file or directory > make[2]: *** [install-binPROGRAMS] Error 1 > make[2]: Leaving directory `P:/unixos2/workdir/gettext-0.11.5/src' > make[1]: *** [install-am] Error 2 > make[1]: Leaving directory `P:/unixos2/workdir/gettext-0.11.5/src' > make: *** [install-recursive] Error 1 I hadn't noticed that myself, and you are right. There is a problem and quite a few programs don't seem to get built. This needs further investigation. I've just spotted this msguniq.exe program under src\.libs, so something isn't quite right. However, the important thing is that the INTL library and DLL look to be built, which means that any subsequent apps where we can run configure --without-included-gettext ought to be built this way which will provide a considerable reduction in size. > texinfo.log tails with: > checking for sigblock... no > ./configure[3961]: syntax error: `done' unexpected > make > make: *** No targets specified and no makefile found. Stop. > make: Nothing to be done for `install'. Can you tell whether autoconf was run. It shouldn't. The supplied configure script is fine and gets messed up when you run autoconf. > automake.log tails with: > automake.texi:5328: Misplaced `{'. > automake.texi:5328: Misplaced `}'. > Making info file `automake.info' from `automake.texi'. > make[1]: *** [automake.info] Error 1 > make[1]: Leaving directory `P:/unixos2/workdir/automake-1.7.2' > make: *** [install-recursive] Error 1 Automake fails because you don't have a recent enough makeinfo, ie. the previous app, texinfo failed. -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 5 ==========================** Date: Sun, 26 Jan 2003 09:30:43 +0000 From: John Poltorak Subject: Re: Help Getting Perl to Run On Sat, Jan 25, 2003 at 07:13:06PM -0500, Hakan wrote: > John, > > As much sense as it does make to build perl on my machine, I have > limited time and, at least at this time, no interest in learning perl. > The only reason I am trying to install it is so I can use swish-e to > retrieve and index various websites I have an interest in and swish-e > apparently uses a perl script to do so.. Further, should I attempt to > build perl, I assume I have to install a C compiler and spend time > getting that to work. Hakan, I can't help wondering why you signed up for this list... It has been made abundantly clear on numerous occasions that the whole point of the list was to come up with a standard, easy to use, build environment. Whether you like it or not Perl is central part of that build environment and without it you won't get very far. If you don't want to build it, there will be very little else you can do and you won't be able to make any sense of the ongoing discussions. > > This is the problem with much of the unix software available -- you > download the main application from one site, read the instructions and > find out that you have to download several other packages the main > application in turn depends on. Fine, you gather the various > components, go through a poorly documented installation process and > then the program does not work. > > In my case the perl package required emx (which I had) but also another > dll I had to download. Since there was no mention where exactly this > dll needed to reside, I dropped it in one of the lib directories. These are problems that we have all had to endure over the years, which should bring home the whole point of putting together a Unix-like environment from scratch and ensuring the whole works together smoothly. It is only by putting this build together in a controlled way that we can ensure it contains all the necessary elements for all programs to function correctly. > Why is it that the OS/2 versions of the unix programs cannot come ready > to run and with a decent installer which checks the installation so > that the user can actually run the application immediately once it is > installed?? You have already said that your time is limited. I, too, only have 24 hrs in my days. Who do you think will provide all these additional features you demand for free? > Hakan -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 6 ==========================** Date: Sun, 26 Jan 2003 11:51:27 -0600 (CST) From: "Maynard" Subject: Re: Starting from scratch GETTEXT: the log indicates: Libraries have been installed in: P:/usr/lib and tails with: P:/usr/bin/install.exe msguniq.exe P:/usr/bin/msguniq.exe P:/usr/bin/install.exe: msguniq.exe: No such file or directory make[2]: *** [install-binPROGRAMS] Error 1 make[2]: Leaving directory `P:/unixos2/workdir/gettext-0.11.5/src' make[1]: *** [install-am] Error 2 make[1]: Leaving directory `P:/unixos2/workdir/gettext-0.11.5/src' make: *** [install-recursive] Error 1 It doesn't appear that any .exe files were installed, which may be OK. There are many .exe files in \UnixOS2\workdir\gettext-0.11.5\src\.libs\ TEXINFO: appears OK, .... from the log: WARNING: You must install texinfo.tex and txi-??.tex manually, on the disk: Directory: P:\usr\local\TMP\share\automake texinfo.tex 208557 1-26-2003 10:58a A --there are no txi-??.tex files in \usr \usr\bin: 1-26-03 10:44 18,120 0 perl.exe 1-26-03 10:50 124,078 0 yacc.exe 1-26-03 10:50 139,268 0 flex.exe 1-26-03 10:57 174,244 0 captoinfo.exe 1-26-03 10:57 174,244 0 infotocap.exe 1-26-03 10:57 174,244 0 tic.exe 1-26-03 10:57 141,096 0 toe.exe 1-26-03 10:57 38,635 0 clear.exe 1-26-03 10:57 153,698 0 infocmp.exe 1-26-03 10:57 122,757 0 reset.exe 1-26-03 10:57 248,098 0 tack.exe 1-26-03 10:57 65,610 0 tput.exe 1-26-03 10:57 122,757 0 tset.exe 1-26-03 11:00 269,766 0 make.exe 1-26-03 11:15 333,628 0 info.exe 1-26-03 11:15 132,832 0 infokey.exe 1-26-03 11:15 301,237 0 makeinfo.exe 1-26-03 11:15 148,134 0 install-info.exe 1-26-03 11:15 23,490 0 texi2dvi 1-26-03 11:15 134,710 0 texindex.exe AUTOMAKE 1.7.2 looks to have failed: from the log: make[1]: Entering directory `P:/unixos2/workdir/automake-1.7.2' P:/bin/sh /unixos2/workdir/automake-1.7.2/lib/missing --run makeinfo -I . \ -o automake.info `test -f 'automake.texi' || echo './'`automake.texi ./version.texi:30: Unknown command `(#)PD'. makeinfo: Removing output file `automake.info' due to errors; use --force to pre make[1]: *** [automake.info] Error 1 make[1]: Leaving directory `P:/unixos2/workdir/automake-1.7.2' make: *** [install-recursive] Error 1 _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 7 ==========================** Date: Sun, 26 Jan 2003 11:52:58 -0600 (CST) From: "Maynard" Subject: Re: Starting from scratch On Sun, 26 Jan 2003 09:11:55 +0000, John Poltorak wrote: >Automake fails because you don't have a recent enough makeinfo, ie. the >previous app, texinfo failed. # pwd / # makeinfo --version makeinfo (GNU texinfo) 4.3 _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 8 ==========================** Date: Sun, 26 Jan 2003 12:06:17 -0500 From: Ted Sikora Subject: UX2BS Webpage http://os2ports.com/content/sections/ux2bs -- Ted Sikora tsikora at ntplx.net _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 9 ==========================** Date: Sun, 26 Jan 2003 12:17:53 -0500 From: Ted Sikora Subject: Re: [Fwd: UX2BS Webpage] You guys may want to add a UX2BS section to Unixos2.org I'm starting to get confused(not too hard) Will there be a UnixOS/2 (aka Polterware) distribution. Or will the BS be the replacement or just the base environment and ports(ala FreeBSD) directory for UnixOS/2? The guys on the Posix/2 and EMX lists seem really pissed off about it so it must be * Right *! (Screw'em) Maybe we need a * Mission Statement * to clarify things on UnixOS2.org? To the outsider it looks like a mish-mash of projects. Ted Sikora wrote: > You still alive? UnixOS2 Presents: (That Dragon is so cool!) > > -------- Original Message -------- > Subject: UX2BS Webpage > Date: Sun, 26 Jan 2003 12:06:17 -0500 > From: Ted Sikora > To: ux2bs at powerusersbbs.net > > http://os2ports.com/content/sections/ux2bs > > > -- > Ted Sikora > tsikora at ntplx.net > > -- -- Ted Sikora tsikora at ntplx.net **= Email 10 ==========================** Date: Sun, 26 Jan 2003 12:44:44 +0000 (GMT) From: "Dave Saville" Subject: Re: Starting from scratch On Sat, 25 Jan 2003 14:48:53 -0600 (CST), Maynard wrote: >On Sat, 25 Jan 2003 14:45:43 +0000, John Poltorak wrote: > >Dave: Failed 5/726 test scripts, 9/68656 subtests failed, >Maynard: Failed 4/726 test scripts, 6/68650 subtests failed, > >note the different number of subtests run. > > >>> lib/os2_base.t 1 256 19 1 5.26% 8 >>Hmm... >pre-existing \usr\lib\perlB12E.dll > > >>> op/stat.t 73 1 1.37% 44 >me too this time; at line 318; this has passed before >may have to do with how it's invoked, and piped output. >It passes on a standalone test: > >[P:\UNIXOS2\workdir\perl-5.8.0\t]perl op\stat.t |grep 44 >ok 44 - -t on STDIN > > >>There's no hostname failure. Have you added something? >This failure can be removed by setting a value for DOMAIN in the build >environment. >Also, it may not be tested under all configurations ?? > >lib/Net/t/hostname >Use of uninitialized value in string eq at ../lib/Net/t/hostname.t line >39 >i.e. DOMAIN Actually there was a change from my first attempts in that I had resolv2 in the /etc this time - I also run bind on my firewall which knows about my local net - Maybe this makes a difference? -- Regards Dave Saville _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 11 ==========================** Date: Sun, 26 Jan 2003 12:46:46 +0000 (GMT) From: "Dave Saville" Subject: Re: Starting from scratch On Sat, 25 Jan 2003 20:28:55 +0000, John Poltorak wrote: >> >But if you have had problems downloading some files, it may be worth >getting them beforehand just in case it fails again. I would like to know *why* that early download failed and all the rest fetched OK though. -- Regards Dave Saville _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 12 ==========================** Date: Sun, 26 Jan 2003 13:04:53 +0000 From: John Poltorak Subject: Apps to try If you have got as far as building and installing Autoconf v2.57, you may be able to paste this into a cmd file and run it:- ... call build gettext call build texinfo call build automake call build bison call build patch call build indent call build dialog call build add call build vile call build tin call build openssl call build lynx Please let me know how you get on. You may need to check build.table to make sure it contains entries for all of these. Also delete any directories in workdir where you have previously attempted to build any of them. -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 13 ==========================** Date: Sun, 26 Jan 2003 13:07:23 -0600 (CST) From: "Maynard" Subject: Re: UX2BS Webpage On Sun, 26 Jan 2003 12:06:17 -0500, Ted Sikora wrote: >http://os2ports.com/content/sections/ux2bs Excellent! I'm confused however, throughout the sites, by the of term "packages"; unsure of whether it refers to "binaries" or "sources". -- Maynard _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 14 ==========================** Date: Sun, 26 Jan 2003 13:19:21 -0600 (CST) From: "Maynard" Subject: Re: Apps to try >call build bison [P:\]bison --version bison (GNU Bison) 1.875 >call build patch [P:\]patch --version GNU patch 2.5 >call build indent [P:\]indent --version GNU indent 2.2.9 >call build dialog [P:\]dialog --version Version: 0.9b-20020814 >call build add [P:\]add --version add: invalid option `--' Usage: add [options] [scripts] >call build vile ./configure[4775]: syntax error: `if' unmatched make make: *** No targets specified and no makefile found. Stop. >call build tin --nope-- >call build openssl -- I don't think so -- Directory of P:\UnixOS2\workdir\openssl-0.9.7\out\*.* 6,946,744 bytes in 28 files -- but not distributed from workdir -- >call build lynx [P:\]lynx --version Lynx Version 2.8.4rel.1 (17 Jul 2001) Built on os2-emx Jan 26 2003 12:22:40 _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 15 ==========================** Date: Sun, 26 Jan 2003 13:40:44 -0600 (CST) From: "Maynard" Subject: Re: Help Getting Perl to Run Hakan, >I promptly ran into a problem with >LINK386.EXE not being present. I had that problem also. It's one of the Warp Install options. You can maybe find it on your source disks or run Selective Install -- Maynard _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 16 ==========================** Date: Sun, 26 Jan 2003 13:41:44 -0500 (EST) From: "Hakan" Subject: Re: Re: install.exe Maynard, Thanks, even thought the build script aborted early, I do have install.exe in the same directory so I will see if I can do anything worthwhile with it, i.e., automatically configure perl. Hakan On Sun, 26 Jan 2003 00:07:49 -0600 (CST), Maynard wrote: >On Sat, 25 Jan 2003 23:46:54 -0500 (EST), Hakan wrote: > >>Thank you for looking. I made a mistake, though. The program is >>called install.exe, not installer.exe, and Henry Sobotka has explained >>that it was part of an earlier distribution (the documentation is thus >>not up-to-date.) > >None-the-less, I find one in \usr\bin: > install.exe 7190 3-31-1998 1:22a > >I'm not sure what put it there, but I am sure that \usr was deleted >earlier today. > >-- Maynard > > > >_______________________________________________ >UX2BS mailing list >UX2BS at powerusersbbs.net >http://powerusersbbs.net/mailman/listinfo/ux2bs > > _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 17 ==========================** Date: Sun, 26 Jan 2003 13:48:47 -0500 (EST) From: "Hakan" Subject: Re: Help Getting Perl to Run John, >I can't help wondering why you signed up for this list... To learn about the efforts of this group and perhaps get some unix applications working on my system without tinkering taking on a life on its own. >It has been made abundantly clear on numerous occasions that the whole >point of the list was to come up with a standard, easy to use, build >environment. Whether you like it or not Perl is central part of that build >environment and without it you won't get very far. If you don't want to >build it, there will be very little else you can do and you won't be able >to make any sense of the ongoing discussions. OK, as you may have seen in a later posting I did decide to build perl and other applications whereupon I promptly ran into a problem with LINK386.EXE not being present. I just searched my harddisks and LINK386.EXE is nowhere to be found -- where is a "novice" user to get LINK386.EXE from (and I am far from a novice user, although newcomer to UnixOS/2)? You may also have seen that I happened to see an error message I got while downloading stuff "rsync error: syntax or usage error (code 1) at main.c(935)" I have no idea what this means and whether I should be concered or not. >> >> This is the problem with much of the unix software available -- you >> download the main application from one site, read the instructions and >> find out that you have to download several other packages the main >> application in turn depends on. Fine, you gather the various >> components, go through a poorly documented installation process and >> then the program does not work. >> >> In my case the perl package required emx (which I had) but also another >> dll I had to download. Since there was no mention where exactly this >> dll needed to reside, I dropped it in one of the lib directories. > >These are problems that we have all had to endure over the years, which >should bring home the whole point of putting together a Unix-like >environment from scratch and ensuring the whole works together smoothly. >It is only by putting this build together in a controlled way that we can >ensure it contains all the necessary elements for all programs to function >correctly. > > >> Why is it that the OS/2 versions of the unix programs cannot come ready >> to run and with a decent installer which checks the installation so >> that the user can actually run the application immediately once it is >> installed?? > >You have already said that your time is limited. I, too, only have 24 hrs >in my days. Who do you think will provide all these additional features >you demand for free? I know. John, I can see your points and I think you can see my points as well. However, the Unix developer community seems to have a mindset of "if you cannot figure out how to install/configure/run this software, you should not be running it." Further, tinkering seems to be goal of its own rather than using the software in a productive manner. Re the various installation scripts, they should always check not only for other required software but also make sure the system is configured in an acceptable manner *before* even attempting downloading/building etc. Further, complete logging of the various steps is mandatory. Hakan _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 18 ==========================** Date: Sun, 26 Jan 2003 14:00:42 -0500 From: Henry Sobotka Subject: Re: Building perl-5.8.0 Stefan.Neis at t-online.de wrote: > > Also, during "Configure" I get lots of warnings along the lines of > > sqrtl() NOT found. > > *** WHOA THERE!!! *** > > The previous value for $d_sqrtl on this machine was "define"! > > Keep the previous value? [y] > which shouldn't cause any harm as "Keeping the previous value" is the > preselected solution, but it's still somewhat ugly to essentially get > such a warning for every single one of those symbols that are defined in > c_alias.[a,lib]. Am I the only one to get those warnings or do others > have the same problem? Here when Configure tries the quick nm route, defines always get messed up. But when I let it do the compilation tests, they all get found. > Afterwards, I extended C_INCLUDE_PATH to really point to Posix/2 headers > first and retried compiling and got the same problems/solutions reported > by John on unixos2 and/or posix2 mailing lists (where I also posted my > details). Anybody already found the right place to add "-lcExt" for building > a Posix/2-based Perl? I would suggest setting it up in hints/os2.sh (libc variable perhaps?) before running Configure. h~ _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 19 ==========================** Date: Sun, 26 Jan 2003 14:59:18 -0600 (CST) From: "Maynard" Subject: Info-ZIP I had no trouble with zip23.tar.gz as per the file INSTALL: make -f os2\makefile.os2 gcc sources: http://www.info-zip.org/pub/infozip/Zip.html#Sources perhaps I can fathom how to tweak certain defaults, most importantly case sensitivity in unzipping of individual files Later, -- Maynard _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 20 ==========================** Date: Sun, 26 Jan 2003 15:02:50 -0600 (CST) From: "Maynard" Subject: Re: Starting from scratch On Sun, 26 Jan 2003 20:28:55 +0000, John Poltorak wrote: >Can you post dir \usr\local\bin\* ? 1-26-03 9:13 295,055 0 info.exe 1-26-03 9:13 132,832 0 infokey.exe 1-26-03 9:13 301,237 0 makeinfo.exe 1-26-03 11:01 7,971 0 autoconf 1-26-03 11:01 8,265 0 autoheader 1-26-03 11:01 34,800 0 autom4te 1-26-03 11:01 18,237 0 autoreconf 1-26-03 11:01 16,714 0 autoscan 1-26-03 11:01 33,950 0 autoupdate 1-26-03 11:01 3,764 0 ifnames 1-26-03 12:01 348,263 0 bison.exe 1-26-03 12:01 47 0 yacc 1-26-03 12:02 222,701 0 patch 1-26-03 12:06 190,743 0 indent.exe 1-26-03 12:06 74,260 0 texinfo2man.exe 1-26-03 12:07 213,431 0 dialog.exe 1-26-03 12:08 143,200 0 add.exe 1-26-03 12:08 4,319 0 add.hlp 1-26-03 12:23 1,534,196 0 lynx.exe _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 21 ==========================** Date: Sun, 26 Jan 2003 15:02:59 -0500 (EST) From: "Hakan" Subject: Re: Help Getting Perl to Run Maynard, I eventually copied it from my development machine which has VAC++ 4 and the Developer's Toolkit. An ordinary user, however, would have no idea of how to proceed. Again, the installation script should check for its presence at the very beginning, and, if not found, suggest where the user could find the file. The process has to be foolproof. Hakan On Sun, 26 Jan 2003 13:40:44 -0600 (CST), Maynard wrote: >Hakan, > >>I promptly ran into a problem with >>LINK386.EXE not being present. > >I had that problem also. It's one of the Warp Install options. You can >maybe find it on your source disks or run Selective Install > >-- Maynard > > > >_______________________________________________ >UX2BS mailing list >UX2BS at powerusersbbs.net >http://powerusersbbs.net/mailman/listinfo/ux2bs > > _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 22 ==========================** Date: Sun, 26 Jan 2003 15:17:39 +0000 From: John Poltorak Subject: RECODE built I managed to RECODE built, but it needed a little user intervention... The original configure script provided was used, ie. I didn't run autoconf. However it did require LN, which isn't part of the build environment, but so I created ln.cmd:- at echo off cp -p %1 %2 Now it gets as creating src\recode which can be converted into an OS/2 executable by running EMXBIND. So now, all I need to do is figure out a way to automate this part. Any suggestions? I may be able to add some parameters to Make but not sure what... -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 23 ==========================** Date: Sun, 26 Jan 2003 15:37:25 -0600 (CST) From: "Maynard" Subject: Re: Apps to try On Sun, 26 Jan 2003 21:00:46 +0000, John Poltorak wrote: >> GNU patch 2.5 > >Bad. Should be 2.54, don't know why it isn't. I've no doubt that the version is in fact 2.54 and that it just isn't reporting that fact. >Copy \unixos2\scripts\pre-process as >vile in the same directory. ?^?^?^?^?^?^?^?^?^?^?^ need more complete specification of sourcefile; or update of your rsync server [p:\]type ux2_update.cmd rsync -av 213.152.37.92::build P:\UnixOS2 -- Maynard _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 24 ==========================** Date: Sun, 26 Jan 2003 16:54:21 -0500 (EST) From: "Hakan" Subject: Re: Help Getting Perl to Run Better to check for the presence of LINK386.EXE before the process is started, not when it is needed. BTW, I simply reran the ux2_bootstrap.cmd file after finding LINK386 and copying it to C:\OS2\SYSTEM. However, the build script said it could not find it in the path (C:\OS2\SYSTEM is in the path) so I quickly copied it into d:\usr\bin in another CMD window and there it seemed it could be found. Luckily it seems that the files did not need to be downloaded again so the script began assembling the various components and is now (after three hours) still building perl, making encode. Does the build script use the PATH variable or does it use another path? Hakan On Sun, 26 Jan 2003 21:25:12 +0000, John Poltorak wrote: >On Sun, Jan 26, 2003 at 10:09:46PM +0100, Stefan.Neis at t-online.de wrote: > >> > You do get a warning about LINK386.EXE not being on the path and that you >> > could encounter problems. >> > >> > If you like I could output a stupid message like:- >> > >> > 'Press C to continue or any other key to abort. >> > By selecting C I agree that I will not winge about missing elements >> > in the Build System' >> >> At the degree of automation we reached, I'd prefer to actually have the >> thing stop with a "You have not installed a mandatory element in the build >> system, can't continue". > >OK, I guess I could put that in instead. The check was only put in as an >afterthought, since I assumed everyone already had it. > >> Continuing silently makes it _much_ harder to dig >> out the real problem from the log files - see my problem with DBProf which >> presumably broke my whole attempts at building/installing Perl and required >> two or three weeks to be noticed by myself ... :-( >> >> > > Further, complete logging of the various steps is mandatory. >> > >> > You show me how, and I will gladly include it. >> >> The perl.log file is quite nice already, IMHO. > >The individual logging of each build of an app is OK. Hakan is complaining >about the lack of logging of the install of the build system itself. > >I agree that this is a shortcoming, but without access to TEE at that >point in the process, I don't see any way to log it. > > >> Regards, >> Stefan > > >-- >John > > > > >_______________________________________________ >UX2BS mailing list >UX2BS at powerusersbbs.net >http://powerusersbbs.net/mailman/listinfo/ux2bs > > _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 25 ==========================** Date: Sun, 26 Jan 2003 17:22:05 +0000 From: John Poltorak Subject: Re: [Fwd: UX2BS Webpage] On Sun, Jan 26, 2003 at 12:17:53PM -0500, Ted Sikora wrote: > You guys may want to add a UX2BS section to Unixos2.org > > I'm starting to get confused(not too hard) Will there be a > UnixOS/2 (aka Polterware) distribution. Or will the BS be the > replacement or just the base environment and ports(ala FreeBSD) > directory for UnixOS/2? > The guys on the Posix/2 and EMX lists seem really pissed off about it so > it must be * Right *! (Screw'em) Those lists are virtually dead. Posix/2 had hardly any postings for around 18 months. Similarly EMX is completely devoid of any traffic. > Maybe we need a * Mission Statement * to clarify things on UnixOS2.org? > > To the outsider it looks like a mish-mash of projects. I'm not sure about any mission statements, but my goal has always been to produce some sort of UnixOS/2 distro. It has become apparent that without a standard build environment it is difficult to just collect various packages from every porter and simply unzip them and expect them to work. Also I don't see how any pkgs can be produced without having a standard build environment. I'm actually quite pleased with how the build system is working and that is what I intend to be concentrating on for the time being, until we have something which resembles a usable distro. Once we have that then we can think of pkg handling, although idealy, the making of pkgs could be integrated into the build system itself. There seem to be a number of options in many apps for distributing that app, but I haven't even begun to explore those and would not want to start re-inventing the wheel if something perfectly adequate already exists. The reason for wanting a seperate list for ux2bs was to keep the traffic down to manageable proportions for those people not really involved with building apps. Around six months ago when a number of us were testing Perl builds there were complaints about too much traffic and suggestions that the list should be split, and I think it was a fair point. So now I see the unixos2 list as a place for general discussion whereas ux2bs is more focused on building apps within the framework of the build system. Unfortunately, there are certain key, knowledgeable people that I have been unable to entice onto the ux2bs list yet, so I often repeat posts to elicit responses from those people... -- John **= Email 26 ==========================** Date: Sun, 26 Jan 2003 18:55:58 +0100 From: Stefan.Neis at t-online.de Subject: Building perl-5.8.0 Hi, Some more details on my attempts of building perl-5.8.0 I tried to build perl using Posix/2 headers, failed to set C_INCLUDE_PATH properly and finally noticed, that I was getting some error from the build _all_the_time_, just never noticed it, because "make harness" - though not as succesful as for others - still worked relatively nicely. So here's what I get when trying to build Perl within John's standard build environment: gcc -c -Zomf -Zmt -DDOSISH -DOS2=2 -DEMBED -I. -D_EMX_CRT_REV_=64 -O2 -fomit-frame-pointer -malign-loops=2 -malign-jumps=2 -malign-functions=2 -s -DVERSION=\"20000000.00_01\" -DXS_VERSION=\"20000000.00_01\" -Zdll "-I../../.." -DPERLDBf_NONAME=0x40 -DPERLDBf_GOTO=0x80 -DG_NODEBUG=32 -DPL_NEEDED DProf.c DProf.xs:90: field `prof_start' has incomplete type DProf.xs:91: field `prof_end' has incomplete type DProf.xs: In function `dprof_times': DProf.xs:174: dereferencing pointer to incomplete type DProf.xs:175: dereferencing pointer to incomplete type DProf.xs: In function `prof_dump_until': DProf.xs:241: storage size of `t1' isn't known DProf.xs:241: storage size of `t2' isn't known DProf.xs: In function `prof_mark': DProf.xs:294: storage size of `t' isn't known DProf.xs: In function `test_time': DProf.xs:403: storage size of `t1' isn't known DProf.xs:403: storage size of `t2' isn't known make[2]: *** [DProf.obj] Error 1 make[2]: Leaving directory `/unixos2/workdir/perl-5.8.0/ext/Devel/DProf' make[1]: *** [lib/auto/Devel/DProf/DProf.dll] Error 2 make[1]: Leaving directory `/unixos2/workdir/perl-5.8.0' make: *** [install] Error 2 This error causes both "make" and the following "make install" to stop and probably explains all problems of my attempts to run perl harness. I suppose it would be preferable to just completely stop the build on such errors instead of just going on with the next command of the build script .... Anyway, the real problem behind it apparently is that HAS_TIMES is not defined in config.h (i.e. I have /*#define HAS_TIMES / **/ in there), so sys/times.h is not included in perl.h and so the definition of "struct tms" is missing. What experiences do others have in that respect? Is compiling that file working for anybody and what does config.h say about HAS_TIMES in your case? Also, during "Configure" I get lots of warnings along the lines of > sqrtl() NOT found. > *** WHOA THERE!!! *** > The previous value for $d_sqrtl on this machine was "define"! > Keep the previous value? [y] which shouldn't cause any harm as "Keeping the previous value" is the preselected solution, but it's still somewhat ugly to essentially get such a warning for every single one of those symbols that are defined in c_alias.[a,lib]. Am I the only one to get those warnings or do others have the same problem? Afterwards, I extended C_INCLUDE_PATH to really point to Posix/2 headers first and retried compiling and got the same problems/solutions reported by John on unixos2 and/or posix2 mailing lists (where I also posted my details). Anybody already found the right place to add "-lcExt" for building a Posix/2-based Perl? Regards, Stefan _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 27 ==========================** Date: Sun, 26 Jan 2003 20:10:16 +0000 From: John Poltorak Subject: Re: Help Getting Perl to Run On Sun, Jan 26, 2003 at 01:48:47PM -0500, Hakan wrote: > John, > > >I can't help wondering why you signed up for this list... > > To learn about the efforts of this group and perhaps get some unix > applications working on my system without tinkering taking on a life on > its own. Hakan, You must understand that this is work in progress rather than a finished project. It is still at a very early stage, but does show promise. > OK, as you may have seen in a later posting I did decide to build perl > and other applications whereupon I promptly ran into a problem with > LINK386.EXE not being present. I just searched my harddisks and > LINK386.EXE is nowhere to be found -- where is a "novice" user to get > LINK386.EXE from (and I am far from a novice user, although newcomer to > UnixOS/2)? LINK386.EXE is part of OS/2. It is something that always gets installed whenever I install OS/2. I was under the impression that most people had it installed, but it seems that this is not the case. > You may also have seen that I happened to see an error message I got > while downloading stuff "rsync error: syntax or usage error (code 1) at > main.c(935)" I have no idea what this means and whether I should be > concered or not. Neither have I. What would you like me to do about it? > >> Why is it that the OS/2 versions of the unix programs cannot come ready > >> to run and with a decent installer which checks the installation so > >> that the user can actually run the application immediately once it is > >> installed?? > > > >You have already said that your time is limited. I, too, only have 24 hrs > >in my days. Who do you think will provide all these additional features > >you demand for free? > > I know. John, I can see your points and I think you can see my points > as well. However, the Unix developer community seems to have a mindset > of "if you cannot figure out how to install/configure/run this > software, you should not be running it." Further, tinkering seems to > be goal of its own rather than using the software in a productive > manner. I am not trying to re-educate the Unix developer community. All I am interested in is having the use of some of the fine tools they have developed, available to me on OS/2. Unfortunately, having to contend with lack of user-friendliness is the price you have to pay. > Re the various installation scripts, they should always check not only > for other required software but also make sure the system is configured > in an acceptable manner *before* even attempting downloading/building > etc. You are confusing two stages here. First and most importantly, you are downloading and installing all the elements required for a basic toolset set which will build all the apps you want to build. Building Perl, is a completely sperate process which has been bundled to show that the build system is complete and actually does something. You do get a warning about LINK386.EXE not being on the path and that you could encounter problems. If you like I could output a stupid message like:- 'Press C to continue or any other key to abort. By selecting C I agree that I will not winge about missing elements in the Build System' But what would be the point? Are you seriously asking me to check every single application and know which tools it requires and ensure they are present before continuing? > Further, complete logging of the various steps is mandatory. You show me how, and I will gladly include it. Every application which is built is logged, but I don't know of any way to log the installation of the build system itself. Feel free to provide the missing feature.... > Hakan -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 28 ==========================** Date: Sun, 26 Jan 2003 20:28:55 +0000 From: John Poltorak Subject: Re: Starting from scratch On Sun, Jan 26, 2003 at 11:51:27AM -0600, Maynard wrote: > GETTEXT: > the log indicates: > Libraries have been installed in: > P:/usr/lib > > and tails with: > P:/usr/bin/install.exe msguniq.exe P:/usr/bin/msguniq.exe > P:/usr/bin/install.exe: msguniq.exe: No such file or directory > make[2]: *** [install-binPROGRAMS] Error 1 > make[2]: Leaving directory `P:/unixos2/workdir/gettext-0.11.5/src' > make[1]: *** [install-am] Error 2 > make[1]: Leaving directory `P:/unixos2/workdir/gettext-0.11.5/src' > make: *** [install-recursive] Error 1 > > It doesn't appear that any .exe files were installed, which may be OK. > There are many .exe files in \UnixOS2\workdir\gettext-0.11.5\src\.libs\ That obviously needs looking at, but it's good that the .exe's got built. Do they all normally get dumped in /usr/bin? > TEXINFO: > appears OK, .... > from the log: > WARNING: You must install texinfo.tex and txi-??.tex manually, > on the disk: > Directory: P:\usr\local\TMP\share\automake > texinfo.tex 208557 1-26-2003 10:58a A > --there are no txi-??.tex files in \usr I hadn't noticed that, but it says these files should be installed in the TeX tree, but since we don't have one yet, we can leave this until later, but I think Texinfo is built and working... > > AUTOMAKE 1.7.2 looks to have failed: > from the log: > make[1]: Entering directory `P:/unixos2/workdir/automake-1.7.2' > P:/bin/sh /unixos2/workdir/automake-1.7.2/lib/missing --run makeinfo -I . \ > -o automake.info `test -f 'automake.texi' || echo './'`automake.texi > ./version.texi:30: Unknown command `(#)PD'. > makeinfo: Removing output file `automake.info' due to errors; use --force to pre > make[1]: *** [automake.info] Error 1 > make[1]: Leaving directory `P:/unixos2/workdir/automake-1.7.2' > make: *** [install-recursive] Error 1 I have seen this error before but I thought it was due to an outdated makeinfo. Mine installs OK. Can you post dir \usr\local\bin\* ? -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 29 ==========================** Date: Sun, 26 Jan 2003 21:00:46 +0000 From: John Poltorak Subject: Re: Apps to try On Sun, Jan 26, 2003 at 01:19:21PM -0600, Maynard wrote: > > >call build bison > [P:\]bison --version > bison (GNU Bison) 1.875 Good. > >call build patch > [P:\]patch --version > GNU patch 2.5 Bad. Should be 2.54, don't know why it isn't. > >call build indent > [P:\]indent --version > GNU indent 2.2.9 Good. > >call build dialog > [P:\]dialog --version > Version: 0.9b-20020814 Good. > >call build add > [P:\]add --version > add: invalid option `--' > Usage: add [options] [scripts] Good. > >call build vile > ./configure[4775]: syntax error: `if' unmatched > make > make: *** No targets specified and no makefile found. Stop. Oops... You used the wrong autoconf. Copy \unixos2\scripts\pre-process as vile in the same directory. I forgot to update the RSYNC server. > >call build tin > --nope-- Bad. Could be the same thing. I need to check. > >call build openssl > -- I don't think so -- > Directory of P:\UnixOS2\workdir\openssl-0.9.7\out\*.* > 6,946,744 bytes in 28 files > -- but not distributed from workdir -- Good, but .... Just realised that \unixos2\scripts\build\build_openssl.cmd has not been updated. It should contain:- rm include/openssl/* call os2\os2-emx make -f os2-emx-dll.mak cp -p openssl.exe %uxrt%\usr\bin cp -p out_dll\*.dll %uxrt%\usr\lib cp -p out_dll\*.a %uxrt%\usr\lib cp -p -r outinc\openssl %uxrt%\usr\include If you do an RSYNC refresh from my system and run this again after deleting openssl from the workdir, it should install the files, at the least the ones I believe should be installed. I'm not sure about what all the .exe's are for... > >call build lynx > [P:\]lynx --version > Lynx Version 2.8.4rel.1 (17 Jul 2001) > Built on os2-emx Jan 26 2003 12:22:40 Good. -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 30 ==========================** Date: Sun, 26 Jan 2003 21:25:12 +0000 From: John Poltorak Subject: Re: Help Getting Perl to Run On Sun, Jan 26, 2003 at 10:09:46PM +0100, Stefan.Neis at t-online.de wrote: > > You do get a warning about LINK386.EXE not being on the path and that you > > could encounter problems. > > > > If you like I could output a stupid message like:- > > > > 'Press C to continue or any other key to abort. > > By selecting C I agree that I will not winge about missing elements > > in the Build System' > > At the degree of automation we reached, I'd prefer to actually have the > thing stop with a "You have not installed a mandatory element in the build > system, can't continue". OK, I guess I could put that in instead. The check was only put in as an afterthought, since I assumed everyone already had it. > Continuing silently makes it _much_ harder to dig > out the real problem from the log files - see my problem with DBProf which > presumably broke my whole attempts at building/installing Perl and required > two or three weeks to be noticed by myself ... :-( > > > > Further, complete logging of the various steps is mandatory. > > > > You show me how, and I will gladly include it. > > The perl.log file is quite nice already, IMHO. The individual logging of each build of an app is OK. Hakan is complaining about the lack of logging of the install of the build system itself. I agree that this is a shortcoming, but without access to TEE at that point in the process, I don't see any way to log it. > Regards, > Stefan -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 31 ==========================** Date: Sun, 26 Jan 2003 21:39:27 -0500 From: Ted Sikora Subject: Impressive! This is a multi-part message in MIME format. --------------010703030502050200050907 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Finally used this thing in ernest. Put together a new clean OS/2 install and tried to approach this as a Unix novice. First thing the servers sucked.. slow as hell. So I put a BS mirror at dumbdog.org From start to the beginning of the perl build was about 1 minute... cool! EMX runtimes are also a prerequisite for rsync. ux2_bootstrap.cmd changes: ------------------------------------------------------------------- set host=dumbdog.org echo open dumbdog.org >ux2_ftp echo user anonymous pwd "" >>ux2_ftp echo binary >>ux2_ftp echo get /pub/ux2bs/build/lib/rsync.exe >>ux2_ftp echo bye >>ux2_ftp I would use this instead. Finally it ended with: (perl.log attached) ------------------------------------------------------------------- WORKDIR=d:/unixos2/workdir OS2PATH=d:\usr\bin;d:\emx\bin;d:\usr\local\bin;d:\os2; _emx_sig=00001b65:00000000 Sun Jan 26 20:47:02 GMT 2003 elapsed time: 731 secs end [D:\unixos2\lib]end Pretty Impressive. Suggestions: Seperate perl into a /ports aka /ports/perl-5.8.0 directory like BSD ports and call the build with 'build perl'. The BS installs ok end it there. It will be easier to debug this thing keeping port builds and the env seperate like it should be. -- Ted Sikora tsikora at ntplx.net --------------010703030502050200050907 Content-Type: text/plain; name="perl.log" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="perl.log" Sun Jan 26 20:34:51 GMT 2003 DIR URL CFLAGS LDFLAGS CFGPARMS MAKEPARM SRC http://www.cpan.org/src/perl-5.8.0.tar.gz . URL http://www.cpan.org/src/perl-5.8.0.tar.gz CFLAGS LDFLAGS CFGPARMS . MAKEPARM SRC retrieving perl-5.8.0.tar.gz d:/unixos2/workdir d:/unixos2/workdir/perl-5.8.0 using perl specific Build script [D:\unixos2\workdir\perl-5.8.0]set os2_shell=d:\os2\cmd.exe [D:\unixos2\workdir\perl-5.8.0]sh Configure -des -D prefix=d:/usr/lib/perl (I see you are using the Korn shell. Some ksh's blow up on Configure, mainly on older exotic systems. If yours does, try the Bourne shell instead.) First let's make sure your kit is complete. Checking... Locating common programs... Checking compatibility between d:/usr/bin/echo.exe and builtin echo (if any)... Symbolic links are NOT supported. No symbolic links, so not testing for their testing... Good, your tr supports [:lower:] and [:upper:] to convert case. Using [:upper:] and [:lower:] to convert case. 3b1 dynix isc_2 opus super-ux aix dynixptx linux os2 svr4 altos486 epix lynxos os390 svr5 amigaos esix4 machten posix-bc ti1500 apollo fps machten_2 powerux titanos atheos freebsd mint qnx ultrix_4 aux_3 genix mips rhapsody umips beos gnu mpc sco unicos bsdos greenhills mpeix sco_2_3_0 unicosmk convexos hpux ncr_tower sco_2_3_1 unisysdynix cxux i386 netbsd sco_2_3_2 utekv cygwin irix_4 newsos4 sco_2_3_3 uts darwin irix_5 next_3 sco_2_3_4 uwin dcosx irix_6 next_3_0 solaris_2 vmesa dec_osf irix_6_0 next_4 stellar vos dgux irix_6_1 nonstopux sunos_4_0 dos_djgpp isc openbsd sunos_4_1 Which of these apply, if any? [os2] !!! Apparently there is no need to patch Configure. Operating system name? [os2] Operating system version? [2] Build Perl for SOCKS? [n] Use the PerlIO abstraction layer? [y] Build a threading Perl? [n] Build Perl for multiplicity? [n] Use which C compiler? [gcc] Checking for GNU cc in disguise and/or its version number... Now, how can we feed standard input to your C preprocessor... Directories to use for library searches? [d:/usr/lib d:/emx/lib d:/emx/lib/mt] What is the file extension used for shared libraries? [dll] Checking for optional libraries... What libraries to use? [-lsocket -lm -lbsd] What optimizer/debugger flag should be used? [-O2 -fomit-frame-pointer -malign-loops=2 -malign-jumps=2 -malign-functions=2 -s] Any additional cc flags? [-Zomf -Zmt -DDOSISH -DOS2=2 -DEMBED -I. -D_EMX_CRT_REV_=64] Let me guess what the preprocessor flags are... Any additional ld flags (NOT including libraries)? [-Zexe -Zomf -Zmt -Zcrtdll -Zstack 32000 -Zlinker /e:2] Checking your choice of C compiler and flags for coherency... Checking to see how big your integers are... Checking to see if you have long long... Checking to see how big your long longs are... Computing filename position in cpp output for #include directives... NOT found. Checking to see if you have int64_t... Checking which 64-bit integer type we could use... We could use 'long long' for 64-bit integers. Try to use 64-bit integers, if available? [n] Try to use maximal 64-bit support, if available? [n] Checking for GNU C Library... Shall I use d:/emx/bin/nm to extract C symbols from the libraries? [y] Where is your C library? [d:/emx/lib/mt/c_import.lib] Extracting names from the following files for later perusal: d:/emx/lib/bsd.lib d:/emx/lib/c_alias.lib d:/emx/lib/m.lib d:/emx/lib/mt/c_import.lib d:/emx/lib/socket.lib This may take a while..................d:/emx/bin/nm didn't seem to work right. Trying emxomfar instead... Ok. sqrtl() found. Checking to see how big your double precision numbers are... Checking to see if you have long double... Checking to see how big your long doubles are... Checking how to print long doubles... modfl() found. Your modfl() seems okay for large values. Try to use long doubles if available? [n] What is your architecture name [os2] Perlio selected. Installation prefix to use? (~name ok) [d:/usr/lib/perl] Directory d:/usr/lib/perl doesn't exist. Use that name anyway? [y] AFS does not seem to be running... What installation prefix should I use for installing files? (~name ok) [d:/usr/lib/perl] Directory d:/usr/lib/perl doesn't exist. Use that name anyway? [y] Getting the current patchlevel... Pathname where the private library files will reside? (~name ok) [d:/usr/lib/perl/lib/5.8.0] Where do you want to put the public architecture-dependent libraries? (~name ok) [d:/usr/lib/perl/lib/5.8.0/os2] I don't think setuid scripts are secure (no /dev/fd directory). Do you want to do setuid/setgid emulation? [n] found. found. Checking to see how well your C compiler groks the void type... Good. It appears to support void to the level perl5 wants. Checking to see how big your pointers are... Do you wish to attempt to use the malloc that comes with perl5? [y] Your system wants malloc to return 'void *', it would seem. Your system uses void free(), it would seem. Installation prefix to use for add-on modules and utilities? (~name ok) [d:/usr/lib/perl] Pathname for the site-specific library files? (~name ok) [d:/usr/lib/perl/lib/site_perl/5.8.0] Pathname for the site-specific architecture-dependent library files? (~name ok) [d:/usr/lib/perl/lib/site_perl/5.8.0/os2] Do you want to configure vendor-specific add-on directories? [n] Colon-separated list of additional directories for perl to search? [none] Checking out function prototypes... Pathname where the public executables will reside? (~name ok) [d:/usr/lib/perl/bin] Directory d:/usr/lib/perl/bin doesn't exist. Use that name anyway? [y] Install any extra modules (y or n)? [n] List of earlier versions to include in at INC? [none] Do you want to install perl as /usr/bin/perl? [y] NOT found. dlopen() NOT found. Do you wish to use dynamic loading? [y] Source file to use for dynamic loading [ext/DynaLoader/dl_dlopen.xs] Any special flags to pass to gcc -c to compile shared library modules? [-Zdll] What command should be used to create dynamic libraries? [gcc] Any special flags to pass to gcc to create a dynamically loaded library? [-Zdll -Zomf -Zmt -Zcrtdll -Zlinker /e:2] Any special flags to pass to gcc to use dynamic linking? [none] Build a shared libperl.dll (y/n) [y] What name do you want to give to the shared libperl? [libperl.lib] Could not find manual pages in source form. Where do the main Perl5 manual pages (source) go? (~name ok) [d:/usr/lib/perl/man/man1] What suffix should be used for the main Perl5 man pages? [1] You can have filenames longer than 14 characters. Where do the perl5 library man pages (source) go? (~name ok) [d:/usr/lib/perl/man/man3] What suffix should be used for the perl5 library man pages? [3] Figuring out host name... Your host name appears to be "standalone". Right? [y] What is your domain name? [.nonet] What is your e-mail address? [root at standalone.nonet] Perl administrator e-mail address [root at standalone.nonet] Do you want to install only the version-specific parts of perl? [n] What shall I put after the #! to start up perl ("none" to not use #!)? [d:/usr/lib/perl/bin/perl] Where do you keep publicly executable scripts? (~name ok) [d:/usr/lib/perl/bin] Directory d:/usr/lib/perl/bin doesn't exist. Use that name anyway? [y] Pathname where the add-on public executables should be installed? (~name ok) [d:/usr/lib/perl/bin] Directory d:/usr/lib/perl/bin doesn't exist. Use that name anyway? [y] off_t found. Checking to see how big your file offsets are... fpos_t found. Checking the size of fpos_t... Try to understand large files, if available? [y] qgcvt() NOT found. fwalk() NOT found. access() found. defines the *_OK access constants. accessx() NOT found. alarm() found. NOT found. found. found. Testing to see if we should include , or both. We'll include . Checking to see if your struct tm has tm_zone field... Checking to see if your struct tm has tm_gmtoff field... asctime_r() NOT found. atolf() NOT found. atoll() NOT found. Checking whether your compiler can handle __attribute__ ... bcmp() found. bcopy() found. found. getpgrp() found. You have to use getpgrp() instead of getpgrp(pid). setpgrp() NOT found. bzero() found. You have void (*signal())(). Checking whether your C compiler can cast large floats to int32. Checking whether your C compiler can cast negative float to unsigned. vprintf() found. Your vsprintf() returns (int). chown() NOT found. chroot() NOT found. chsize() found. class() NOT found. Hmm... Looks like you have Berkeley networking support. socketpair() NOT found. Checking the availability of certain socket constants... found. Checking to see if your system supports struct cmsghdr... Checking to see if your C compiler knows about "const"... crypt() NOT found. crypt() NOT found. NOT found. crypt_r() NOT found. ctermid_r() NOT found. ctime_r() NOT found. cuserid() found. found. found. DBL_DIG found. dbmclose() NOT found. difftime() found. found. :7: warning: #warning requires Your directory entries are struct dirent. :7: warning: #warning requires Good, your directory entry keeps length information in d_namlen. found. NOT found. dirfd() found. dlerror() NOT found. NOT found. *** WHOA THERE!!! *** The recommended value for $i_dlfcn on this machine was "define"! Keep the recommended value? [y] What is the extension of dynamically loaded modules [dll] Checking whether your dlsym() needs a leading underscore ... I can't compile and run the test program. I'm guessing that dlsym doesn't need a leading underscore. drand48_r() NOT found. dup2() found. eaccess() NOT found. endgrent() NOT found. found. endgrent_r() NOT found. endhostent() found. found. endhostent_r() NOT found. endnetent() found. endnetent_r() NOT found. endprotoent() found. endprotoent_r() NOT found. endpwent() found. found. endpwent_r() NOT found. endservent() found. endservent_r() NOT found. defines the O_* constants... and you have the 3 argument form of open(). Using instead of . found. We'll be including . found. We don't need to include if we include . Figuring out the flag used by open() for non-blocking I/O... Let's see what value errno gets from read() on a O_NONBLOCK file... fchdir() NOT found. fchmod() NOT found. fchown() NOT found. fcntl() found. Well, your system knows about the normal fd_set typedef... and you have the normal fd_set macros (just as I'd expect). fgetpos() found. finite() NOT found. finitel() NOT found. flock() found. fork() found. fp_class() NOT found. pathconf() found. fpathconf() found. fpclass() NOT found. fpclassify() NOT found. fpclassl() NOT found. Checking to see if you have fpos64_t... frexpl() found. found. NOT found. Checking to see if your system supports struct fs_data... fseeko() NOT found. fsetpos() found. fstatfs() NOT found. statvfs() NOT found. fstatvfs() NOT found. fsync() found. ftello() NOT found. getcwd() found. getespwnam() NOT found. getfsstat() NOT found. getgrent() NOT found. getgrent_r() NOT found. getgrgid_r() NOT found. getgrnam_r() NOT found. gethostbyaddr() found. gethostbyname() found. gethostent() found. gethostname() found. uname() found. Shall I ignore gethostname() from now on? [n] gethostbyaddr_r() NOT found. gethostbyname_r() NOT found. gethostent_r() NOT found. getitimer() NOT found. getlogin() found. getlogin_r() NOT found. getmnt() NOT found. getmntent() NOT found. getnetbyaddr() found. getnetbyname() found. getnetent() found. getnetbyaddr_r() NOT found. getnetbyname_r() NOT found. getnetent_r() NOT found. getpagesize() found. getprotobyname() found. getprotobynumber() found. getprotoent() found. getpgid() NOT found. getpgrp2() NOT found. getppid() found. getpriority() NOT found. *** WHOA THERE!!! *** The recommended value for $d_getprior on this machine was "define"! Keep the recommended value? [y] getprotobyname_r() NOT found. getprotobynumber_r() NOT found. getprotoent_r() NOT found. getprpwnam() NOT found. getpwent() found. getpwent_r() NOT found. getpwnam_r() NOT found. getpwuid_r() NOT found. getservbyname() found. getservbyport() found. getservent() found. getservbyname_r() NOT found. getservbyport_r() NOT found. getservent_r() NOT found. getspnam() NOT found. NOT found. getspnam_r() NOT found. gettimeofday() found. gmtime_r() NOT found. hasmntopt() NOT found. found. found. htonl() NOT found. But it seems to be defined as a macro. strchr() found. inet_aton() NOT found. isascii() found. isfinite() NOT found. isinf() NOT found. isnan() NOT found. isnanl() NOT found. killpg() NOT found. lchown() NOT found. LDBL_DIG found. link() NOT found. localtime_r() NOT found. localeconv() found. lockf() NOT found. lstat() NOT found. madvise() NOT found. mblen() found. mbstowcs() found. mbtowc() found. memchr() found. memcmp() found. memcpy() found. memmove() found. memset() found. mkdir() found. mkdtemp() NOT found. mkfifo() NOT found. mkstemp() found. mkstemps() NOT found. mktime() found. NOT found. mmap() NOT found. mprotect() NOT found. msgctl() NOT found. msgget() NOT found. msgsnd() NOT found. msgrcv() NOT found. You don't have the full msg*(2) library. Checking to see if your system supports struct msghdr... msync() NOT found. munmap() NOT found. nice() NOT found. NOT found. nl_langinfo() NOT found. Checking to see how big your characters are (hey, you never know)... What is the size of a character (in bytes)? [1] Checking to see if your C compiler knows about "volatile"... Choosing the C types to be used for Perl's internal types... Checking how many bits of your UVs your NVs can preserve... Checking to see if you have off64_t... pause() found. pipe() found. poll() NOT found. readlink() NOT found. random_r() NOT found. readdir() found. seekdir() found. telldir() found. rewinddir() found. readdir64_r() NOT found. readdir_r() NOT found. readv() found. recvmsg() NOT found. rename() found. rmdir() found. found. Checking if your memcmp() can compare relative magnitude... select() found. semctl() NOT found. semget() NOT found. semop() NOT found. You don't have the full sem*(2) library. You do not have union semun in . sendmsg() NOT found. setegid() NOT found. seteuid() NOT found. setgrent() NOT found. setgrent_r() NOT found. sethostent() found. sethostent_r() NOT found. setitimer() NOT found. setlinebuf() NOT found. setlocale() found. found. setlocale_r() NOT found. setnetent() found. setnetent_r() NOT found. setprotoent() found. setpgid() found. setpgrp2() NOT found. setpriority() NOT found. *** WHOA THERE!!! *** The recommended value for $d_setprior on this machine was "define"! Keep the recommended value? [y] setproctitle() NOT found. setprotoent_r() NOT found. setpwent() found. setpwent_r() NOT found. setregid() NOT found. setresgid() NOT found. setreuid() NOT found. setresuid() NOT found. setrgid() NOT found. setruid() NOT found. setservent() found. setservent_r() NOT found. setsid() NOT found. setvbuf() found. NOT found. shmctl() NOT found. shmget() NOT found. shmat() NOT found. shmdt() NOT found. You don't have the full shm*(2) library. sigaction() found. sigprocmask() found. POSIX sigsetjmp found. sockatmark() NOT found. socks5_init() NOT found. srand48_r() NOT found. srandom_r() NOT found. found. Checking to see if your struct stat has st_blocks field... NOT found. found. Checking to see if your system supports struct statfs... Checking to see if your struct statfs has f_flags field... Checking how std your stdio is... Checking to see what happens if we set the stdio ptr... Increasing ptr in your stdio leaves cnt unchanged. Good. Checking how to access stdio streams by file descriptor number... I can't figure out how to access stdio streams by file descriptor number. strcoll() found. Checking to see if your C compiler can copy structs... strerror() found. strerror_r() NOT found. strftime() found. strtod() found. strtol() found. strtold() found. strtoll() NOT found. *** WHOA THERE!!! *** The recommended value for $d_strtoll on this machine was "define"! Keep the recommended value? [y] strtoq() NOT found. strtoul() found. strtoull() NOT found. *** WHOA THERE!!! *** The recommended value for $d_strtoull on this machine was "define"! Keep the recommended value? [y] strtouq() NOT found. strxfrm() found. symlink() NOT found. syscall() NOT found. sysconf() found. system() found. tcgetpgrp() found. tcsetpgrp() found. time() found. time_t found. found. times() found. clock_t found. tmpnam_r() NOT found. truncate() found. ttyname_r() NOT found. tzname[] found. (Testing for character data alignment may crash the test. That's okay.) You can access character data pretty unalignedly. ualarm() NOT found. umask() found. unordered() NOT found. usleep() NOT found. ustat() NOT found. vfork() NOT found. closedir() found. Checking whether closedir() returns a status... wait4() NOT found. waitpid() found. wcstombs() found. wctomb() found. writev() found. Checking alignment constraints... Doubles must be aligned on a how-many-byte boundary? [4] Checking to see how your cpp does stuff like catenate tokens... Oh! Smells like ANSI's been here. found. Checking Berkeley DB version ... Looks OK. Checking return type needed for hash for Berkeley DB ... Checking return type needed for prefix for Berkeley DB ... Looking for a random number function... OK, found random(). Use which function to generate random numbers? [random] How many bits does your random() function produce? [31] Determining whether or not we are on an EBCDIC system... Nope, no EBCDIC, probably ASCII or some ISO Latin. Or UTF-8. Checking how to flush all pending stdio output... Checking the size of gid_t... Checking the sign of gid_t... Checking how to print 64-bit integers... Checking the format strings to be used for Perl's internal types... Checking the format string to be used for gids... getgroups() found. setgroups() NOT found. What type pointer is the second argument to getgroups() and setgroups()? [gid_t] Checking if your d:/usr/bin/make program sets $(MAKE)... mode_t found. found. found. We'll include to get va_dcl definition. It seems that you don't need va_copy(). size_t found. What pager is used on your system? [cmd /c more] pid_t found. Checking how to generate random libraries on your machine... Your select() operates on 256 bits at a time. Generating a list of signal names and numbers... Checking the size of size_t... Checking to see if you have socklen_t... NOT found. I'll be using ssize_t for functions returning a byte count. Your stdio uses signed chars. Checking the size of uid_t... Checking the sign of uid_t... Checking the format string to be used for uids... Which compiler compiler (yacc) shall I use? [yacc] NOT found. NOT found. NOT found. NOT found. found. NOT found. NOT found. NOT found. found. NOT found. NOT found. Guessing which symbols your C compiler and preprocessor define... tcsetattr() found. You have POSIX termios.h... good! found. NOT found. NOT found. NOT found. found. No socket ioctls found in . NOT found. NOT found. found. NOT found. NOT found. found. found. found. NOT found. found. NOT found. NOT found. Looking for extensions... What extensions do you wish to load dynamically? [B ByteLoader Cwd DB_File Data/Dumper Devel/DProf Devel/PPPort Devel/Peek Digest/MD5 Encode Fcntl File/Glob Filter/Util/Call IO List/Util MIME/Base64 OS2/ExtAttr OS2/PrfDB OS2/Process OS2/REXX Opcode POSIX PerlIO/encoding PerlIO/scalar PerlIO/via SDBM_File Socket Storable Sys/Hostname Sys/Syslog Time/HiRes Unicode/Normalize XS/APItest XS/Typemap attrs re threads threads/shared] What extensions do you wish to load statically? [none] Stripping down executable paths... Creating config.sh... Doing variable substitutions on .SH files... Extracting cflags (with variable substitutions) Extracting config.h (with variable substitutions) Extracting makeaperl (with variable substitutions) Extracting makedepend (with variable substitutions) Extracting makedir (with variable substitutions) Extracting Makefile (with variable substitutions) Configure: os2/Makefile.SHs[14]: too many files open in shell Configure: ./Makefile.SH[24]: too many files open in shell Configure: UU/myread[16]: too many files open in shell [D:\unixos2\workdir\perl-5.8.0]make makefile:737: warning: overriding commands for target `TAGS' makefile:729: warning: ignoring old commands for target `TAGS' make depend MAKEDEPEND= make[1]: Entering directory `/unixos2/workdir/perl-5.8.0' makefile:737: warning: overriding commands for target `TAGS' makefile:729: warning: ignoring old commands for target `TAGS' sh ./makedepend MAKE=make make[2]: Entering directory `/unixos2/workdir/perl-5.8.0' GNUmakefile:737: warning: overriding commands for target `TAGS' GNUmakefile:729: warning: ignoring old commands for target `TAGS' sh writemain lib/auto/DynaLoader/DynaLoader.lib > writemain.tmp sh mv-if-diff writemain.tmp perlmain.c echo malloc.c av.c scope.c op.c doop.c doio.c dump.c hv.c mg.c reentr.c perl.c perly.c pp.c pp_hot.c pp_ctl.c pp_sys.c regcomp.c regexec.c utf8.c gv.c sv.c taint.c toke.c util.c deb.c run.c universal.c xsutils.c globals.c perlio.c perlapi.c numeric.c locale.c pp_pack.c pp_sort.c miniperlmain.c perlmain.c | tr ' ' '\n\r' >.clist make[2]: Leaving directory `/unixos2/workdir/perl-5.8.0' Finding dependencies for malloc.obj. Finding dependencies for av.obj. Finding dependencies for scope.obj. Finding dependencies for op.obj. Finding dependencies for doop.obj. Finding dependencies for doio.obj. Finding dependencies for dump.obj. Finding dependencies for hv.obj. Finding dependencies for mg.obj. Finding dependencies for reentr.obj. Finding dependencies for perl.obj. Finding dependencies for perly.obj. Finding dependencies for pp.obj. Finding dependencies for pp_hot.obj. Finding dependencies for pp_ctl.obj. Finding dependencies for pp_sys.obj. Finding dependencies for regcomp.obj. Finding dependencies for regexec.obj. Finding dependencies for utf8.obj. Finding dependencies for gv.obj. Finding dependencies for sv.obj. Finding dependencies for taint.obj. Finding dependencies for toke.obj. Finding dependencies for util.obj. Finding dependencies for deb.obj. Finding dependencies for run.obj. Finding dependencies for universal.obj. Finding dependencies for xsutils.obj. Finding dependencies for globals.obj. Finding dependencies for perlio.obj. Finding dependencies for perlapi.obj. Finding dependencies for numeric.obj. Finding dependencies for locale.obj. Finding dependencies for pp_pack.obj. Finding dependencies for pp_sort.obj. Finding dependencies for miniperlmain.obj. Finding dependencies for perlmain.obj. make[2]: Entering directory `/unixos2/workdir/perl-5.8.0' GNUmakefile:737: warning: overriding commands for target `TAGS' GNUmakefile:729: warning: ignoring old commands for target `TAGS' echo Makefile.SH cflags.SH config_h.SH makeaperl.SH makedepend.SH makedir.SH myconfig.SH writemain.SH pod/Makefile.SH | tr ' ' '\n\r' >.shlist make[2]: Leaving directory `/unixos2/workdir/perl-5.8.0' Updating GNUmakefile... test -s perlmain.c && touch perlmain.c cd x2p; make depend make[2]: Entering directory `/unixos2/workdir/perl-5.8.0/x2p' sh ../makedepend MAKE=make make[3]: Entering directory `/unixos2/workdir/perl-5.8.0/x2p' echo hash.c str.c util.c walk.c | tr ' ' '\n\r' >.clist make[3]: Leaving directory `/unixos2/workdir/perl-5.8.0/x2p' Finding dependencies for hash.obj. Finding dependencies for str.obj. Finding dependencies for util.obj. Finding dependencies for walk.obj. make[3]: Entering directory `/unixos2/workdir/perl-5.8.0/x2p' echo Makefile.SH cflags.SH | tr ' ' '\n\r' >.shlist make[3]: Leaving directory `/unixos2/workdir/perl-5.8.0/x2p' Updating GNUmakefile... make[2]: Leaving directory `/unixos2/workdir/perl-5.8.0/x2p' make[1]: Leaving directory `/unixos2/workdir/perl-5.8.0' make: *** No rule to make target `miniperl.exe', needed by `all'. Stop. [D:\unixos2\workdir\perl-5.8.0]make test GNUmakefile:737: warning: overriding commands for target `TAGS' GNUmakefile:729: warning: ignoring old commands for target `TAGS' make: *** No rule to make target `miniperl.exe', needed by `preplibrary'. Stop. [D:\unixos2\workdir\perl-5.8.0]make install GNUmakefile:737: warning: overriding commands for target `TAGS' GNUmakefile:729: warning: ignoring old commands for target `TAGS' make install.perl install.man STRIPFLAGS= make[1]: Entering directory `/unixos2/workdir/perl-5.8.0' GNUmakefile:737: warning: overriding commands for target `TAGS' GNUmakefile:729: warning: ignoring old commands for target `TAGS' make[1]: *** No rule to make target `miniperl.exe', needed by `all'. Stop. make[1]: Leaving directory `/unixos2/workdir/perl-5.8.0' make: *** [install] Error 2 [D:\unixos2\workdir\perl-5.8.0]cd t [D:\unixos2\workdir\perl-5.8.0\t]perl harness SYS1041: The name perl is not recognized as an internal or external command, operable program or batch file. [D:\unixos2\workdir\perl-5.8.0\t]cp perl.exe d:/usr/bin cp: perl.exe: No such file or directory [D:\unixos2\workdir\perl-5.8.0\t]cp perl*.dll d:/usr/lib cp: perl*.dll: No such file or directory UXRT=d: TMP=d:\tmp PATH=d:\usr\bin;d:\emx\bin;d:\usr\local\bin;d:\os2; BLD_HOME=d:/unixos2 CFLAGS= ETC=d:\etc CONFIG_SITE= CPLUS_INCLUDE_PATH=d:/usr/include/cpp;d:/usr/included:/emx/include/cpp;d:/emx/include C_INCLUDE_PATH=d:/usr/include;d:/emx/include LIBRARY_PATH=d:/usr/lib;d:/emx/lib HOME=d:/home/root REPOSITORY=d:/unixos2/archives/source BUILDLOGS=d:/unixos2/logs LDFLAGS= BLDRT=d: OS2_SHELL=d:\os2\cmd.exe TERM=ansi-color-3 OSRT=d: WORKDIR=d:/unixos2/workdir OS2PATH=d:\usr\bin;d:\emx\bin;d:\usr\local\bin;d:\os2; _emx_sig=00001b65:00000000 Sun Jan 26 20:47:02 GMT 2003 elapsed time: 731 secs end --------------010703030502050200050907-- _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 32 ==========================** Date: Sun, 26 Jan 2003 21:52:52 +0000 From: John Poltorak Subject: MAN pages AFAICT, handling MAN pages requires the installation of MAN, GROFF and LESS, so I'd like to get these built... I've built all of them at some point, but have this aversion to MAN since it seemed so awkward the last time I tried, and I was never sure if it worked right. I'd like to know how anyone else builds in manually. The original is available here:- ftp://ftp.win.tue.nl/pub/linux-local/utils/man/man-1.5g.tar.gz and the OS/2 patch is here:- http://homepage1.nifty.com/jsawa/linux/man15g.zip It is an old version, but the most recent one I could find which is available for OS/2. It isn't a GNU app and doesn't look as though it will build easily on OS/2... -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 33 ==========================** Date: Sun, 26 Jan 2003 21:55:43 -0500 From: Ted Sikora Subject: Re: Impressive! Ted Sikora wrote: > Finally used this thing in ernest. Put together a new clean OS/2 install > and tried to approach this as a Unix novice. First thing the servers > sucked.. slow as hell. So I put a BS mirror at dumbdog.org From start > to the beginning of the perl build was about 1 minute... cool! EMX > runtimes are also a prerequisite for rsync. > > ux2_bootstrap.cmd changes: > ------------------------------------------------------------------- > set host=dumbdog.org > > echo open dumbdog.org >ux2_ftp > > echo user anonymous pwd "" >>ux2_ftp > > echo binary >>ux2_ftp > > echo get /pub/ux2bs/build/lib/rsync.exe >>ux2_ftp > > echo bye >>ux2_ftp > > I would use this instead. > > > Finally it ended with: (perl.log attached) > ------------------------------------------------------------------- > WORKDIR=d:/unixos2/workdir > OS2PATH=d:\usr\bin;d:\emx\bin;d:\usr\local\bin;d:\os2; > _emx_sig=00001b65:00000000 > > Sun Jan 26 20:47:02 GMT 2003 > elapsed time: 731 secs > end > > [D:\unixos2\lib]end > > Pretty Impressive. Suggestions: > > Seperate perl into a /ports aka /ports/perl-5.8.0 directory like BSD > ports and call the build with 'build perl'. The BS installs ok end it > there. It will be easier to debug this thing keeping port builds and the > env seperate like it should be. > > BTW I made a UX2core list a few days ago. I know "another list"!! Considering the scope of the ux2 project it will make it easier to manage. The ux2core is really an offshoot of posix/2 and should deal only with the Build System env and nothing more. UX2BS is the entire system with ports. In the future port maintainers can branch off ie; devel tools, Gnome, XFree86, etc. http://powerusersbbs.net/mailman/listinfo/ux2core -- Ted Sikora tsikora at ntplx.net _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 34 ==========================** Date: Sun, 26 Jan 2003 22:01:23 -0600 (CST) From: "Maynard" Subject: Re: Impressive! Ted, >Finally it ended with: (perl.log attached) Your perl build looks incomplete. You should end up with: Total for: P:\usr\lib\perl\*.* 30,345,029 bytes in 1,758 files and 165 dirs and P:\usr\bin\perl.exe P:\usr\lib\perlB12E.dll and near the end of the log file, something like: Failed 5/726 test scripts, 99.31% okay. 9/68650 subtests failed, 99.99% okay. Failed Test Stat Wstat Total Fail Failed List of Failed ------------------------------------------------------------------------------ ../lib/ExtUtils/t/basic.t 1 256 17 1 5.88% 14 ../lib/Net/t/hostname.t 2 1 50.00% 1 lib/os2_process.t 2 512 227 2 0.88% 46 57 lib/os2_process_kid.t 227 2 0.88% 46 57 lib/rx_cmprt.t 255 65280 18 3 16.67% 16-18 64 tests and 557 subtests skipped. _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 35 ==========================** Date: Sun, 26 Jan 2003 22:09:46 +0100 From: Stefan.Neis at t-online.de Subject: Re: Help Getting Perl to Run Hi, > LINK386.EXE is part of OS/2. It is something that always gets installed > whenever I install OS/2. I was under the impression that most people had > it installed, but it seems that this is not the case. IIRC, in the standard OS/2 install process (don't know about eCS), there's one dialog, where you can configure a certain set of applications to be installed, like "backup", "restore" and a couple of others. One of them is "link386". I'd expect that whoever intends to ever compile something on his machine did select to install "link386", but by default it is unselected ... > You do get a warning about LINK386.EXE not being on the path and that you > could encounter problems. > > If you like I could output a stupid message like:- > > 'Press C to continue or any other key to abort. > By selecting C I agree that I will not winge about missing elements > in the Build System' At the degree of automation we reached, I'd prefer to actually have the thing stop with a "You have not installed a mandatory element in the build system, can't continue". Continuing silently makes it _much_ harder to dig out the real problem from the log files - see my problem with DBProf which presumably broke my whole attempts at building/installing Perl and required two or three weeks to be noticed by myself ... :-( > > Further, complete logging of the various steps is mandatory. > > You show me how, and I will gladly include it. The perl.log file is quite nice already, IMHO. Regards, Stefan _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 36 ==========================** Date: Sun, 26 Jan 2003 22:10:42 -0500 From: Ted Sikora Subject: Re: Impressive! Ted Sikora wrote: > Ted Sikora wrote: > >> >> Pretty Impressive. Suggestions: >> >> Seperate perl into a /ports aka /ports/perl-5.8.0 directory like BSD >> ports and call the build with 'build perl'. The BS installs ok end it >> there. It will be easier to debug this thing keeping port builds and >> the env seperate like it should be. >> >> 'build perl pkg' could also be added eventually. So the distribution maintainer just has to run 'build pkg' from the BS. Very BSD like and still be Slack like on the distribution end. Like the best of both worlds. For ports not included in the distro the user just needs to go into /ports pick the port wanted and run 'build '. We can add a script much like ux2bs/cvs with rsync to mirror the /ports dir. To keep it current for now. The best part of all this it will be the 'Standard' for OS/2. If it's not part of ux2 ports it's not a community supported port. -- Ted Sikora tsikora at ntplx.net _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 37 ==========================** Date: Sun, 26 Jan 2003 22:13:16 +0000 From: John Poltorak Subject: Re: Apps to try On Sun, Jan 26, 2003 at 03:37:25PM -0600, Maynard wrote: > On Sun, 26 Jan 2003 21:00:46 +0000, John Poltorak wrote: > > >> GNU patch 2.5 > > > >Bad. Should be 2.54, don't know why it isn't. > > I've no doubt that the version is in fact 2.54 and that it just isn't > reporting that fact. Actually, it looks as though it didn't build automatically and I had to cheat... I actually edited the Makefile and ran Make. Normally when Makefile.in includes:- EXEEXT = at EXEEXT at this gets translated in the Makefile as:- EXEXT = .exe I don't fully understand how this mechanism works - I wish Andreas Buening would explain it as he seems to be one of the few people who do understand it. Anyway it wasn't set in the Makefile for whatever reason, but adding it manually and re-running Make does create patch.exe. > >Copy \unixos2\scripts\pre-process as > >vile in the same directory. Did I really write that? :-)... I was meant to have add at the end of that path... > ?^?^?^?^?^?^?^?^?^?^?^ > need more complete specification of sourcefile; or update of your rsync > server Maybe an update would be easiest... > > > [p:\]type ux2_update.cmd > rsync -av 213.152.37.92::build P:\UnixOS2 Good idea, but it should be %bldrt% of course :-). Isn't RSYNC a wonderful program? > -- Maynard -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 38 ==========================** Date: Sun, 26 Jan 2003 22:34:15 +0100 From: Stefan.Neis at t-online.de Subject: Re: Apps to try Hi, > If you do an RSYNC refresh from my system and run this again after > deleting openssl from the workdir, it should install the files, at the > least the ones I believe should be installed. I'm not sure about what all > the .exe's are for... Apparently just used for testing. They are build but not installed on Unix as well (however, on Unix systems, there is a second executable which gets installed, that isn't even compiled for OS/2. Didn't check what this is about, though). Regards, Stefam _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs