Date: Thu, 30 Jan 2003 02:29:07 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [Ux2bs_Archive] No. 62 ************************************************** Wednesday 29 January 2003 Number 62 ************************************************** Subjects for today 1 Re: GROFF progress : Sebastian Wittmeier (ShadoW)" 2 Re: TIN : Maynard" 3 Re: TIN : Patrick Ash 4 Re: Building ZLIB : Maynard" 5 Re: TIN : John Poltorak 6 Re: GROFF progress : John Poltorak 7 Building ZLIB : John Poltorak 8 ZLIB : John Poltorak 9 BYACC build : John Poltorak 10 Re: Building ZLIB : John Poltorak 11 Building BIND : John Poltorak 12 Re: ux2 posix : John Poltorak 13 Re: ux2 posix : Andreas Buening 14 Re: ux2 posix : Thomas Hoffmann **= Email 1 ==========================** Date: Thu, 30 Jan 2003 00:11:06 +0100 (CET) From: "Sebastian Wittmeier (ShadoW)" Subject: Re: GROFF progress On Wed, 29 Jan 2003 21:16:59 +0000, John Poltorak wrote: >There is a problem at the end, but it's probably related to X not being >installed. Then let's use the XFree86 .LIBs and .Hs. The XFree86/2 DLLs are very compatible (even to Everblue). The only exception I heard of is Xaw, which got extended. Sebastian _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 2 ==========================** Date: Thu, 30 Jan 2003 08:48:18 -0600 (CST) From: "Maynard" Subject: Re: TIN tin built fine; to run, it must first acquire a fully qualified domain name; one way to provide this is via envar HOSTNAME My suspicion however is that it directly calls some routine which may have other sources for the information (i.e. some file in $ETC). It does not use \usr\bin\hostname.exe at startup. that done, run 'tin -h' or 'tin -V' successfully configuration files are created in $HOME/.tin it gets it's server location from $ETC/nntpserver which you have to create to be useful however, it needs to overcome a scree initilization/configuration problem: tin: Terminal must have clear to end-of-screen (cd) tin: Screen initialization failed -- Maynard _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 3 ==========================** Date: Thu, 30 Jan 2003 11:58:00 +0000 From: Patrick Ash Subject: Re: TIN While I am not an expert, here are a couple of things that I find necessary. the following environment variables need to be set, either globally from the config.sys or for each session. SET TERMINFO= SET HOME= SET TERM= SET TMP= all of the above need appropriate entries. Tin also seems to want to connect to 'news', so I have the following line in config.sys (for my newsserver) SET NNTPSERVER=news.comcast.giganews.com I also have news defined in my hosts file - 216.166.71.239 news.nj.comcast.giganews.com news You must use tin -r to connect to a remote newsserver, or rename the executable to rtin.exe. There is also a configuration file that is found in $home/tinrc that contains a number of optional values that can be changed to suit the user. Pat On Thu, 30 Jan 2003 08:48:18 -0600 (CST), Maynard wrote: >tin built fine; >to run, it must first acquire a fully qualified domain name; one way to >provide this is via envar HOSTNAME > >My suspicion however is that it directly calls some routine which may >have other sources for the information (i.e. some file in $ETC). It >does not use \usr\bin\hostname.exe at startup. > >that done, run 'tin -h' or 'tin -V' successfully > >configuration files are created in $HOME/.tin > >it gets it's server location from $ETC/nntpserver which you have to >create > >to be useful however, it needs to overcome a scree >initilization/configuration problem: > >tin: Terminal must have clear to end-of-screen (cd) >tin: Screen initialization failed -- Patrick Ash patash at comcast.net This OS/2 system uptime is 3 days, 21:16 hours and 13 seconds _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 4 ==========================** Date: Thu, 30 Jan 2003 12:02:53 -0600 (CST) From: "Maynard" Subject: Re: Building ZLIB John, >Building ZLIB fails because it expressly uses bash for the SHELL. > >What is the best way to sort out the problem? I'd like to see bash installed anyway ;-} -- Maynard _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 5 ==========================** Date: Thu, 30 Jan 2003 15:04:59 +0000 From: John Poltorak Subject: Re: TIN On Thu, Jan 30, 2003 at 08:48:18AM -0600, Maynard wrote: > tin built fine; > to run, it must first acquire a fully qualified domain name; one way to > provide this is via envar HOSTNAME > > My suspicion however is that it directly calls some routine which may > have other sources for the information (i.e. some file in $ETC). It > does not use \usr\bin\hostname.exe at startup. I'm always a little uncertain as to how apps derive the hostname of the localhost and suspect different apps have different methods. Perhaps we could set USE_HOSTS_FIRST=1... Maybe it tries a lookup via your RESOLV(2) file... > that done, run 'tin -h' or 'tin -V' successfully > > configuration files are created in $HOME/.tin > > it gets it's server location from $ETC/nntpserver which you have to > create Does anyone on this list run a news server? If so can we use it for testing TIN? If a public news serveris available we could use that. > to be useful however, it needs to overcome a scree > initilization/configuration problem: > > tin: Terminal must have clear to end-of-screen (cd) > tin: Screen initialization failed Is this a terminfo problem, I wonder... > -- Maynard -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 6 ==========================** Date: Thu, 30 Jan 2003 15:11:54 +0000 From: John Poltorak Subject: Re: GROFF progress On Wed, Jan 29, 2003 at 07:30:05PM -0600, Maynard wrote: > > Three sys3170's from > \UNIXOS2\WORKDIR\GROFF-CURRENT\SRC\ROFF\GROFF\GROFF.EXE Any idea why? Maybe some support files didn't get installed. GROFF is a fairly sizable package and one I'm not familiar with at all. I'll try and read up on it... > > > Total for: P:\usr\local\share\groff\*.* > 2,393,360 bytes in 319 files and 21 dirs > > > [P:\unixos2\lib]sh > # groff --version > GNU groff version 1.18.2 > > > 1/29/03 6:47p 323602 A---- P:\usr\local\bin\groff.exe > 1/29/03 6:48p 119626 A---- P:\usr\local\bin\groffer Maybe there are some sample documents which can be printed... -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 7 ==========================** Date: Thu, 30 Jan 2003 17:00:09 +0000 From: John Poltorak Subject: Building ZLIB Building ZLIB fails because it expressly uses bash for the SHELL. What is the best way to sort out the problem? Just change Makefile.os2 to use sh... ? -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 8 ==========================** Date: Thu, 30 Jan 2003 17:34:03 +0000 From: John Poltorak Subject: ZLIB I've managed to build ZLIB. How do I make sure it works properly? One thing I'd like to change is the value of 'prefix' which is hard coded in the Makefile as:- prefix=/usr/local How do I set it so that it is picked up from the environment? -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 9 ==========================** Date: Thu, 30 Jan 2003 18:43:38 +0000 From: John Poltorak Subject: BYACC build BYACC builds successfully, but they way it does so is not very elegant... Here's the build command:- at echo off cp %uxrt%\emx\bin\gcc.exe %uxrt%\emx\bin\cc.exe make "LDFLAGS=-Zexe" "LIBS=../../defs/byacc.def" cp -p yacc.exe %uxrt%\usr\bin cp -p yacc.1 %uxrt%\usr\share\man\man1 gzip -9 %uxrt%\usr\share\man\man1\yacc.1 rm %uxrt%\emx\bin\cc.exe BYACC is harded coded to compile using 'cc' rather than $CC which many other programs use. What I've done is temporarily copy gcc.exe as cc.exe and it seems to do the trick, but I'd prefer a different solution... Any suggestions? How about patching the Makefile so that is does use $CC? What else? Maybe having some sort of link program which launches gcc.exe... Could this achieve it:- ? at echo off echo #include ^>%2.c echo #include ^>>%2.c echo:>>%2.c echo int main(int argc, char *argv[])>>%2.c echo {>>%2.c echo argv[0] = "%1";>>%2.c echo return execvp(argv[0], argv) ? EXIT_FAILURE : EXIT_SUCCESS;>>%2.c echo }>>%2.c gcc %2.c -Zcrtdll -Zomf -Zlinker /pmtype:vio rm %2.c mv %2.exe %uxrt%\usr\bin %1 -o %2.exe %2.c If this was called lnk.cmd, it would be used somethink like:- lnk gcc cc and would produce a short stub program called cc.exe. -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 10 ==========================** Date: Thu, 30 Jan 2003 19:31:22 +0000 From: John Poltorak Subject: Re: Building ZLIB On Thu, Jan 30, 2003 at 12:02:53PM -0600, Maynard wrote: > John, > > >Building ZLIB fails because it expressly uses bash for the SHELL. > > > >What is the best way to sort out the problem? > > I'd like to see bash installed anyway ;-} To build it, you need the source, and then maybe some patches... You could always see whether it needed any patches by simply adding the correct entry to build.table which in this case would be:- bash;;ftp://ftp.gnu.org/pub/gnu/bash/bash-2.05.tar.gz;;;;;. then: build bash It probably won't work, but then I didn't expect it to ork with GROFF either... > -- Maynard -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 11 ==========================** Date: Thu, 30 Jan 2003 20:54:35 +0000 From: John Poltorak Subject: Building BIND I guess it's time to try building BIND... Anyone else interested? Do an RSYNC refresh and run:- build bind It doesn't get very far, only to this point:- checking printf format modifier for 64-bit integers... ll checking for chroot... no checking for linux/capability.h... no checking for sys/prctl.h... no checking for type rlim_t... no checking type of rlim_cur... configure: error: unable to determine sizeof rlim_cur But as my old friend Chairman Mao used to say, 'the longest march starts with the first step'... So, lets see what we are missing and where we can get it... -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 12 ==========================** Date: Thu, 30 Jan 2003 20:58:29 +0000 From: John Poltorak Subject: Re: ux2 posix On Thu, Jan 30, 2003 at 09:36:35PM +0100, Andreas Buening wrote: > Thomas Hoffmann wrote: > > > > [EMX and Posix/2 headers] > > > May I suggest that we try to move towards a replacement for the original > > EMX headers which will be ONE set of header files, resulting from > > amalgamating EMX and posix/2 headers. We then should start trying to > > build the ux2 stuff against this headers/lib, report the problems and > > improve the new standard headers step by step. > > Yes, 200% ACK! We need _one_ set of standard headers. Just create > a new directory "new", put EMX headers into "emx" and Posix/2 headers > into "posix2". Then start with a standard header, e.g. stddef.h, check > the "emx" and "posix2" version, decide what's required and put the > result into "new". After that continue with the next header. At least, > that's the basic idea. ;-) We don't even need that... We can simply have both sets of headers but in a particulat search sequence. This is what I'm currently doing with the build system, but we won't get very far until gcc is recompiled to incorporate -lcExt. > > Somebody should provide a > > starting point, > > In other words we need a maintainer for this. I guess, we won't > find a fulltime maintainer who does the job alone. So we need at > least one (or two) coordinators who check in the new patches/bug > fixes submitted by other people. > > > > possibly based on Stefan's recent release of p2alpha. > > There was a recent release? It is included in the build system. Have you tried using it yet? > > 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. -- John _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 13 ==========================** Date: Thu, 30 Jan 2003 21:36:35 +0100 From: Andreas Buening Subject: Re: ux2 posix Thomas Hoffmann wrote: > [EMX and Posix/2 headers] > May I suggest that we try to move towards a replacement for the original > EMX headers which will be ONE set of header files, resulting from > amalgamating EMX and posix/2 headers. We then should start trying to > build the ux2 stuff against this headers/lib, report the problems and > improve the new standard headers step by step. Yes, 200% ACK! We need _one_ set of standard headers. Just create a new directory "new", put EMX headers into "emx" and Posix/2 headers into "posix2". Then start with a standard header, e.g. stddef.h, check the "emx" and "posix2" version, decide what's required and put the result into "new". After that continue with the next header. At least, that's the basic idea. ;-) > Somebody should provide a > starting point, In other words we need a maintainer for this. I guess, we won't find a fulltime maintainer who does the job alone. So we need at least one (or two) coordinators who check in the new patches/bug fixes submitted by other people. > possibly based on Stefan's recent release of p2alpha. There was a recent release? 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 powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 14 ==========================** Date: Thu, 30 Jan 2003 21:51:50 +0100 From: Thomas Hoffmann Subject: Re: ux2 posix John Poltorak wrote: > Should DMAKE be included in UnixOS/2 ? > Oh no! Make is one of the few programs for which we have a current port AND a responsive maintainer. Do not unearth such relicts of software history. It's enough that there ist still NMAKE around ... Thomas. _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs