Date: Mon, 3 Mar 2003 02:37:59 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [Ux2bs_Archive] No. 94 ************************************************** Sunday 02 March 2003 Number 94 ************************************************** Subjects for today 1 Re: GETTEXT install failure : Maynard" 2 Re: Updating UX2BS : Ted Sikora 3 Re: GETTEXT install failure : John Poltorak 4 Re: Updating UX2BS : John Poltorak 5 Re: Updating UX2BS : Dave Saville" 6 Re: Updating UX2BS : John Poltorak 7 rsync : Dave Saville" 8 Re: rsync : John Poltorak 9 Re: rsync : Dave Saville" 10 Re: GETTEXT install failure : Andreas Buening **= Email 1 ==========================** Date: Mon, 03 Mar 2003 06:51:17 -0600 (CST) From: "Maynard" Subject: Re: GETTEXT install failure gettext is a pretty lengthy build; and the test/check even longer My notes indicate that when I start with the GNU distribution, and apply Andreas's patches *_except_for_* those in .../intl followed by ./configure and make and make install I feel like things went pretty good; but I had to abandon the tests because the last set, requiring a missing rpath, was just taking way too long. Andreas made the important point "Don't forget --disable-static or --disable-shared as libtool can't build a static and a dynamic library at the same time on OS/2." I figure this means that two cycles of configure-make-install are required, presuming that you can end up with both static and dynamic functionality when it is all over. He also recommends use of --with-included-gettext with configure Running autoconf didn't seem to help matters for me. Again, just patching ltmain.sh was sufficient to solve the immediate problem of executables in the wrong place. I don't know what other bennies accrue from Andreas's work. The readme.os2 in Andreas's distribution indicates a need for something which I don't have yet: libunixos2 0.1.1 Later, -- Maynard _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 2 ==========================** Date: Mon, 03 Mar 2003 09:58:12 +0000 From: Ted Sikora Subject: Re: Updating UX2BS John Poltorak wrote: > On Sun, Mar 02, 2003 at 09:31:32AM -0600, Maynard wrote: > >>John, >> >>Is the information on my page at >>http://warped.mentabolism.org/UnixOS2/updates.html accurate? > > > Currently, ux2_bootstrap.cmd refers to os2ports.com rather than > powerusersbbs.net. > That server is faster and on cron 2x daily so it would be the most current except for John's 'Master Server'. powerusersbbs.net is updated once nightly. > > rsync usually terminates with an error "rsync error: unexplained error > (code 241) at main.c(935)" which we just ignore because it doesn't > seem to indicate any real problem. It seems the OS/2 port has a glitch but that error could pretty much be ignored. It's seems to work fine and usually appears when finished. I thought it was the server setup but Unix clients work perfect with the OS/2 rsync server with no errors. So it has to do with the OS/2 client part. -- Ted Sikora tsikora at ntplx.net _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 3 ==========================** Date: Mon, 3 Mar 2003 13:50:05 +0000 From: John Poltorak Subject: Re: GETTEXT install failure On Mon, Mar 03, 2003 at 06:51:17AM -0600, Maynard wrote: > gettext is a pretty lengthy build; and the test/check even longer > > My notes indicate that when I start with the GNU distribution, and > apply Andreas's patches *_except_for_* those in .../intl followed by > ./configure and make and make install I feel like things went > pretty good; but I had to abandon the tests because the last set, > requiring a missing rpath, was just taking way too long. > > Andreas made the important point "Don't forget --disable-static or > --disable-shared as libtool can't build a static and a dynamic library > at the same time on OS/2." Are we bothered about building both? Which gets built by running 'build gettext' ? And is it sufficient? > He also recommends use of --with-included-gettext with configure I don't understand the point of that. What else could it use? > Running autoconf didn't seem to help matters for me. > > Again, just patching ltmain.sh was sufficient to solve the immediate > problem of executables in the wrong place. I'm tempted to just add that. What functionality is missing from the final product if this the only file patched? > I don't know what other > bennies accrue from Andreas's work. Me neither... > The readme.os2 in Andreas's distribution indicates a need for something > which I don't have yet: libunixos2 0.1.1 I'd prefer not to have this as a requirement at this stage. I don't really understand what it provides and have a feeling that it overlaps with Posix/2. I'd like to get Posix/2 properly integrated first before looking at other enhancements. > > Later, > > -- Maynard -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 4 ==========================** Date: Mon, 3 Mar 2003 14:28:29 +0000 From: John Poltorak Subject: Re: Updating UX2BS On Sun, Mar 02, 2003 at 09:31:32AM -0600, Maynard wrote: > John, > > Is the information on my page at > http://warped.mentabolism.org/UnixOS2/updates.html accurate? Currently, ux2_bootstrap.cmd refers to os2ports.com rather than powerusersbbs.net. rsync usually terminates with an error "rsync error: unexplained error (code 241) at main.c(935)" which we just ignore because it doesn't seem to indicate any real problem. It would be nice to be able to resolve this error... Is anyone up to the task? > Do you or others have suggestions for that content? > > Thanks, > > -- Maynard > > I'll soon have much reworking to do of the page at > http://warped.mentabolism.org/UnixOS2/ux2bs_0.html -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 5 ==========================** Date: Mon, 03 Mar 2003 16:47:05 +0000 (GMT) From: "Dave Saville" Subject: Re: Updating UX2BS On Mon, 3 Mar 2003 14:28:29 +0000, John Poltorak wrote: >On Sun, Mar 02, 2003 at 09:31:32AM -0600, Maynard wrote: >> John, >> >> Is the information on my page at >> http://warped.mentabolism.org/UnixOS2/updates.html accurate? > >Currently, ux2_bootstrap.cmd refers to os2ports.com rather than >powerusersbbs.net. > > > rsync usually terminates with an error "rsync error: unexplained error > (code 241) at main.c(935)" which we just ignore because it doesn't > seem to indicate any real problem. > > >It would be nice to be able to resolve this error... > >Is anyone up to the task? Dunno :-) But point me at the tar ball and I will have a hack. -- Regards Dave Saville _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 6 ==========================** Date: Mon, 3 Mar 2003 16:55:11 +0000 From: John Poltorak Subject: Re: Updating UX2BS On Mon, Mar 03, 2003 at 04:47:05PM +0000, Dave Saville wrote: > On Mon, 3 Mar 2003 14:28:29 +0000, John Poltorak wrote: > > >On Sun, Mar 02, 2003 at 09:31:32AM -0600, Maynard wrote: > >> John, > >> > >> Is the information on my page at > >> http://warped.mentabolism.org/UnixOS2/updates.html accurate? > > > >Currently, ux2_bootstrap.cmd refers to os2ports.com rather than > >powerusersbbs.net. > > > > > > rsync usually terminates with an error "rsync error: unexplained error > > (code 241) at main.c(935)" which we just ignore because it doesn't > > seem to indicate any real problem. > > > > > >It would be nice to be able to resolve this error... > > > >Is anyone up to the task? > > Dunno :-) But point me at the tar ball and I will have a hack. You could always try 'build rsync' and see how far you get :-)... build.table contains a lot of URLs. I'd like to keep it as uptodate as possible irrespective of whether an app currently builds on OS/2. > -- > Regards > > Dave Saville -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 7 ==========================** Date: Mon, 03 Mar 2003 17:45:09 +0000 (GMT) From: "Dave Saville" Subject: rsync tried build rsync - failed :-) checking compat.h presence... yes configure: WARNING: compat.h: present but cannot be compiled configure: WARNING: compat.h: check for missing prerequisite headers? configure: WARNING: compat.h: proceeding with the preprocessor's result configure: WARNING: ## ------------------------------------ ## configure: WARNING: ## Report this to bug-autoconf at gnu.org. ## configure: WARNING: ## ------------------------------------ ## checking for compat.h... yes e:\posix2\include\compat.h:43: warning: `O_EXLOCK' redefined e:\posix2\include\sys/fcntl.h:47: warning: this is the location of the previous definition e:\posix2\include\compat.h:44: warning: `O_SHLOCK' redefined e:\posix2\include\sys/fcntl.h:46: warning: this is the location of the previous definition e:\posix2\include\compat.h:52: warning: `MIN' redefined e:\posix2\include\sys/param.h:235: warning: this is the location of the previous definition e:\posix2\include\compat.h:53: warning: `MAX' redefined e:\posix2\include\sys/param.h:236: warning: this is the location of the previous definition In file included from rsync.h:217, from rsync.c:23: e:\posix2\include\compat.h:55: parse error before `char' make: *** [rsync.o] Error 1 compat.h has O_EXLOXK set to 0, fcntl.h has it set to hex 40 compat.h has O_SHLOCK set to 0, fcntl.h has it set to hex 20 MIN & MAX defs look the same bar an extra set of () line 55 of compat.h is typedef char *_BSD_VA_LIST_; I never did get my brain around typedefs :-) -- Regards Dave Saville _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 8 ==========================** Date: Mon, 3 Mar 2003 19:11:22 +0000 From: John Poltorak Subject: Re: rsync On Mon, Mar 03, 2003 at 05:45:09PM +0000, Dave Saville wrote: > tried build rsync - failed :-) > > checking compat.h presence... yes > configure: WARNING: compat.h: present but cannot be compiled > configure: WARNING: compat.h: check for missing prerequisite headers? > configure: WARNING: compat.h: proceeding with the preprocessor's > result > configure: WARNING: ## ------------------------------------ ## > configure: WARNING: ## Report this to bug-autoconf at gnu.org. ## > configure: WARNING: ## ------------------------------------ ## > checking for compat.h... yes > > > > > e:\posix2\include\compat.h:43: warning: `O_EXLOCK' redefined > e:\posix2\include\sys/fcntl.h:47: warning: this is the location of > the previous > definition > e:\posix2\include\compat.h:44: warning: `O_SHLOCK' redefined > e:\posix2\include\sys/fcntl.h:46: warning: this is the location of > the previous > definition > e:\posix2\include\compat.h:52: warning: `MIN' redefined > e:\posix2\include\sys/param.h:235: warning: this is the location of > the previous > definition > e:\posix2\include\compat.h:53: warning: `MAX' redefined > e:\posix2\include\sys/param.h:236: warning: this is the location of > the previous > definition > In file included from rsync.h:217, > from rsync.c:23: > e:\posix2\include\compat.h:55: parse error before `char' > make: *** [rsync.o] Error 1 > > > compat.h has O_EXLOXK set to 0, fcntl.h has it set to hex 40 > compat.h has O_SHLOCK set to 0, fcntl.h has it set to hex 20 These look like errors due to Posix/2... You can eliminate them by adding:- rsync; to p2_exc.lst. But then you will also need syslog.h and paths.h as a well as a syslog library, syslog.a. If you can assemble that lot then you also need to change the RSYNC makefile so that it includes:- LIBS=-lsyslog -lsocket ...in that order. Finally, you will need to run EMXBIND. I'd like to get this to build easily under UX2BS so 'build rsync' does everything required, but there are a few issues which need resolving first, one of which is how to build a SYSLOG library... > -- > Regards > > Dave Saville -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 9 ==========================** Date: Mon, 03 Mar 2003 19:54:08 +0000 (GMT) From: "Dave Saville" Subject: Re: rsync On Mon, 3 Mar 2003 19:11:22 +0000, John Poltorak wrote: >On Mon, Mar 03, 2003 at 05:45:09PM +0000, Dave Saville wrote: >> tried build rsync - failed :-) >> >> checking compat.h presence... yes >> configure: WARNING: compat.h: present but cannot be compiled >> configure: WARNING: compat.h: check for missing prerequisite headers? >> configure: WARNING: compat.h: proceeding with the preprocessor's >> result >> configure: WARNING: ## ------------------------------------ ## >> configure: WARNING: ## Report this to bug-autoconf at gnu.org. ## >> configure: WARNING: ## ------------------------------------ ## >> checking for compat.h... yes >> >> >> >> >> e:\posix2\include\compat.h:43: warning: `O_EXLOCK' redefined >> e:\posix2\include\sys/fcntl.h:47: warning: this is the location of >> the previous >> definition >> e:\posix2\include\compat.h:44: warning: `O_SHLOCK' redefined >> e:\posix2\include\sys/fcntl.h:46: warning: this is the location of >> the previous >> definition >> e:\posix2\include\compat.h:52: warning: `MIN' redefined >> e:\posix2\include\sys/param.h:235: warning: this is the location of >> the previous >> definition >> e:\posix2\include\compat.h:53: warning: `MAX' redefined >> e:\posix2\include\sys/param.h:236: warning: this is the location of >> the previous >> definition >> In file included from rsync.h:217, >> from rsync.c:23: >> e:\posix2\include\compat.h:55: parse error before `char' >> make: *** [rsync.o] Error 1 >> >> >> compat.h has O_EXLOXK set to 0, fcntl.h has it set to hex 40 >> compat.h has O_SHLOCK set to 0, fcntl.h has it set to hex 20 > >These look like errors due to Posix/2... > >You can eliminate them by adding:- > >rsync; > > >to p2_exc.lst. But then you will also need syslog.h and paths.h as a well >as a syslog library, syslog.a. If you can assemble that lot then you also >need to change the RSYNC makefile so that it includes:- > >LIBS=-lsyslog -lsocket > >...in that order. Finally, you will need to run EMXBIND. > >I'd like to get this to build easily under UX2BS so 'build rsync' does >everything required, but there are a few issues which need resolving >first, one of which is how to build a SYSLOG library... Hmm What *is* this compat.h creature anyway? -- Regards Dave Saville _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 10 ==========================** Date: Mon, 03 Mar 2003 21:10:39 +0100 From: Andreas Buening Subject: Re: GETTEXT install failure John Poltorak wrote: > > On Mon, Mar 03, 2003 at 06:51:17AM -0600, Maynard wrote: > > gettext is a pretty lengthy build; and the test/check even longer I've never tried "make check" for gettext. > > My notes indicate that when I start with the GNU distribution, and > > apply Andreas's patches *_except_for_* those in .../intl followed by > > ./configure and make and make install I feel like things went > > pretty good; but I had to abandon the tests because the last set, > > requiring a missing rpath, was just taking way too long. > > > > Andreas made the important point "Don't forget --disable-static or > > --disable-shared as libtool can't build a static and a dynamic library > > at the same time on OS/2." > > Are we bothered about building both? Depends on what you want to do. > Which gets built by running 'build gettext' ? And is it sufficient? > > > He also recommends use of --with-included-gettext with configure > > I don't understand the point of that. What else could it use? It could try to use an external gettext which is the default. You'd better specify --with-included-gettext. > > Running autoconf didn't seem to help matters for me. > > > > Again, just patching ltmain.sh was sufficient to solve the immediate > > problem of executables in the wrong place. > > I'm tempted to just add that. What functionality is missing from the final > product if this the only file patched? Depending on your configure options, your LIBS, your *FLAGS and the mean room temperature - the library might not compile - the library might not work or not work as expected - the tools might not compile - the tools might not work - make install might fail > > I don't know what other > > bennies accrue from Andreas's work. > > Me neither... The idea of all those patches is to get a working gettext. > > The readme.os2 in Andreas's distribution indicates a need for something > > which I don't have yet: libunixos2 0.1.1 > > I'd prefer not to have this as a requirement at this stage. I don't really > understand what it provides and have a feeling that it overlaps with > Posix/2. I'd like to get Posix/2 properly integrated first before looking > at other enhancements. One of the gettext tools requires either a working fork() or posix_spawn(). Bye, Andreas -- One OS to rule them all, One OS to find them, One OS to bring them all and in the darkness bind them In the Land of Mordor where the Shadows lie. _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs