Date: Sun, 19 Jan 2003 02:27:47 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [Ux2bs_Archive] No. 51 ************************************************** Saturday 18 January 2003 Number 51 ************************************************** Subjects for today 1 UX2BS -- confirmation of subscription -- request 254182 : ux2bs-request at powerusersbbs.net 2 Re: building PERL: 4/726 and 6/68650 : Maynard" 3 Welcome to the "UX2BS" mailing list : ux2bs-request at powerusersbbs.net 4 building PERL: 2/726 and 4/68650 : Maynard" 5 %uxrt% =??= %bldrt% : Maynard" 6 Re: Autoconf : Maynard" 7 Greetings & building JOE : Marty" 8 Re: Greetings & building JOE : Marty" 9 Getting started : John Poltorak 10 Re: building PERL: 4/726 and 6/68650 : John Poltorak 11 Autoconf : John Poltorak 12 Re: building PERL: 2/726 and 4/68650 : John Poltorak 13 Re: Greetings & building JOE : Marty" 14 Re: Autoconf : John Poltorak 15 Re: Greetings & building JOE : John Poltorak 16 Re: =?iso-8859-1?Q?=5BUx2bs=5D_%uxrt%_=3D=3F=3F=3D_%bldrt%?= : John Poltorak 17 Re: Greetings & building JOE : John Poltorak **= Email 1 ==========================** Date: Sun, 19 Jan 2003 11:03:13 -0500 From: ux2bs-request at powerusersbbs.net Subject: UX2BS -- confirmation of subscription -- request xxxxxxx If you do not wish to subscribe to this list, please simply disregard this message. Send questions to ux2bs-admin at powerusersbbs.net. **= Email 2 ==========================** Date: Sun, 19 Jan 2003 11:03:28 -0600 (CST) From: "Maynard" Subject: Re: building PERL: 4/726 and 6/68650 improvement: Failed 3/726 test scripts, 99.59% okay. 5/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/rx_cmprt.t 255 65280 18 3 16.67% 16-18 64 tests and 557 subtests skipped. >> %uxrt% == %bldrt% still true for this result >> ../lib/ExtUtils/t/basic.t 1 256 17 1 5.88% 14 >BUG in distribution. >> ../lib/Net/t/hostname.t 2 1 50.00% 1 >Not sure about this one yet... I got this test to pass by adding envars for DOMAIN and DOMAINNAME I'm running now to see which one was responsible. >> lib/os2_base.t 1 256 19 1 5.26% 8 >Did you delete the perl dll from \usr\lib before running this test? This test passes when there is NO prior perl in \usr\lib >> lib/rx_cmprt.t 255 65280 18 3 16.67% 16-18 >Object REXX missing. >> P:\etc\resolv >Does this make any difference at all? $ETC/resolve is not required; did not exist for this test P:\etc\hosts P:\etc\protocol P:\etc\services Environment for this build included: COMSPEC=N:\OS2\CMD.EXE OS2_SHELL=N:\OS2\CMD.EXE HOSTNAME=arcturus TERM=ansi-color-3 NOTE: I think that the trick to passing tests: lib/os2_process.t lib/os2_process_kid.t is to let the build work in the foreground, and not be fighting with the tests for focus. _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 3 ==========================** Date: Sun, 19 Jan 2003 11:13:07 -0500 From: ux2bs-request at powerusersbbs.net Subject: Welcome to the "UX2BS" mailing list Welcome to the UX2BS at powerusersbbs.net mailing list! **= Email 4 ==========================** Date: Sun, 19 Jan 2003 11:41:02 -0600 (CST) From: "Maynard" Subject: building PERL: 2/726 and 4/68650 Failed 2/726 test scripts, 99.72% okay. 4/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/rx_cmprt.t 255 65280 18 3 16.67% 16-18 64 tests and 557 subtests skipped. These are known errors; the first a bug; the second three are because I don't have Object Rexx installed. envars: OSRT=N: UXRT=P: BLDRT=P: PATH=P:\usr\bin;P:\emx\bin;P:\usr\local\bin;N:\os2; TMP=P:\tmp HOME=P:/home/root BLD_HOME=P:/unixos2 REPOSITORY=P:/unixos2/archives/source WORKDIR=P:/unixos2/workdir BUILDLOGS=P:/unixos2/logs CONFIG_SITE=P:/unixos2/lib/config.site C_INCLUDE_PATH=P:/usr/include CPLUS_INCLUDE_PATH=P:/usr/include/cpp;P:/usr/include LIBRARY_PATH=P:/usr/lib ETC=P:\etc COMSPEC=N:\OS2\CMD.EXE OS2_SHELL=N:\OS2\CMD.EXE HOSTNAME=arcturus TERM=ansi-color-3 DOMAIN=unixos2.com /etc: P:\etc\hosts P:\etc\protocol P:\etc\services _______________________________________________ UX2bs mailing list UX2bs at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 5 ==========================** Date: Sun, 19 Jan 2003 12:31:39 -0600 (CST) From: "Maynard" Subject: %uxrt% =??= %bldrt% On Sun, 19 Jan 2003 17:33:19 +0000, John Poltorak wrote: >> >> %uxrt% == %bldrt% >> still true for this result > >I wonder why this makes a difference... when UXRT != BLDRT, DIALOG fails to build with: checking for ncurses header in include-path... no checking for ncurses include-path... configure: error: not found make make: *** No targets. Stop. make: *** No rule to make target `install'. Stop. the following two PERL tests fail: op/grent.t 3 1 33.33% 2 op/pwent.t 2 1 50.00% 1 Note: # pwd /UNIXOS2/workdir/perl-5.8.0 # ./perl t/op/pwent.t 1..0 # Skip: no /etc/passwd file In the above test, %bldrt%/etc/passwd did not exist while %uxrt%/etc/passwd did exist. Moving passwd from %uxrt% to %bldrt% results in: # ./perl t/op/pwent.t 1..2 # where /etc/passwd # max = 25, n = 25, perfect = 0 # # The failure of op/pwent test is not necessarily serious. # It may fail due to local password administration conventions. # If you are for example using both NIS and local passwords, # test failure is possible. Any distributed password scheme # can cause such failures. # # What the pwent test is doing is that it compares the 26 first # entries of /etc/passwd # with the results of getpwuid() and getpwnam() call. If it finds no # matches at all, it suspects something is wrong. # not ok 1 # (not necessarily serious: run t/op/pwent.t by itself) ok 2 # _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 6 ==========================** Date: Sun, 19 Jan 2003 12:47:24 -0600 (CST) From: "Maynard" Subject: Re: Autoconf On Sun, 19 Jan 2003 17:36:49 +0000, John Poltorak wrote: >When I try building Autoconf it gets into a continous loop during Make. Here's my log snippets: make[2]: Entering directory `/unixos2/workdir/autoconf-2.57/bin' P:/bin/sh ../config/mkinstalldirs /usr/local/bin P:/usr/bin/install.exe -c autom4te /usr/local/bin/autom4te P:/usr/bin/install.exe -c autoconf /usr/local/bin/autoconf P:/usr/bin/install.exe -c autoheader /usr/local/bin/autoheader P:/usr/bin/install.exe -c autoreconf /usr/local/bin/autoreconf P:/usr/bin/install.exe -c ifnames /usr/local/bin/ifnames P:/usr/bin/install.exe -c autoscan /usr/local/bin/autoscan P:/usr/bin/install.exe -c autoupdate /usr/local/bin/autoupdate make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/unixos2/workdir/autoconf-2.57/bin' make[1]: Leaving directory `/unixos2/workdir/autoconf-2.57/bin' Making install in tests make[1]: Entering directory `/unixos2/workdir/autoconf-2.57/tests' .... make[52]: Entering directory `/unixos2/workdir/autoconf-2.57/bin' P:/bin/sh ../config/mkinstalldirs /usr/local/bin P:/usr/bin/install.exe -c autom4te /usr/local/bin/autom4te P:/usr/bin/install.exe -c autoconf /usr/local/bin/autoconf P:/usr/bin/install.exe -c autoheader /usr/local/bin/autoheader P:/usr/bin/install.exe -c autoreconf /usr/local/bin/autoreconf P:/usr/bin/install.exe -c ifnames /usr/local/bin/ifnames P:/usr/bin/install.exe -c autoscan /usr/local/bin/autoscan P:/usr/bin/install.exe -c autoupdate /usr/local/bin/autoupdate make[52]: Nothing to be done for `install-data-am'. make[52]: Leaving directory `/unixos2/workdir/autoconf-2.57/bin' make[51]: Leaving directory `/unixos2/workdir/autoconf-2.57/bin' Making install in tests make[51]: Entering directory `/unixos2/workdir/autoconf-2.57/tests' .... make[53]: Entering directory `/unixos2/workdir/autoconf-2.57/bin' make[53]: *** [install-binSCRIPTS] Error 295 make[53]: Leaving directory `/unixos2/workdir/autoconf-2.57/bin' make[52]: *** [install-am] Error 2 make[52]: Leaving directory `/unixos2/workdir/autoconf-2.57/bin' .... make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/unixos2/workdir/autoconf-2.57' make: *** [install-recursive] Error 1 Sun Jan 19 12:35:18 GMT 2003 elapsed time: 109 secs does install however: P:\usr\local\bin\autoconf P:\usr\local\bin\autoheader P:\usr\local\bin\autom4te P:\usr\local\bin\autoreconf P:\usr\local\bin\autoscan P:\usr\local\bin\autoupdate _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 7 ==========================** Date: Sun, 19 Jan 2003 13:34:59 -0500 (EST) From: "Marty" Subject: Greetings & building JOE Howdy folks. Just joined the list. So far from what I've seen of the build system it's looking very good. Perl and NCurses build on my system without any hassle at all. Because it was so easy to get that far, I took it upon myself to try to build Joe's Own Editor (JOE) with the build system. For those who aren't familiar with it, this is a really good console-based text editor that's been around forever, which can handle extremely large files quickly and has advanced features like incremental search, embedded shell, on-line help, fully remappable keyboard, spell check and compiler integration, and many others. Firstly, I added an appropriate line to \unixos2\lib\build.table as follows: joe;joe-2.9.7;http://umn.dl.sourceforge.net/sourceforge/joe-editor/joe-2.9.7.tgz;;-l bsd;;;. I needed the -lbsd libflag for the "random" function. I also needed to build ncurses first. Next, since the archive was a .TGZ file (not a .tar.gz) I had to tweak the build.sh script to support this. I changed the "if" block starting on line 35 to read: if test -f $REPOSITORY/$ARCHIVE.tar.gz; then ARCHIVEFILE=$REPOSITORY/$ARCHIVE.tar.gz else { if test -f $REPOSITORY/$ARCHIVE.tgz; then ARCHIVEFILE=$REPOSITORY/$ARCHIVE.tgz else { grep ^$ARCHIVE build.aliases > $TMP/ux2_tmp read p1 ALIAS < $TMP/ux2_tmp ARCHIVEFILE=$REPOSITORY/$ALIAS.tar.gz } fi } fi Of course you should also look for aliases with the tgz extension if it fails to find the .tar.gz, but that'll be left as an exercise to the reader. After that, I started to build and found that it was looking for /usr/include/sys/termios.h (which doesn't exist) and /usr/include/termios.h (which does). I got around this problem by simply creating an empty file at /usr/include/sys/termios.h. After that, I got all the way through the build to the linking phase, where it barfed due to missing symbols: b.o: Undefined symbol _lstat referenced from text segment b.o: Undefined symbol _fchmod referenced from text segment path.o: Undefined symbol _fchmod referenced from text segment tty.o: Undefined symbol _siginterrupt referenced from text segment tty.o: Undefined symbol _siginterrupt referenced from text segment tty.o: Undefined symbol _setpgrp referenced from text segment Other than that, the build looks like it's working. Anyone know if we have compatibility libraries that define these functions? I did an OBJDUMP on every library I had, grepping for them and I couldn't find them anywhere. _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 8 ==========================** Date: Sun, 19 Jan 2003 15:38:07 -0500 (EST) From: "Marty" Subject: Re: Greetings & building JOE On Sun, 19 Jan 2003 20:08:04 +0000, John Poltorak wrote: > I was hoping to incorporate the Posix/2 headers and library, which may > solve some of these problems, but I didn't get very far in building Perl > with those in place. > > siginterrupt is defined in signal.h of the Posix/2 headers, but not in the > EMX headers. > > So do you basically have a working JOE now? As for the build, yes. As for the functionality, I have no idea yet. Hopefully the ncurses package that I built with the new environment will work better than the one I was using for the last time I attempted to port JOE. > And the only additional thing I need to do to build it is:- ? > > touch /usr/include/sys/termios.h Yup. And I have the feeling the Posix/2 headers would eliminate the need to do this too. The last time I got a pseudo-working port of JOE going, I had to actually edit the source code to eliminate the need to use these functions, but I have the feeling it would benefit society as a whole more to get the source distribution working as is with a fixed build environment, which may in turn help other ports. _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 9 ==========================** Date: Sun, 19 Jan 2003 16:10:31 +0000 From: John Poltorak Subject: Getting started For anyone new to the list, or who hasn't felt like dipping their toes in the water yet, the aim of the list is to produce a standard OS/2 build environment for building Unix apps. You should be able to this by running this command:- wget ftp://unixos2: at 213.152.37.92/pub/unixos2/build_system/lib/ux2_bootstrap.cmd and then running the retrived ux2_bootstrap.cmd to pull down everything you need to create the standard build environment, and assuming everything goes to plan, it will proceed to build Perl v5.8.0. Before running the command, you need to change three variables at the beginning of the script. It seems that it works best if %UXRT% and %BLDRT% use the same drive - not sure why, since it shouldn't make a difference. Also, if you do not have a C: drive accessible by OS/2 you may as well forget trying to build Perl... :-(... A couple of things to watch... Make sure you do not have a \emx or \usr drive on %exrt% as they are likely to get overwritten. You also need around 100MB free to get anywhere... If Perl does build, please post the test results summary. This should be the last few lines in \unixos2\logs\perl.log and hopefully will look something like:- Failed 6/726 test scripts, 99.17% okay. 10/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% 174 209 lib/os2_process_kid.t 227 2 0.88% 174 209 lib/rx_cmprt.t 255 65280 18 3 16.67% 16-18 op/stat.t 73 1 1.37% 44 64 tests and 561 subtests skipped. Now lets see some results from a few new people... -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 10 ==========================** Date: Sun, 19 Jan 2003 17:33:19 +0000 From: John Poltorak Subject: Re: building PERL: 4/726 and 6/68650 On Sun, Jan 19, 2003 at 11:03:28AM -0600, Maynard wrote: > improvement: > > Failed 3/726 test scripts, 99.59% okay. 5/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/rx_cmprt.t 255 65280 18 3 16.67% 16-18 > 64 tests and 557 subtests skipped. Good. I think 2 fails is the best we can hope for, unless Object REXX is installed. > >> %uxrt% == %bldrt% > still true for this result I wonder why this makes a difference... > >> ../lib/Net/t/hostname.t 2 1 50.00% 1 > >Not sure about this one yet... > I got this test to pass by adding envars for DOMAIN and DOMAINNAME > I'm running now to see which one was responsible. Strange - I'm not familiar with any requirement to set up either of these variables. > HOSTNAME=arcturus Does this make any difference to the results? > NOTE: I think that the trick to passing tests: > lib/os2_process.t > lib/os2_process_kid.t > is to let the build work in the foreground, and not be fighting with > the tests for focus. I'm not really sure about that. I think the results of some of the tests may be deternined my screen resolution or something like that. I always get a couple of fails. Maybe I'll try running the tests individually... -- John _______________________________________________ UX2bs mailing list UX2bs at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 11 ==========================** Date: Sun, 19 Jan 2003 17:36:49 +0000 From: John Poltorak Subject: Autoconf When I try building Autoconf it gets into a continous loop during Make. Can anyone confirm this, or even suggest what the problem might be? -- John _______________________________________________ UX2bs mailing list UX2bs at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 12 ==========================** Date: Sun, 19 Jan 2003 18:02:56 +0000 From: John Poltorak Subject: Re: building PERL: 2/726 and 4/68650 On Sun, Jan 19, 2003 at 11:41:02AM -0600, Maynard wrote: > Failed 2/726 test scripts, 99.72% okay. 4/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/rx_cmprt.t 255 65280 18 3 16.67% 16-18 > 64 tests and 557 subtests skipped. > > These are known errors; the first a bug; the second three are because I don't have Object Rexx installed. Well done. That looks like it's as good as it is going to get, unless you really want to get on the bleeding edge... Ilyaz sent me this command to get the most recent source which includes all the latest patches:- rsync -avz rsync://ftp.linux.activestate.com/perl-5.8.x/ . |& tee 00rs That is exactly as he sent it but the '|& tee 00rs' bit doesn't make complete sense to me - maybe a typo. Anyway, if you feel adventurous you could try the most update source and see if it removes those two final errors. I think it is supposed to. > envars: > DOMAIN=unixos2.com I'm suprised at this. I would have thought it could be established some other way, either through the resolver - maybe it looks for RESOLV2 and not RESOLV, or it may get it from a fully qualified hostname in the environment. -- John _______________________________________________ UX2bs mailing list UX2bs at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 13 ==========================** Date: Sun, 19 Jan 2003 18:25:55 -0500 (EST) From: "Marty" Subject: Re: Greetings & building JOE On Sun, 19 Jan 2003 21:35:40 +0000, John Poltorak wrote: > Hmm... I gave it a try and it collapsed here:- > > depmode=gcc u:/bin/sh ./depcomp \ > gcc -DHAVE_CONFIG_H -I. -I. -I. -DJOERC="\"/usr/local/etc/\"" -c `test > -f utils.c || echo './'`utils.c > gcc -o joe.exe b.o blocks.o bw.o cmd.o hash.o help.o kbd.o macro.o > main.o menu.o path.o poshist.o pw.o queue.o qw.o rc.o regex.o scrn.o tab.o > termcap.o tty.o tw.o ublock.o uedit.o uerror.o ufile.o uformat.o uisrch.o > umath.o undo.o usearch.o ushell.o utag.o va.o vfile.o vs.o w.o utils.o > -lncurses That's where it dies for me too, but didn't the LDFLAGS (-lbsd) make it through? Apparently not. That should get rid of the undefined "random"s. > Have you installed Autoconf, BTW? I think that's part of the script bootstrap that I ran. I see a workdir for it, so I assume it has been processed. > I started with the supplied configure. > All I did was created a termios.h file and ran:- > > build joe Same here. Maybe going the autoconf route gets better results. I'll give it a try, though I usually just throw up my hands and say "screw it" at the first error I see autoconf spit out. > I often think that there are too many #ifdef's for EMX in many ports and > that they wouldn't be necessary if the environment was right. I agree. It's so close already that we might as well just get it *right* rather than tweaking everything in existence. > Essentially, coming up with the correct build framework is my principle > concern here. Building apps is a way of testing it as well as providing a > simplified way of building them, and if we get updated versions of apps > like JOE, that is an added bonus. The other "pro" here is that we don't have to submit changes to the authors or worse yet continually patch the source when the authors release an updated version without our needed changes. I got into that game with MAME a while back and man was that obnoxious. _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 14 ==========================** Date: Sun, 19 Jan 2003 19:54:16 +0000 From: John Poltorak Subject: Re: Autoconf On Sun, Jan 19, 2003 at 12:47:24PM -0600, Maynard wrote: > On Sun, 19 Jan 2003 17:36:49 +0000, John Poltorak wrote: > > >When I try building Autoconf it gets into a continous loop during Make. > > Here's my log snippets: > > make[2]: Entering directory `/unixos2/workdir/autoconf-2.57/bin' > P:/bin/sh ../config/mkinstalldirs /usr/local/bin > P:/usr/bin/install.exe -c autom4te /usr/local/bin/autom4te ... > make[2]: Nothing to be done for `install-data-am'. > make[2]: Leaving directory `/unixos2/workdir/autoconf-2.57/bin' > make[1]: Leaving directory `/unixos2/workdir/autoconf-2.57/bin' > Making install in tests > make[1]: Entering directory `/unixos2/workdir/autoconf-2.57/tests' > .... > make[52]: Entering directory `/unixos2/workdir/autoconf-2.57/bin' > P:/bin/sh ../config/mkinstalldirs /usr/local/bin > P:/usr/bin/install.exe -c autom4te /usr/local/bin/autom4te On and on and on it goes.... If anyone understands the debug output from make, maybe they could pinpoint the problem. I notice there are two debug options for make:- -d Print lots of debugging information. --debug[=FLAGS] Print various types of debugging information. but don't how different the output from either is... > does install however: > > P:\usr\local\bin\autoconf Yes, **52** times before it packed in, but unfortunately it doen't install fully... I'd really like to figure out why. It doesn't do this with a more recent version of Make, but I'd prefer not to update the baseline toolset unless I have to. -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 15 ==========================** Date: Sun, 19 Jan 2003 20:08:04 +0000 From: John Poltorak Subject: Re: Greetings & building JOE On Sun, Jan 19, 2003 at 01:34:59PM -0500, Marty wrote: > Howdy folks. Just joined the list. Good to see you on board, Marty. > So far from what I've seen of the build system > it's looking very good. Perl and NCurses build on my system without any hassle at > all. > > Because it was so easy to get that far, I took it upon myself to try to build Joe's > Own Editor (JOE) with the build system. For those who aren't familiar with it, this > is a really good console-based text editor that's been around forever, which can > handle extremely large files quickly and has advanced features like incremental > search, embedded shell, on-line help, fully remappable keyboard, spell check and > compiler integration, and many others. > > Firstly, I added an appropriate line to \unixos2\lib\build.table as follows: > joe;joe-2.9.7;http://umn.dl.sourceforge.net/sourceforge/joe-editor/joe-2.9.7.tgz;;-l > bsd;;;. > > I needed the -lbsd libflag for the "random" function. I also needed to build > ncurses first. > > Next, since the archive was a .TGZ file (not a .tar.gz) I had to tweak the build.sh > script to support this. I changed the "if" block starting on line 35 to read: > if test -f $REPOSITORY/$ARCHIVE.tar.gz; then > ARCHIVEFILE=$REPOSITORY/$ARCHIVE.tar.gz > else > { > if test -f $REPOSITORY/$ARCHIVE.tgz; then > ARCHIVEFILE=$REPOSITORY/$ARCHIVE.tgz > else > { > grep ^$ARCHIVE build.aliases > $TMP/ux2_tmp > read p1 ALIAS < $TMP/ux2_tmp > ARCHIVEFILE=$REPOSITORY/$ALIAS.tar.gz > } > fi > } > fi I'm glad you figured out how to add a new app. > After that, I started to build and found that it was looking for > /usr/include/sys/termios.h (which doesn't exist) and /usr/include/termios.h (which > does). I got around this problem by simply creating an empty file at > /usr/include/sys/termios.h. > > After that, I got all the way through the build to the linking phase, where it > barfed due to missing symbols: > b.o: Undefined symbol _lstat referenced from text segment > b.o: Undefined symbol _fchmod referenced from text segment > path.o: Undefined symbol _fchmod referenced from text segment > tty.o: Undefined symbol _siginterrupt referenced from text segment > tty.o: Undefined symbol _siginterrupt referenced from text segment > tty.o: Undefined symbol _setpgrp referenced from text segment > > Other than that, the build looks like it's working. Anyone know if we have > compatibility libraries that define these functions? I did an OBJDUMP on every > library I had, grepping for them and I couldn't find them anywhere. I was hoping to incorporate the Posix/2 headers and library, which may solve some of these problems, but I didn't get very far in building Perl with those in place. siginterrupt is defined in signal.h of the Posix/2 headers, but not in the EMX headers. So do you basically have a working JOE now? And the only additional thing I need to do to build it is:- ? touch /usr/include/sys/termios.h -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 16 ==========================** Date: Sun, 19 Jan 2003 20:18:24 +0000 From: John Poltorak Subject: Re: =?iso-8859-1?Q?=5BUx2bs=5D_%uxrt%_=3D=3F=3F=3D_%bldrt%?= On Sun, Jan 19, 2003 at 12:31:39PM -0600, Maynard wrote: > On Sun, 19 Jan 2003 17:33:19 +0000, John Poltorak wrote: > > >> >> %uxrt% == %bldrt% > >> still true for this result > > > >I wonder why this makes a difference... > > when UXRT != BLDRT, > > DIALOG fails to build with: > checking for ncurses header in include-path... no > checking for ncurses include-path... configure: error: not found > make > make: *** No targets. Stop. > make: *** No rule to make target `install'. Stop. This may be fixable by adding this line:- export CPPFLAGS=-I$UXRT/usr/include/ncurses to \unixos2\scripts\pre-process\dialog. > the following two PERL tests fail: > op/grent.t 3 1 33.33% 2 > op/pwent.t 2 1 50.00% 1 > > Note: > # pwd > /UNIXOS2/workdir/perl-5.8.0 > # ./perl t/op/pwent.t > 1..0 # Skip: no /etc/passwd file > > In the above test, %bldrt%/etc/passwd did not exist while %uxrt%/etc/passwd did exist. > Moving passwd from %uxrt% to %bldrt% results in: > # ./perl t/op/pwent.t > 1..2 > # where /etc/passwd > # max = 25, n = 25, perfect = 0 > # > # The failure of op/pwent test is not necessarily serious. > # It may fail due to local password administration conventions. > # If you are for example using both NIS and local passwords, > # test failure is possible. Any distributed password scheme > # can cause such failures. > # > # What the pwent test is doing is that it compares the 26 first > # entries of /etc/passwd > # with the results of getpwuid() and getpwnam() call. If it finds no > # matches at all, it suspects something is wrong. > # > not ok 1 # (not necessarily serious: run t/op/pwent.t by itself) > ok 2 > # I'm not sure there is anthing we can do about this, but the error seems fairly minor. -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 17 ==========================** Date: Sun, 19 Jan 2003 21:35:40 +0000 From: John Poltorak Subject: Re: Greetings & building JOE On Sun, Jan 19, 2003 at 03:38:07PM -0500, Marty wrote: > On Sun, 19 Jan 2003 20:08:04 +0000, John Poltorak wrote: > > > I was hoping to incorporate the Posix/2 headers and library, which may > > solve some of these problems, but I didn't get very far in building Perl > > with those in place. > > > > siginterrupt is defined in signal.h of the Posix/2 headers, but not in the > > EMX headers. > > > > So do you basically have a working JOE now? > > As for the build, yes. As for the functionality, I have no idea yet. Hopefully the > ncurses package that I built with the new environment will work better than the one > I was using for the last time I attempted to port JOE. > > > And the only additional thing I need to do to build it is:- ? > > > > touch /usr/include/sys/termios.h > > Yup. Hmm... I gave it a try and it collapsed here:- depmode=gcc u:/bin/sh ./depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I. -DJOERC="\"/usr/local/etc/\"" -c `test -f utils.c || echo './'`utils.c gcc -o joe.exe b.o blocks.o bw.o cmd.o hash.o help.o kbd.o macro.o main.o menu.o path.o poshist.o pw.o queue.o qw.o rc.o regex.o scrn.o tab.o termcap.o tty.o tw.o ublock.o uedit.o uerror.o ufile.o uformat.o uisrch.o umath.o undo.o usearch.o ushell.o utag.o va.o vfile.o vs.o w.o utils.o -lncurses b.o: Undefined symbol _lstat referenced from text segment b.o: Undefined symbol _fchmod referenced from text segment path.o: Undefined symbol _fchmod referenced from text segment tty.o: Undefined symbol _siginterrupt referenced from text segment tty.o: Undefined symbol _siginterrupt referenced from text segment tty.o: Undefined symbol _setpgrp referenced from text segment vfile.o: Undefined symbol _random referenced from text segment vfile.o: Undefined symbol _random referenced from text segment make: *** [joe.exe] Error 1 Have you installed Autoconf, BTW? I started with the supplied configure. All I did was created a termios.h file and ran:- build joe > And I have the feeling the Posix/2 headers would eliminate the need to > do this too. I hope you're right. > The last time I got a pseudo-working port of JOE going, I had to actually edit the > source code to eliminate the need to use these functions, but I have the feeling it > would benefit society as a whole more to get the source distribution working as is > with a fixed build environment, which may in turn help other ports. I often think that there are too many #ifdef's for EMX in many ports and that they wouldn't be necessary if the environment was right. Essentially, coming up with the correct build framework is my principle concern here. Building apps is a way of testing it as well as providing a simplified way of building them, and if we get updated versions of apps like JOE, that is an added bonus. -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs