Date: Mon, 27 Jan 2003 02:28:45 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [Ux2bs_Archive] No. 59 ************************************************** Sunday 26 January 2003 Number 59 ************************************************** Subjects for today 1 Re: Impressive! : Maynard" 2 Re: Help Getting Perl to Run : Maynard" 3 Perl harness : Maynard" 4 Re: Help Getting Perl to Run : Hakan" 5 Re: Perl harness : Maynard" 6 Re: Impressive! : Maynard" 7 Re: Building perl-5.8.0 : John Poltorak 8 Re: Building FILE : Maynard" 9 Re: Impressive! : John Poltorak 10 Re: Impressive! : Ted Sikora 11 Re: Building perl-5.8.0 : Stefan.Neis at t-online.de 12 Re: Building FILE : Maynard" 13 Re: Perl : Maynard" 14 Logs of successful builds : Maynard" 15 tar failing in ux2bs : Ted Sikora 16 Re: Help Getting Perl to Run : John Poltorak 17 GROFF builds! : John Poltorak 18 Re: Perl harness : John Poltorak 19 Perl : Ted Sikora 20 Re: Logs of successful builds : Maynard" 21 Building FILE : John Poltorak 22 Building SLANG : John Poltorak 23 Re: Impressive! : John Poltorak 24 Re: Building FILE : John Poltorak 25 Re: Help Getting Perl to Run : John Poltorak 26 Re: Perl : John Poltorak 27 6/726 test failed 99.17% okay subsets 99.98% okay : Ted Sikora 28 Perl env vaiables : Ted Sikora 29 Re: Perl env vaiables : Hakan" 30 Re: Logs of successful builds : John Poltorak **= Email 1 ==========================** Date: Mon, 27 Jan 2003 10:05:58 -0600 (CST) From: "Maynard" Subject: Re: Impressive! On Mon, 27 Jan 2003 12:58:42 +0000, John Poltorak wrote: >It didn't really get started and have no idea what happened. >> EMX runtimes are also a prerequisite for rsync. I issued my message to Ted last night with only one eye left open. After I closed it I realized that his failed perl build may be due to incomplete EMX installation due to prior EMX in the way. What I had to do was install EMX for my other-than-ux2 uses; and then dedicate a separate volume or two for %bldrt% and %uxrt% ux2_inst.cmd and emx_inst.cmd probably bust if there is a locked file in a pre-existing \emx tree. -- Maynard _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 2 ==========================** Date: Mon, 27 Jan 2003 10:11:25 -0600 (CST) From: "Maynard" Subject: Re: Help Getting Perl to Run Well Done, Harkan! >Do these failures present a problem? Not at all. see http://warped.mentabolism.org/UnixOS2/perl.html >BTW, on my Cyrix 586-100 and 64 >Mb of memory, the entire build process for perl took 44107 seconds, >i.e., a little over 12.hours. XP1700+ w/1Gb sdram : elapsed time: 1613 secs = 27 minutes [for reference] -- Maynard _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 3 ==========================** Date: Mon, 27 Jan 2003 10:14:11 -0600 (CST) From: "Maynard" Subject: Perl harness running perl harness from the workdir adds a new set of errors which do not fail during the build. ../lib/ExtUtils/t/Constant.t 255 65280 51 49 96.08% 3-51 ../lib/ExtUtils/t/Embed.t 9 9 100.00% 1-9 -- Maynard _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 4 ==========================** Date: Mon, 27 Jan 2003 10:39:34 -0500 (EST) From: "Hakan" Subject: Re: Help Getting Perl to Run Perl finished building with the following: Failed 4/726 test scripts, 99.45% okay. 370/68650 subtests failed, 99.46% okay. Failed Test Stat Wstat Total Fail Failed List of Failed ------------------------------------------------------------------------ ------- ../lib/ExtUtils/t/basic.t 1 256 17 1 5.88% 14 lib/os2_process.t 255 65280 227 184 81.06% 44-227 lib/os2_process_kid.t 227 184 81.06% 44-227 op/stat.t 73 1 1.37% 44 64 tests and 545 subtests skipped. Do these failures present a problem? BTW, on my Cyrix 586-100 and 64 Mb of memory, the entire build process for perl took 44107 seconds, i.e., a little over 12.hours.. Thanks for the help. 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 5 ==========================** Date: Mon, 27 Jan 2003 12:29:54 -0600 (CST) From: "Maynard" Subject: Re: Perl harness John, >During the build they are run from the 't' directory under perl's workdir. >Maybe the different path at that point has some effect... I got these same results running from t/, from t/./; from OS/2 or 'sh' -- Maynard _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 6 ==========================** Date: Mon, 27 Jan 2003 12:34:13 -0600 (CST) From: "Maynard" Subject: Re: Impressive! Ted, >That's exactly what happened 6 zips failed to install because of it. I >installed it for the runtime for rsync. I'm going to broadcast my ignorance here and maybe learn something..... Can we rebuild 'rsync' as 'static' so that EMX is not required? -- Maynard _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 7 ==========================** Date: Mon, 27 Jan 2003 12:37:30 +0000 From: John Poltorak Subject: Re: Building perl-5.8.0 On Sun, Jan 26, 2003 at 06:55:58PM +0100, Stefan.Neis at t-online.de wrote: > 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: > > 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 .... Sure - that makes a lot of sense, and something I have thought of, only I have no idea about whether Configure provides any meaningful return codes. If you know of any please let me know. > 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 was wondering was whether building Perl with Posix/2 headers might just be too big a job at this point. Perl is a big, demanding app... What if... Perl was built using EMX headers and all the other apps used Posix/2 ? I know it may sound crazy, but would be relatively easy to try because a default INCLUDE/LIB search could be set up, but simply switched for the purposes of building Perl. It would mean that Posix/2 could be tested with a wide variety of apps rather than getting bogged down and failing at the first hurdle with Perl. Any experience gained in the building of those apps could then be used to update Posix/2 and may make it simpler to build Perl subsequently. ...just a thought. > > Regards, > Stefan -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 8 ==========================** Date: Mon, 27 Jan 2003 12:42:34 -0600 (CST) From: "Maynard" Subject: Re: Building FILE John, Again, broadcasting my ignorance.... >I'm attaching stdint.h in case anyone wants to give it a try... isn't an associated file also required with *.h header files? aren't the #includes also required?: #include #include #include My build log: creating config.h make cd . && /unixos2/workdir/file-3.39/missing aclocal SYS1041: The name \unixos2\workdir\file-3.39\missing is not recognized as an internal or external command, operable program or batch file. make: *** [aclocal.m4] Error 255 cd . && /unixos2/workdir/file-3.39/missing aclocal SYS1041: The name \unixos2\workdir\file-3.39\missing is not recognized as an internal or external command, operable program or batch file. make: *** [aclocal.m4] Error 255 ??clues?? [p:\unixos2\workdir\file-3.39]grep missing * |grep aclocal config.status:s% at ACLOCAL at %/unixos2/workdir/file-3.39/missing aclocal%g configure: ACLOCAL="$missing_dir/missing aclocal" Makefile:ACLOCAL = /unixos2/workdir/file-3.39/missing aclocal _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 9 ==========================** Date: Mon, 27 Jan 2003 12:58:42 +0000 From: John Poltorak Subject: Re: Impressive! Ted, You impress far too easily! :-)... On Sun, Jan 26, 2003 at 09:39:27PM -0500, 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! I saw this and thought ***WOW***, Ted must be running OS/2 on some CRAY Super Computer, but then looking throught the log, came across:- 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. It didn't really get started and have no idea what happened. For it to work successfully, you may need to give it an hour or two depending on what sort of CPU you're using. And please don't send the full 500kB log to the list... > EMX runtimes are also a prerequisite for rsync. Yes, I think I realised that and wanted to create a standalone version but couldn't remember how... > 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. The Perl build is used to test that the toolset is functioning correctly. It get called simply beause perl is listed in BUILD.LST > It will be easier to debug this thing keeping port builds and the > env seperate like it should be. In effect, they already are seperate, but it doesn't appear that way. Perl can be built by itself at any time by running 'build perl' > -- > Ted Sikora > tsikora at ntplx.net -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 10 ==========================** Date: Mon, 27 Jan 2003 13:45:38 -0500 From: Ted Sikora Subject: Re: Impressive! Maynard wrote: > On Mon, 27 Jan 2003 12:58:42 +0000, John Poltorak wrote: > > >>It didn't really get started and have no idea what happened. > > >>>EMX runtimes are also a prerequisite for rsync. >> > > I issued my message to Ted last night with only one eye left open. > After I closed it I realized that his failed perl build may be due to > incomplete EMX installation due to prior EMX in the way. That's exactly what happened 6 zips failed to install because of it. I installed it for the runtime for rsync. > > What I had to do was install EMX for my other-than-ux2 uses; and then > dedicate a separate volume or two for %bldrt% and %uxrt% > > ux2_inst.cmd and emx_inst.cmd probably bust if there is a locked file > in a pre-existing \emx tree. > -- Ted Sikora tsikora at ntplx.net _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 11 ==========================** Date: Mon, 27 Jan 2003 14:38:13 +0100 (CET) From: Stefan.Neis at t-online.de Subject: Re: Building perl-5.8.0 John Poltorak schrieb: > > I was wondering was whether building Perl with Posix/2 > headers might just > be too big a job at this point. Perl is a big, demanding > app... That's not the real problem (or at least not the most important part of it). Perl explicitly provides a lot of features to handle "DOSISH" environments and treats OS/2 as such, whereas Posix/2 aims at easier _Unix_ portability, i.e. whenever there is a choice between a DOS-like and a UNIX-like implementation ("setmode"), Posix/2 is choosing the "wrong" one from Perl's point of view... Anyway, I really would be happy, if I managed to build Perl with EMX headers for now, but even that is failing over here... Regards, Stefan _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 12 ==========================** Date: Mon, 27 Jan 2003 15:34:23 -0600 (CST) From: "Maynard" Subject: Re: Building FILE John, >ISTR you didn't get Automake installed. It appears that I'm still lacking, in sequential order: gettext, texinfo, and automake ref. recent subject thread "Starting from scratch" Thanks, -- Maynard _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 13 ==========================** Date: Mon, 27 Jan 2003 15:52:32 -0600 (CST) From: "Maynard" Subject: Re: Perl Ted, It'd be nice to see just a few of the last good lines before the bad, in order to attempt sync with successful log (which I'll post online soon) >Here's what mine fails with: > >In file included from D:\emx\include\fcntl.h:5, > from os2.c:23: >D:\emx\include\sys/fcntl.h:75: parse error before `off_t' here's what I see from my log as only references to fcntl.h: We'll be including . found. We don't need to include if we include . which was in: Directory: P:\emx\include\sys file.h 126 3-02-1993 5:44p A So it still looks like your emx installation is incomplete. I've now put all my successful logs, including bootstrap.log to http://warped.mentabolism.org/UnixOS2/logs/ the bootstrap was generated by "ux2_bootstrap.cmd 2>&1 >>\bootstrap.log" running blind and remembering to key 'enter' once at the beginning. -- Maynard _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 14 ==========================** Date: Mon, 27 Jan 2003 15:54:14 -0600 (CST) From: "Maynard" Subject: Logs of successful builds I've now put all my successful logs, including bootstrap.log to http://warped.mentabolism.org/UnixOS2/logs/ the bootstrap was generated by "ux2_bootstrap.cmd 2>&1 >>\bootstrap.log" running blind and remembering to key 'enter' once at the beginning. Tip: after a successful build, move your logfile to some place which indicates success. -- Maynard _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 15 ==========================** Date: Mon, 27 Jan 2003 15:54:40 -0500 From: Ted Sikora Subject: tar failing in ux2bs Anyone have tar failing? It core dumps on perl and never untars completely when I remove the runtimes I had configured. -- Ted Sikora tsikora at ntplx.net _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 16 ==========================** Date: Mon, 27 Jan 2003 15:55:54 +0000 From: John Poltorak Subject: Re: Help Getting Perl to Run On Mon, Jan 27, 2003 at 10:39:34AM -0500, Hakan wrote: > Perl finished building with the following: > > Failed 4/726 test scripts, 99.45% okay. 370/68650 subtests failed, 99.46% okay. > Failed Test Stat Wstat Total Fail Failed List of Failed > ------------------------------------------------------------------------------- > ../lib/ExtUtils/t/basic.t 1 256 17 1 5.88% 14 > lib/os2_process.t 255 65280 227 184 81.06% 44-227 > lib/os2_process_kid.t 227 184 81.06% 44-227 > op/stat.t 73 1 1.37% 44 > 64 tests and 545 subtests skipped. Well done, Hakan. These results are as good as you could hope to get, AFAIAA. I'm glad you persevered with it. > Do these failures present a problem? I don't think so, but can't be certain. > BTW, on my Cyrix 586-100 and 64 > Mb of memory, the entire build process for perl took 44107 seconds, > i.e., a little over 12.hours.. Yes, building Perl is certainly a good way of testing out how powerful your mahine is. Now be carefull to create a Perl zip so that you don't need to go through all that again. Just zip up \usr\lib\perl and add \usr\bin\perl.exe and \usr\lib\perl*.dll. If you want to run Perl from a different drive other than the one you built it on, you will need to set some variable. Can't remeber which, off the top of my head... > Thanks for the help. > > Hakan -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 17 ==========================** Date: Mon, 27 Jan 2003 16:07:28 +0000 From: John Poltorak Subject: GROFF builds! I just grabbed the latest release of GROFF without making any changes or adding patches and ran:- build groff and to my amazement it worked! ... well at least groff --version produced this:- GNU groff version 1.18.1 Copyright (C) 2002 Free Software Foundation, Inc. GNU groff comes with ABSOLUTELY NO WARRANTY. You may redistribute copies of groff and its subprograms under the terms of the GNU General Public License. For more information about these matters, see the file named COPYING. The whole package didn't build completely and some things still need sorting out, but I'm very pleased things got as far as they did. I think this build system does show a lot of promise. -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 18 ==========================** Date: Mon, 27 Jan 2003 16:21:10 +0000 From: John Poltorak Subject: Re: Perl harness On Mon, Jan 27, 2003 at 10:14:11AM -0600, Maynard wrote: > > running perl harness from the workdir adds a new set of errors which do not fail during the build. > > ../lib/ExtUtils/t/Constant.t 255 65280 51 49 96.08% 3-51 > ../lib/ExtUtils/t/Embed.t 9 9 100.00% 1-9 During the build they are run from the 't' directory under perl's workdir. Maybe the different path at that point has some effect... > -- Maynard -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 19 ==========================** Date: Mon, 27 Jan 2003 16:37:37 -0500 From: Ted Sikora Subject: Perl Here's what mine fails with: In file included from D:\emx\include\fcntl.h:5, from os2.c:23: D:\emx\include\sys/fcntl.h:75: parse error before `off_t' D:\emx\include\sys/fcntl.h:75: warning: no semicolon at end of struct or union D:\emx\include\sys/fcntl.h:76: warning: type defaults to `int' in declaration of `l_len' D:\emx\include\sys/fcntl.h:76: warning: data definition has no type or storage c lass D:\emx\include\sys/fcntl.h:77: parse error before `l_pid' D:\emx\include\sys/fcntl.h:77: warning: type defaults to `int' in declaration of `l_pid' D:\emx\include\sys/fcntl.h:77: warning: data definition has no type or storage c lass D:\emx\include\sys/fcntl.h:80: parse error before `}' make: *** [os2.obj] Error 1 -- Ted Sikora tsikora at ntplx.net _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 20 ==========================** Date: Mon, 27 Jan 2003 16:44:13 -0600 (CST) From: "Maynard" Subject: Re: Logs of successful builds On Mon, 27 Jan 2003 22:28:38 +0000, John Poltorak wrote: >It isn't always clear whether there is a success or not. That's for sure! It'd be nice if we could provide some level of confidence; and for those builds which are known to have failed, comparison of log against the log of a successful build may provide direction toward fixing something. Thanks, -- Maynard _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 21 ==========================** Date: Mon, 27 Jan 2003 17:23:25 +0000 From: John Poltorak Subject: Building FILE --VuFqdY39xq5QZd4e Content-Type: text/plain; charset=us-ascii Can someone have a try an building FILE? You may need to do an RSYNC refresh first... I get an error but am told by the author that it is due to EMX not providing a couple of definitions and that I should be OK by adding these definitions into file.h typedef unsigned int uint32_t; typedef int int32_t; These types are actually defined in stdint.h which is part of glibc, so I thought that copying this header to my INCLUDE path, the errors would get sorted out. But they didn't, and neither did adding the two line above. Can anyone tell me what is going wrong? I'm attaching stdint.h in case anyone wants to give it a try... -- John --VuFqdY39xq5QZd4e Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="R:\\glibc-2.2.5\\sysdeps\\generic\\stdint.h" /* Copyright (C) 1997, 1998, 1999, 2000, 2001 Free Software Foundation, Inc. This file is part of the GNU C Library. The GNU C Library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. The GNU C Library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have received a copy of the GNU Lesser General Public License along with the GNU C Library; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA. */ /* * ISO C99: 7.18 Integer types */ #ifndef _STDINT_H #define _STDINT_H 1 #include #include #include /* Exact integral types. */ /* Signed. */ /* There is some amount of overlap with as known by inet code */ #ifndef __int8_t_defined # define __int8_t_defined typedef signed char int8_t; typedef short int int16_t; typedef int int32_t; # if __WORDSIZE == 64 typedef long int int64_t; # else __extension__ typedef long long int int64_t; # endif #endif /* Unsigned. */ typedef unsigned char uint8_t; typedef unsigned short int uint16_t; #ifndef __uint32_t_defined typedef unsigned int uint32_t; # define __uint32_t_defined #endif #if __WORDSIZE == 64 typedef unsigned long int uint64_t; #else __extension__ typedef unsigned long long int uint64_t; #endif /* Small types. */ /* Signed. */ typedef signed char int_least8_t; typedef short int int_least16_t; typedef int int_least32_t; #if __WORDSIZE == 64 typedef long int int_least64_t; #else __extension__ typedef long long int int_least64_t; #endif /* Unsigned. */ typedef unsigned char uint_least8_t; typedef unsigned short int uint_least16_t; typedef unsigned int uint_least32_t; #if __WORDSIZE == 64 typedef unsigned long int uint_least64_t; #else __extension__ typedef unsigned long long int uint_least64_t; #endif /* Fast types. */ /* Signed. */ typedef signed char int_fast8_t; #if __WORDSIZE == 64 typedef long int int_fast16_t; typedef long int int_fast32_t; typedef long int int_fast64_t; #else typedef int int_fast16_t; typedef int int_fast32_t; __extension__ typedef long long int int_fast64_t; #endif /* Unsigned. */ typedef unsigned char uint_fast8_t; #if __WORDSIZE == 64 typedef unsigned long int uint_fast16_t; typedef unsigned long int uint_fast32_t; typedef unsigned long int uint_fast64_t; #else typedef unsigned int uint_fast16_t; typedef unsigned int uint_fast32_t; __extension__ typedef unsigned long long int uint_fast64_t; #endif /* Types for `void *' pointers. */ #if __WORDSIZE == 64 # ifndef __intptr_t_defined typedef long int intptr_t; # define __intptr_t_defined # endif typedef unsigned long int uintptr_t; #else # ifndef __intptr_t_defined typedef int intptr_t; # define __intptr_t_defined # endif typedef unsigned int uintptr_t; #endif /* Largest integral types. */ #if __WORDSIZE == 64 typedef long int intmax_t; typedef unsigned long int uintmax_t; #else __extension__ typedef long long int intmax_t; __extension__ typedef unsigned long long int uintmax_t; #endif /* The ISO C99 standard specifies that in C++ implementations these macros should only be defined if explicitly requested. */ #if !defined __cplusplus || defined __STDC_LIMIT_MACROS # if __WORDSIZE == 64 # define __INT64_C(c) c ## L # define __UINT64_C(c) c ## UL # else # define __INT64_C(c) c ## LL # define __UINT64_C(c) c ## ULL # endif /* Limits of integral types. */ /* Minimum of signed integral types. */ # define INT8_MIN (-128) # define INT16_MIN (-32767-1) # define INT32_MIN (-2147483647-1) # define INT64_MIN (-__INT64_C(9223372036854775807)-1) /* Maximum of signed integral types. */ # define INT8_MAX (127) # define INT16_MAX (32767) # define INT32_MAX (2147483647) # define INT64_MAX (__INT64_C(9223372036854775807)) /* Maximum of unsigned integral types. */ # define UINT8_MAX (255) # define UINT16_MAX (65535) # define UINT32_MAX (4294967295U) # define UINT64_MAX (__UINT64_C(18446744073709551615)) /* Minimum of signed integral types having a minimum size. */ # define INT_LEAST8_MIN (-128) # define INT_LEAST16_MIN (-32767-1) # define INT_LEAST32_MIN (-2147483647-1) # define INT_LEAST64_MIN (-__INT64_C(9223372036854775807)-1) /* Maximum of signed integral types having a minimum size. */ # define INT_LEAST8_MAX (127) # define INT_LEAST16_MAX (32767) # define INT_LEAST32_MAX (2147483647) # define INT_LEAST64_MAX (__INT64_C(9223372036854775807)) /* Maximum of unsigned integral types having a minimum size. */ # define UINT_LEAST8_MAX (255) # define UINT_LEAST16_MAX (65535) # define UINT_LEAST32_MAX (4294967295U) # define UINT_LEAST64_MAX (__UINT64_C(18446744073709551615)) /* Minimum of fast signed integral types having a minimum size. */ # define INT_FAST8_MIN (-128) # if __WORDSIZE == 64 # define INT_FAST16_MIN (-9223372036854775807L-1) # define INT_FAST32_MIN (-9223372036854775807L-1) # else # define INT_FAST16_MIN (-2147483647-1) # define INT_FAST32_MIN (-2147483647-1) # endif # define INT_FAST64_MIN (-__INT64_C(9223372036854775807)-1) /* Maximum of fast signed integral types having a minimum size. */ # define INT_FAST8_MAX (127) # if __WORDSIZE == 64 # define INT_FAST16_MAX (9223372036854775807L) # define INT_FAST32_MAX (9223372036854775807L) # else # define INT_FAST16_MAX (2147483647) # define INT_FAST32_MAX (2147483647) # endif # define INT_FAST64_MAX (__INT64_C(9223372036854775807)) /* Maximum of fast unsigned integral types having a minimum size. */ # define UINT_FAST8_MAX (255) # if __WORDSIZE == 64 # define UINT_FAST16_MAX (18446744073709551615UL) # define UINT_FAST32_MAX (18446744073709551615UL) # else # define UINT_FAST16_MAX (4294967295U) # define UINT_FAST32_MAX (4294967295U) # endif # define UINT_FAST64_MAX (__UINT64_C(18446744073709551615)) /* Values to test for integral types holding `void *' pointer. */ # if __WORDSIZE == 64 # define INTPTR_MIN (-9223372036854775807L-1) # define INTPTR_MAX (9223372036854775807L) # define UINTPTR_MAX (18446744073709551615UL) # else # define INTPTR_MIN (-2147483647-1) # define INTPTR_MAX (2147483647) # define UINTPTR_MAX (4294967295U) # endif /* Minimum for largest signed integral type. */ # define INTMAX_MIN (-__INT64_C(9223372036854775807)-1) /* Maximum for largest signed integral type. */ # define INTMAX_MAX (__INT64_C(9223372036854775807)) /* Maximum for largest unsigned integral type. */ # define UINTMAX_MAX (__UINT64_C(18446744073709551615)) /* Limits of other integer types. */ /* Limits of `ptrdiff_t' type. */ # if __WORDSIZE == 64 # define PTRDIFF_MIN (-9223372036854775807L-1) # define PTRDIFF_MAX (9223372036854775807L) # else # define PTRDIFF_MIN (-2147483647-1) # define PTRDIFF_MAX (2147483647) # endif /* Limits of `sig_atomic_t'. */ # define SIG_ATOMIC_MIN (-2147483647-1) # define SIG_ATOMIC_MAX (2147483647) /* Limit of `size_t' type. */ # if __WORDSIZE == 64 # define SIZE_MAX (18446744073709551615UL) # else # define SIZE_MAX (4294967295U) # endif /* Limits of `wchar_t'. */ # ifndef WCHAR_MIN /* These constants might also be defined in . */ # define WCHAR_MIN __WCHAR_MIN # define WCHAR_MAX __WCHAR_MAX # endif /* Limits of `wint_t'. */ # define WINT_MIN (0u) # define WINT_MAX (4294967295u) #endif /* C++ && limit macros */ /* The ISO C99 standard specifies that in C++ implementations these should only be defined if explicitly requested. */ #if !defined __cplusplus || defined __STDC_CONSTANT_MACROS /* Signed. */ # define INT8_C(c) c # define INT16_C(c) c # define INT32_C(c) c # if __WORDSIZE == 64 # define INT64_C(c) c ## L # else # define INT64_C(c) c ## LL # endif /* Unsigned. */ # define UINT8_C(c) c ## U # define UINT16_C(c) c ## U # define UINT32_C(c) c ## U # if __WORDSIZE == 64 # define UINT64_C(c) c ## UL # else # define UINT64_C(c) c ## ULL # endif /* Maximal type. */ # if __WORDSIZE == 64 # define INTMAX_C(c) c ## L # define UINTMAX_C(c) c ## UL # else # define INTMAX_C(c) c ## LL # define UINTMAX_C(c) c ## ULL # endif #endif /* C++ && constant macros */ #endif /* stdint.h */ --VuFqdY39xq5QZd4e-- _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 22 ==========================** Date: Mon, 27 Jan 2003 17:52:19 +0000 From: John Poltorak Subject: Building SLANG When building SLANG do the only files which need to be copied to the build environment consist of:- ? slang.h slang.a Is there any option in the Makefile for actually installing them? -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 23 ==========================** Date: Mon, 27 Jan 2003 18:56:07 +0000 From: John Poltorak Subject: Re: Impressive! On Mon, Jan 27, 2003 at 12:34:13PM -0600, Maynard wrote: > Ted, > > >That's exactly what happened 6 zips failed to install because of it. I > >installed it for the runtime for rsync. > > I'm going to broadcast my ignorance here and maybe learn something..... > > Can we rebuild 'rsync' as 'static' so that EMX is not required? It's very easy to do when you can remember the correct CFLAGS to use, but I always forget... > -- Maynard -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 24 ==========================** Date: Mon, 27 Jan 2003 19:16:45 +0000 From: John Poltorak Subject: Re: Building FILE On Mon, Jan 27, 2003 at 12:42:34PM -0600, Maynard wrote: > John, > > Again, broadcasting my ignorance.... > > >I'm attaching stdint.h in case anyone wants to give it a try... > > isn't an associated file also required with *.h header files? > > aren't the #includes also required?: > #include > #include > #include Yes, you're right. I didn't even look at the header. Anyay, I copied those missing files but it didn't do any good. Apparently all we really need to do is define two types in file.h but I couldn't figure out how... > My build log: > > creating config.h > > make > > cd . && /unixos2/workdir/file-3.39/missing aclocal > > SYS1041: The name \unixos2\workdir\file-3.39\missing is not recognized > as an > internal or external command, operable program or batch file. I guess your file.log is slightly different to this:-.. u:/unixos2/workdir u:/unixos2/workdir/file-3.39 ./configure loading site script u:/unixos2/lib/config.site creating cache ./config.cache checking for a BSD compatible install... u:/usr/bin/install.exe checking whether build environment is sane... yes checking whether make sets ${MAKE}... yes checking for working aclocal... found checking for working autoconf... found checking for working automake... found checking for working autoheader... found checking for working makeinfo... found ISTR you didn't get Automake installed. If that is correct we need to revisit that app... -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 25 ==========================** Date: Mon, 27 Jan 2003 20:06:35 +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". Having thought about this some more, I think there should be an option to continue, since whilst the process is paused, the user does have the opportunity to correct the situation in another session and proceed without having to start again... > Regards, > Stefan -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 26 ==========================** Date: Mon, 27 Jan 2003 21:23:16 +0000 From: John Poltorak Subject: Re: Perl On Mon, Jan 27, 2003 at 04:37:37PM -0500, Ted Sikora wrote: > Here's what mine fails with: > > In file included from D:\emx\include\fcntl.h:5, > from os2.c:23: Have you overwritten an existing EMX installation with ux2_inst ? I can only suggest that you rename \emx and start again. > > -- > Ted Sikora > tsikora at ntplx.net -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 27 ==========================** Date: Mon, 27 Jan 2003 21:33:52 -0500 From: Ted Sikora Subject: 6/726 test failed 99.17% okay subsets 99.98% okay [D:\]perl --version This is perl, v5.8.0 built for os2 Copyright 1987-2002, Larry Wall OS/2 port Copyright (c) 1990, 1991, Raymond Chen, Kai Uwe Rommel Version 5 port Copyright (c) 1994-2002, Andreas Kaiser, Ilya Zakharevich Cool! After I built it I realized I had the old Perl env variables set. I'm positive I can reduce it to about 2-3 failed on another build. I added the following posix/2 headers to \emx\include: utmp.h syslog.h sys/syslog.h paths.h As far as I can see only inttype.h is missing to make it a complete unix compatible env. I was missing RXU.DLL and VREXX.DLL for one test. Anyone know where I can pick them up? I don't know what happened but I had to install the ux2bs manually then build perl with the perl.cmd script It seems to run okay. The only test that has me worried is the BIG::DUMMY which it failed 1 of 4. That's the test for building/adding modules. I need DBD/DBI::mysql installed. -- Ted Sikora tsikora at ntplx.net _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 28 ==========================** Date: Mon, 27 Jan 2003 22:04:40 -0500 From: Ted Sikora Subject: Perl env vaiables Do I need any of of these with the new build? SET PERLLIB_PREFIX= SET PERL_BADFREE=0 SET PERL_BADLANG=0 SET PERL_SH_DIR= SET PERL= -- Ted Sikora tsikora at ntplx.net _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 29 ==========================** Date: Mon, 27 Jan 2003 22:13:31 -0500 (EST) From: "Hakan" Subject: Re: Perl env vaiables On that topic, I would not mind being told exactly which environment variables I need to set to run perl (and to what) -- if indeed there are more than the ones Ted mentions below... TIA. Hakan On Mon, 27 Jan 2003 22:04:40 -0500, Ted Sikora wrote: >Do I need any of of these with the new build? > >SET PERLLIB_PREFIX= >SET PERL_BADFREE=0 >SET PERL_BADLANG=0 >SET PERL_SH_DIR= >SET PERL= > >-- >Ted Sikora >tsikora at ntplx.net > > > >_______________________________________________ >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 30 ==========================** Date: Mon, 27 Jan 2003 22:28:38 +0000 From: John Poltorak Subject: Re: Logs of successful builds On Mon, Jan 27, 2003 at 03:54:14PM -0600, Maynard wrote: > > I've now put all my successful logs, including bootstrap.log to > http://warped.mentabolism.org/UnixOS2/logs/ > > the bootstrap was generated by "ux2_bootstrap.cmd 2>&1 > >>\bootstrap.log" running blind and remembering to key 'enter' once at the beginning. > > Tip: after a successful build, move your logfile to some place which > indicates success. There are degrees of success... Sometimes an app builds but doesn't get installed for example, or there could be a large number of executables which should get created, but not all of them are. It isn't always clear whether there is a success or not. Also, it may appear that an app has built successfully, but simply crashes when you try running it. > > -- Maynard > > -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs