From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Wed, 26 Jun 2002 04:28:47 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 254 ************************************************** Tuesday 25 June 2002 Number 254 ************************************************** Subjects for today 1 Re: Test for executable extensions in Autoconf : Andreas Buening 2 Re: Building SED using new Autoconf : Andreas Buening 3 Re: unixos2 packages : Adrian Gschwend" 4 Makeflags : John Poltorak 5 Re: unixos2 packages : John Poltorak 6 Re: unixos2 packages : John Poltorak 7 Re: unixos2 packages : Holger Veit 8 Building Perl with VisualAge? : Edwin =?iso-8859-1?Q?G=FCnthner?= 9 Re: latest pearl : Edwin =?iso-8859-1?Q?G=FCnthner?= 10 Re: unixos2 packages : Adrian Gschwend" 11 Re: Makeflags : csaba.raduly at sophos.com 12 Re: unixos2 packages : Adrian Gschwend" 13 Re: unixos2 packages : John Poltorak 14 Re: unixos2 packages : Brian Havard" 15 Re: Building Perl with VisualAge? : James Cannon 16 Re: unixos2 packages : Holger Veit 17 Re: M4 build problem with texinfo : Thomas E. Dickey" 18 Re: unixos2 packages : Adrian Gschwend" 19 Re: Makeflags : John Poltorak 20 Re: UnixOS/2 environment : Lyn St George" 21 Re: Makeflags : csaba.raduly at sophos.com 22 Re: Building Perl with VisualAge? : Henry Sobotka 23 Re: UnixOS/2 environment : John Poltorak 24 Re: latest pearl : John Poltorak 25 latest pearl : Michel Such" 26 Re: ssh in X (was: Re:Emacs & X-Export) : Stefan Neis 27 Re: latest pearl : Michel Such" 28 Re: Patch -p : csaba.raduly at sophos.com 29 Re: Makeflags : John Poltorak 30 Re: unixos2 packages : Stefan Neis 31 Re: ssh in X (was: Re:Emacs & X-Export) : Adrian Gschwend" 32 Re: M4 build problem with texinfo : John Poltorak 33 Perl: os2/Changes : John Poltorak 34 Re: UnixOS/2 environment : Thomas Dickey 35 Re: ssh in X (was: Re:Emacs & X-Export) : Stefan Neis 36 Re: M4 build problem with texinfo : Stefan Neis 37 Re: unixos2 packages : Brian Havard" 38 Re: Makeflags : csaba.raduly at sophos.com 39 Re: Makeflags : Stefan Neis 40 Re: UnixOS/2 environment : Stefan Neis 41 Re: Building Perl with VisualAge? : csaba.raduly at sophos.com 42 make 3.79.1 and (gettext-0_10_39-r2-bin.zip) : Michel SUCH" 43 Re: unixos2 packages : Brian Havard" 44 Re: make 3.79.1 and (gettext-0_10_39-r2-bin.zip) : Michel SUCH" 45 Re: latest pearl : Holger Veit 46 Re: UnixOS/2 environment : Lyn St George" 47 Re: M4 build problem with texinfo : John Poltorak 48 Re: building automake 1.6.2 : John Poltorak 49 Perl: finding a DLL : John Poltorak 50 building automake 1.6.2 : Michel SUCH" 51 Re: UnixOS/2 environment : Lyn St George" 52 Re: UnixOS/2 environment : Lyn St George" 53 Re: building automake 1.6.2 : Michel SUCH" 54 Re: %UNIXROOT% : Thomas Hoffmann **= Email 1 ==========================** Date: Wed, 26 Jun 2002 00:35:42 +0200 From: Andreas Buening Subject: Re: Test for executable extensions in Autoconf John Poltorak wrote: > > I've noticed that Configure warns that ac_executable_extensions not set, > even though I set it through CONFIG.SITE. > > Could this test be moved until after CONFIG.SITE is processed? Sure. 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 Redmond where the Shadows lie. **= Email 2 ==========================** Date: Wed, 26 Jun 2002 00:38:29 +0200 From: Andreas Buening Subject: Re: Building SED using new Autoconf John Poltorak wrote: > > On Mon, Jun 24, 2002 at 08:41:47PM +0200, Andreas Buening wrote: > > John Poltorak wrote: > > > > > > In an attempt to rebuild as many apps from scatch as possible using the > > > new Autoconf, I thought I would start with SED. > > > > > > Do the instructions in README.OS2 of the SED archive:- > > > > > > http://hobbes.nmsu.edu/pub/os2/util/file/sed-3_02-r2.zip > > > > > > still apply, or are any modifications necessary? > > > > Okay, to answer your question I've just tried. ;-) > > If you only run autoconf, no problem. If you want to run > > automake you also need to run aclocal, but this overwrites > > the support for external regex (which is my fault, but > > can be corrected by a simple copy&paste). > > Ah, and you should use "automake -i" otherwise you will > > have to update some outdated help scripts (you will get > > some warnings anyway). ;-) > > Basically I want to build SED using:- > > tar zxf GNU_source > patch < your_ patches > autoconf > configure > make This should work. However, I recommend the already patched package. > but I guess a number of auxilliary files also need updating as well, but > I'm not sure of the exact sequence. Also when patching, should the patches > for aclocal.m4 and configure.in be included, or are they taken care of by > running aclocal and automake? > > If I run things just as above I get these two sets of errors:- > > configure.in:50: warning: AC_COMPILE_IFELSE was called before AC_AIX > configure.in:50: warning: AC_RUN_IFELSE was called before AC_AIX > configure.in:107: warning: AC_ARG_PROGRAM invoked multiple times > configure.in:64: error: do not use LIBOBJS directly, use AC_LIBOBJ (see > section `AC_LIBOBJ vs. LIBOBJS' Warnings. Simply ignore. Newer autoconf versions warn about everything. > > ... > > config.status: creating config.h > config.status: executing default-1 commands > cd . && automake --gnu --include-deps Makefile > configure.in:5: your implementation of AM_INIT_AUTOMAKE comes from an > configure.in:5: old Automake version. You should recreate aclocal.m4 > configure.in:5: with aclocal and run automake again. > make: *** [Makefile.in] Error 1 > cd . \ > && CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status > ./config.status[243]: >&5 : bad file descriptor > config.status: WARNING: ac_executable_extensions not set, assuming .exe > config.status: creating Makefile > config.status: executing default-1 commands > Making install in djgpp > make[1]: Entering directory `C:/unixos2/workdir/sed-3.02/djgpp' > cd .. && automake --gnu --include-deps djgpp/Makefile > configure.in:5: your implementation of AM_INIT_AUTOMAKE comes from an > configure.in:5: old Automake version. You should recreate aclocal.m4 > configure.in:5: with aclocal and run automake again. > make[1]: *** [Makefile.in] Error 1 > make[1]: Leaving directory `C:/unixos2/workdir/sed-3.02/djgpp' > make: *** [install-recursive] Error 1 The original sed package is _really_ old. You may have to rerun a newer automake version. (the patched package has already been updated with automake 1.4p5) Therefore I cannot say what _exactly_ you have to do if I don't know _exactly_ which versions were used for the package you want to update, and which version of which one of the auto-tools you want to use with which option. (what a sentence! ;-) ) Okay, to make it short: if you want to update the config files to the latest automake then you have also to update the help script to the latest version. Which one? If you get a message "bla is too old" or "../config/blurb" not found then you have to update bla or blurb. One comment about aclocal: it's a script that takes _all_ *.m4 files it can find (and some other you need) and puts them into aclocal.m4. If some of the required m4 macros are NOT in the source package (which is the case for sed) then you'll loose those macros if you rerun aclocal. The reason is that a lot of maintainers seem to have their own philosophy where aclocal should get its input from. Sometimes you have to use a path ("aclocal -I m4"), sometimes you have to have those macros somewhere in your build environment, sometimes something else is expected. In the case of sed you have to save the regex macros (from aclocal.m4) somewhere (into acinclude.m4) because they're not part of the source package. Then you can rerun and update everything. One additional comment: Be careful with putting auto* into a standard build scripts. It's a tool for developers only and it may require adjustments (like updating some help files) by hand. One version may require an update of xyz while another may not. New versions may introduce new help scripts which would cause a static build script to fail. If you need a new help script you can find it somewhere in the autoconf/automake package itself but this requires that a human being reads those messages and reacts accordingly. automake 1.6.2 compared to automake 1.4 requires an additional help script (unlike you disable this feature _by_ _hand_) while autoconf 2.53 does not need another script compared to autoconf 2.50. Another thing: If you keep patient for another week I can update some of the packages because I know where to find which macros/files/whatever for those packages if I get a "blurb/bla is missing" message. 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 Redmond where the Shadows lie. **= Email 3 ==========================** Date: Wed, 26 Jun 2002 08:40:41 +0200 (CDT) From: "Adrian Gschwend" Subject: Re: unixos2 packages On Wed, 26 Jun 2002 11:44:34 +1000 (EST), Brian Havard wrote: >I've also got a patch for building it with Watcom C++ but I guess that's >less likely to be of interest here :) hmm wouldn't say that :-), do you plan to compile apache 2.0 with watcom in a longer term? cu Adrian -- Adrian Gschwend at OS/2 Netlabs ICQ: 22419590 ktk at netlabs.org ------- The OS/2 OpenSource Project: http://www.netlabs.org **= Email 4 ==========================** Date: Wed, 26 Jun 2002 09:03:37 +0100 From: John Poltorak Subject: Makeflags Is there any way I can take advantage of $MAKEFLAGS to convert?:- make AR=emxomfar to:- make I don't want to hardcode 'AR=emxomfar' on the make command line. Do I have any alternatives? -- John **= Email 5 ==========================** Date: Wed, 26 Jun 2002 09:12:53 +0100 From: John Poltorak Subject: Re: unixos2 packages On Wed, Jun 26, 2002 at 05:53:52PM +1000, Brian Havard wrote: > On Wed, 26 Jun 2002 08:40:41 +0200 (CDT), Adrian Gschwend wrote: > > >On Wed, 26 Jun 2002 11:44:34 +1000 (EST), Brian Havard wrote: > > > >>I've also got a patch for building it with Watcom C++ but I guess that's > >>less likely to be of interest here :) > > > >hmm wouldn't say that :-), do you plan to compile apache 2.0 with > >watcom in a longer term? > > I've thought about it but probably not as it would make a lot of trouble > with modules (say PHP) built by gcc. It would also be very dificult, if not > impossible, to get the configure script to work with Watcom as much of the > OS/2 stuff in autoconf assumes emx gcc. The Autoconf maintainers say that there is no dependency on gcc, and we can amend any references to emx to be more generic if necessary... It would be nice to have OpenWatcom as a build option in the future, although I don't think it can be used just now, because it doesn't use POSIX standard compiler flags. However, I think we should look at what would need changing in the build environment to accomodate OpenWatcom. > -- > ______________________________________________________________________________ > | Brian Havard | "He is not the messiah! | > | brianh at kheldar.apana.org.au | He's a very naughty boy!" - Life of Brian | > ------------------------------------------------------------------------------ -- John **= Email 6 ==========================** Date: Wed, 26 Jun 2002 09:31:39 +0100 From: John Poltorak Subject: Re: unixos2 packages On Wed, Jun 26, 2002 at 11:44:34AM +1000, Brian Havard wrote: > BTW, I have a patch for 0.9.7 that adds support for building OS/2 DLLs > instead of static libraries which may be of use for building a unixos2 > package. If anyone's interested I can put it up on my "Building OpenSSL" > page. Yes, please. > I've also got a patch for building it with Watcom C++ but I guess that's > less likely to be of interest here :) I think such interest is likely to grow quite a lot over the next year. > -- > ______________________________________________________________________________ > | Brian Havard | "He is not the messiah! | > | brianh at kheldar.apana.org.au | He's a very naughty boy!" - Life of Brian | > ------------------------------------------------------------------------------ -- John **= Email 7 ==========================** Date: Wed, 26 Jun 2002 09:39:20 +0200 From: Holger Veit Subject: Re: unixos2 packages On Tue, Jun 25, 2002 at 10:46:02PM +0400, nick wrote: > On Tue, 25 Jun 2002 11:26:40 +0200 (CDT), Adrian Gschwend wrote: > > >>openssh port is not completed yet, i do want to send only the final diffs for its maintainers. > > > >great! hope they accept it, OpenSSH people got another problem right > >now (root exploit which is not yet public and no fix so far)... > > > > Thus os/2 is single user system, each user is the root here ;) So, we can ignore this exploit ;) > Faithfully Yours, Nick For now, yes... Holger -- Please update your tables to my new e-mail address: holger.veit$ais.fhg.de (replace the '$' with ' at ' -- spam-protection) **= Email 8 ==========================** Date: Wed, 26 Jun 2002 10:42:01 -0400 From: Edwin =?iso-8859-1?Q?G=FCnthner?= Subject: Building Perl with VisualAge? Hi there, just wondering: has anybody ever dared/tried to build Perl on OS/2 with a compiler that was not gcc or pgcc? regards, eg **= Email 9 ==========================** Date: Wed, 26 Jun 2002 10:49:53 -0400 From: Edwin =?iso-8859-1?Q?G=FCnthner?= Subject: Re: latest pearl Hi, John pointed out this ZIP last week: ftp://borneo.gmd.de/pub/misc/XFree86OS2/alpha/emxtree.zip It is about 64 MB in size. Maybe I can use this to repeat my question from yesterday: what exactly is necessary to setup this ZIP file? Just unzipping it and then adding the usual EMX variables to config.sys? regards, eg **= Email 10 ==========================** Date: Wed, 26 Jun 2002 11:20:03 +0200 (CDT) From: "Adrian Gschwend" Subject: Re: unixos2 packages On Wed, 26 Jun 2002 17:53:52 +1000 (EST), Brian Havard wrote: >I've thought about it but probably not as it would make a lot of trouble >with modules (say PHP) built by gcc. It would also be very dificult, if not >impossible, to get the configure script to work with Watcom as much of the >OS/2 stuff in autoconf assumes emx gcc. well we have a VAC version of PHP, I use it with IBM's apache because I had too many problems on netlabs.org with the EMX version unfortunately. Knut compiled it and it's somewhere in Netlabs CVS, if you are interested in it I could point you to the source. I didn't try the V2 yet but I definitely will. But if you run into troubles I'm quite sure that Knut and other people at netlabs would support you to get a VAC or Watcom version of Apache 2.0. But well, when LIBEMU is available we shouldn't have that much problems anymore with EMX stuff. If you would need some support let me know cu Adrian -- Adrian Gschwend at OS/2 Netlabs ICQ: 22419590 ktk at netlabs.org ------- The OS/2 OpenSource Project: http://www.netlabs.org **= Email 11 ==========================** Date: Wed, 26 Jun 2002 11:22:17 +0100 From: csaba.raduly at sophos.com Subject: Re: Makeflags On 26/06/2002 09:03:37 owner-os2-unix wrote: >Is there any way I can take advantage of $MAKEFLAGS to convert?:- > >make AR=emxomfar > >to:- > >make > > >I don't want to hardcode 'AR=emxomfar' on the make command line. Do I have >any alternatives? > Setting AR=emxomfar in the environment, if possible: set AR=emxomfar make -- Csaba Ráduly, Software Engineer Sophos Anti-Virus email: csaba.raduly at sophos.com http://www.sophos.com US Support: +1 888 SOPHOS 9 UK Support: +44 1235 559933 **= Email 12 ==========================** Date: Wed, 26 Jun 2002 11:32:54 +0200 (CDT) From: "Adrian Gschwend" Subject: Re: unixos2 packages On Wed, 26 Jun 2002 09:39:20 +0200, Holger Veit wrote: >> Thus os/2 is single user system, each user is the root here ;) So, we can ignore this exploit ;) >> Faithfully Yours, Nick > >For now, yes... :-)) Holger did you see the question about config-files of ssh, should they be in %UNIXROOT%/etc dir or %UNIXROOT%/etc/ssh? On my linux system it's in /etc/ssh cu Adrian -- Adrian Gschwend at OS/2 Netlabs ICQ: 22419590 ktk at netlabs.org ------- The OS/2 OpenSource Project: http://www.netlabs.org **= Email 13 ==========================** Date: Wed, 26 Jun 2002 11:33:57 +0100 From: John Poltorak Subject: Re: unixos2 packages On Wed, Jun 26, 2002 at 12:18:05PM +0200, Adrian Gschwend wrote: > On Wed, 26 Jun 2002 12:01:59 +0200, Holger Veit wrote: > > >are easily identifiable. In order to keep /etc clean, I would personally > >prefer them to move into an /etc/ssh directory. But this is not mandated > >by some FHS rule. So time for a decision - make it once any way and then > >keep that structure. > > I would go for /etc/ssh as well, looks cleaner for me. Other opinions? I agree with that, although some apps seem to require a cfg file to be in /etc, but in such cases as in named.conf any auxilliary config files should go into a subdirectory of /etc. I already do this with sendmail so that ALIASES, SPAMLIST etc go in /etc/sendmail although sendmail.cf goes in /etc. > cu > > Adrian > > > -- > Adrian Gschwend > at OS/2 Netlabs > > ICQ: 22419590 > ktk at netlabs.org > ------- > The OS/2 OpenSource Project: > http://www.netlabs.org -- John **= Email 14 ==========================** Date: Wed, 26 Jun 2002 11:44:34 +1000 (EST) From: "Brian Havard" Subject: Re: unixos2 packages On Tue, 25 Jun 2002 16:22:00 +0200 (CEST), Stefan Neis wrote: >On Tue, 25 Jun 2002, Brian Havard wrote: >> >> Who me? I supplied a patch for 0.9.6 which some people have used. >> 0.9.7 (currently in beta) will build OOTB after some patches of mine were >> committed. > >I downloaded some snapshot of 0.9.7 (to check AES) some time ago and it >built just nicely on OS/2 and everything else. >So if you want something for OS/2, I'd suggest to forget about >openssl-(engine-)0.9.6d and to take openssl-0.9.7-beta2. >Note however, that it's not using the "configure; make; make install" >way of building. True, openssl does not use autoconf even for unix. The build instructions are in INSTALL.OS2 which is in the root directory of the source tree. BTW, I have a patch for 0.9.7 that adds support for building OS/2 DLLs instead of static libraries which may be of use for building a unixos2 package. If anyone's interested I can put it up on my "Building OpenSSL" page. I've also got a patch for building it with Watcom C++ but I guess that's less likely to be of interest here :) -- ______________________________________________________________________________ | Brian Havard | "He is not the messiah! | | brianh at kheldar.apana.org.au | He's a very naughty boy!" - Life of Brian | ------------------------------------------------------------------------------ **= Email 15 ==========================** Date: Wed, 26 Jun 2002 11:55:15 -0700 (PDT) From: James Cannon Subject: Re: Building Perl with VisualAge? Isn't VA at the end of it's road? It seems pointless to put so much effort in a product that IBM isn't supportting. Meanwhile on the GCC front, developement continues ... --- Henry Sobotka wrote: > Edwin Günthner wrote: > > > > just wondering: has anybody ever dared/tried to > build > > Perl on OS/2 with a compiler that was not gcc or > pgcc? > > It's doable but a fair amount of work, as it would > require not only > setting up the build process for VA, but also fixing > the source to > accommodate IBM C library idiosyncracies and > limitations (including no > fork()). > > h~ > ===== Sincerely, James Cannon Using OS/2 Warp in the beautiful Wine Country of Northern California! __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com **= Email 16 ==========================** Date: Wed, 26 Jun 2002 12:01:59 +0200 From: Holger Veit Subject: Re: unixos2 packages On Wed, Jun 26, 2002 at 11:32:54AM +0200, Adrian Gschwend wrote: > On Wed, 26 Jun 2002 09:39:20 +0200, Holger Veit wrote: > > >> Thus os/2 is single user system, each user is the root here ;) So, we can ignore this exploit ;) > >> Faithfully Yours, Nick > > > >For now, yes... > > :-)) > > Holger did you see the question about config-files of ssh, should they > be in %UNIXROOT%/etc dir or %UNIXROOT%/etc/ssh? > > On my linux system it's in /etc/ssh Yes, I have seen them in /etc/ssh as well as in /etc on different systems. It is not clear from FHS how to proceed there. Traditionally, /etc is the home of configuration files, but this led to the effect that /etc became overcrowded with files that noone really knows where they actually belong to. This is why meanwhile sendmail and YP typically use subdirectories like /etc/mail or /etc/yp (often also /var/yp, but this is a bad Solaris anachronism) to have everything in one place. (With sendmail, the problem is that it then additionally scatter symlinks back into /etc for compatibility. With ssh, the files themselves have names like 'ssh_*' or 'sshd_*', so they are easily identifiable. In order to keep /etc clean, I would personally prefer them to move into an /etc/ssh directory. But this is not mandated by some FHS rule. So time for a decision - make it once any way and then keep that structure. Holger -- Please update your tables to my new e-mail address: holger.veit$ais.fhg.de (replace the '$' with ' at ' -- spam-protection) **= Email 17 ==========================** Date: Wed, 26 Jun 2002 12:10:59 -0400 (EDT) From: "Thomas E. Dickey" Subject: Re: M4 build problem with texinfo On Wed, 26 Jun 2002, Stefan Neis wrote: > On Tue, 25 Jun 2002, Thomas Dickey wrote: > > > On Tue, Jun 25, 2002 at 10:05:45PM +0100, John Poltorak wrote: > > > > > > Whilst building M4, I get the following error when creating the texinfo > > > docs:- > > > > I see stuff like this when someone's distributed a texinfo file that's > > newer than the texinfo executables (using features that weren't recognized > > by the older program). > > Maybe this time it's rather the other way round? texinfo being way to new > for M4 docs and having acquired a backward incompatible change over the > years? It seems unlikely that anybody could have a texinfo executable > that's older than the latest M4 distribution ... I suppose that's more likely. It's been a few years since I needed to build m4 (new/updated platforms either bundle m4, as in Linux, or I've no use for it, as on M$'s win32 stuff). -- T.E.Dickey http://invisible-island.net ftp://invisible-island.net **= Email 18 ==========================** Date: Wed, 26 Jun 2002 12:18:05 +0200 (CDT) From: "Adrian Gschwend" Subject: Re: unixos2 packages On Wed, 26 Jun 2002 12:01:59 +0200, Holger Veit wrote: >are easily identifiable. In order to keep /etc clean, I would personally >prefer them to move into an /etc/ssh directory. But this is not mandated >by some FHS rule. So time for a decision - make it once any way and then >keep that structure. I would go for /etc/ssh as well, looks cleaner for me. Other opinions? cu Adrian -- Adrian Gschwend at OS/2 Netlabs ICQ: 22419590 ktk at netlabs.org ------- The OS/2 OpenSource Project: http://www.netlabs.org **= Email 19 ==========================** Date: Wed, 26 Jun 2002 12:21:13 +0100 From: John Poltorak Subject: Re: Makeflags On Wed, Jun 26, 2002 at 11:22:17AM +0100, csaba.raduly at sophos.com wrote: > > On 26/06/2002 09:03:37 owner-os2-unix wrote: > > >Is there any way I can take advantage of $MAKEFLAGS to convert?:- > > > >make AR=emxomfar > > > >to:- > > > >make > > > > > >I don't want to hardcode 'AR=emxomfar' on the make command line. Do I have > >any alternatives? > > > > Setting AR=emxomfar in the environment, if possible: > > set AR=emxomfar > make Thanks for the suggestion, but I couldn't get it to work. I had this in a shell script:- export AR=emxomfar make but Make failed with 'LINK386 : invalid library' It does work OK when I have this:- make AR=emxomfar I guess I need to check that the environment is actually getting set correctly... -- John **= Email 20 ==========================** Date: Wed, 26 Jun 2002 12:27:18 +0000 From: "Lyn St George" Subject: Re: UnixOS/2 environment On Mon, 24 Jun 2002 14:49:32 +0100, John Poltorak wrote: > >If you find such an environment, please feel free to tell me about it :-)... Having now completely rebuilt EMX and GNU, I have one such list. Note that this lot will build Apache or Perl 5.6.1, but will not build Perl 5.8.0. EMX - 0.9d, fix 04, pgcc-2.95. Nothing else in it. kept in \emx\foo GNU: (kept in \usr\foo) file utils 3.16 shell utils 2.0 text utils 2.0 find 4.1 (1998) bison 1.28 byacc 1.0 flex 2.5.4 grep 2.4 make 3.79.1 patch 2.5 sed 3.02.80 gettext 0.11.1 file 333 bash 2.04 ksh/sh either Brian Harvard's pdksh-5.2.13, or Ilya Z's 2 releases of pdksh-5.2.14 (plus crypt, openssl, other non-base things) If you see anything missing here, please tell me - Cheers Lyn St George +--------------------------------------------------------------------------------- + http://www.zolotek.net .. eCommerce hosting, consulting + http://www.os2docs.org .. some 'How To' stuff ... +---------------------------------------------------------------------------------- **= Email 21 ==========================** Date: Wed, 26 Jun 2002 12:47:24 +0100 From: csaba.raduly at sophos.com Subject: Re: Makeflags On 26/06/2002 12:21:13 owner-os2-unix wrote: [snip] > >export AR=emxomfar >make > >but Make failed with 'LINK386 : invalid library' > >It does work OK when I have this:- > >make AR=emxomfar > Add the following to the makefile: say: at echo AR is now '$(AR)' then do export AR=emxomfar make say -- Csaba Ráduly, Software Engineer Sophos Anti-Virus email: csaba.raduly at sophos.com http://www.sophos.com US Support: +1 888 SOPHOS 9 UK Support: +44 1235 559933 **= Email 22 ==========================** Date: Wed, 26 Jun 2002 12:51:40 -0400 From: Henry Sobotka Subject: Re: Building Perl with VisualAge? Edwin Günthner wrote: > > just wondering: has anybody ever dared/tried to build > Perl on OS/2 with a compiler that was not gcc or pgcc? It's doable but a fair amount of work, as it would require not only setting up the build process for VA, but also fixing the source to accommodate IBM C library idiosyncracies and limitations (including no fork()). h~ **= Email 23 ==========================** Date: Wed, 26 Jun 2002 13:44:58 +0100 From: John Poltorak Subject: Re: UnixOS/2 environment On Wed, Jun 26, 2002 at 12:27:18PM +0000, Lyn St George wrote: > On Mon, 24 Jun 2002 14:49:32 +0100, John Poltorak wrote: > > > >If you find such an environment, please feel free to tell me about it :-)... > > Having now completely rebuilt EMX and GNU, I have one > such list. Note that this lot will build Apache or Perl 5.6.1, but > will not build Perl 5.8.0. > > EMX - 0.9d, fix 04, pgcc-2.95. Nothing else in it. > kept in \emx\foo > > GNU: (kept in \usr\foo) > file utils 3.16 > shell utils 2.0 > text utils 2.0 > find 4.1 (1998) > bison 1.28 > byacc 1.0 > flex 2.5.4 > grep 2.4 grep 2.4.2 > make 3.79.1 > patch 2.5 patch 2.5.4 > sed 3.02.80 > gettext 0.11.1 > file 333 file 3.37 > bash 2.04 Where is this from? > ksh/sh either Brian Harvard's pdksh-5.2.13, or > Ilya Z's 2 releases of pdksh-5.2.14 Can you try using IlyaZ's latest? ...unless you have a problem with it. http://www.math.ohio-state.edu/~ilya/software/os2/pdksh-5.2.14-bin-2.zip It would be good to standardise on a shell. > (plus crypt, openssl, other non-base things) crypt is something I need to incorporate. Where do I get it from? > > If you see anything missing here, please tell me awk 3.1.0 also gzip,tar,bzip2,less,m4 Most of these are in the A1 series in the UnixOS/2 distro, mainly in the BIN.ZIP package. > > - > Cheers > Lyn St George > +--------------------------------------------------------------------------------- > + http://www.zolotek.net .. eCommerce hosting, consulting > + http://www.os2docs.org .. some 'How To' stuff ... > +---------------------------------------------------------------------------------- > -- John **= Email 24 ==========================** Date: Wed, 26 Jun 2002 13:51:48 +0100 From: John Poltorak Subject: Re: latest pearl On Wed, Jun 26, 2002 at 02:34:43PM +0100, Michel Such wrote: > Where can I find this The most recent Perl distribution for OS/2 is here:- http://hobbes.nmsu.edu/pub/os2/dev/perl/perl-5.7.2.zip > and, more generally, where can I find latest apps > in the unixos/2 site in which I must admit I am lost! The directory structure has been completely moved for some reason, so I don't know where anything is any more and all the links I spent months setting up no longer work either. > Michel SUCH - Team OS/2 France - msuch at free.fr > ICQ # 51654489 > -- John **= Email 25 ==========================** Date: Wed, 26 Jun 2002 14:34:43 +0100 (CET) From: "Michel Such" Subject: latest pearl Where can I find this and, more generally, where can I find latest apps in the unixos/2 site in which I must admit I am lost! Michel SUCH - Team OS/2 France - msuch at free.fr ICQ # 51654489 **= Email 26 ==========================** Date: Wed, 26 Jun 2002 15:59:43 +0200 (CEST) From: Stefan Neis Subject: Re: ssh in X (was: Re:Emacs & X-Export) On Tue, 25 Jun 2002, Adrian Gschwend wrote: > well the problem is that ssh does simply *nothing* in the terminal, it > does not even prompt for the password. I just checked what happens for me: "ssh my_solaris_box" opens an ssh session with X forwarding disabled "ssh -X my_solaris_box" does print a message about correct usage and does nothing - and it doesn't list a "-X" option, just "-x" for turning off X11 forwarding... HTH, Stefan **= Email 27 ==========================** Date: Wed, 26 Jun 2002 16:02:14 +0100 (CET) From: "Michel Such" Subject: Re: latest pearl Well, So, how can I get a full unixos/2 package with all package at coherent level (I do not hope ready to install). On Wed, 26 Jun 2002 13:51:48 +0100, John Poltorak wrote: >On Wed, Jun 26, 2002 at 02:34:43PM +0100, Michel Such wrote: >> Where can I find this > >The most recent Perl distribution for OS/2 is here:- > >http://hobbes.nmsu.edu/pub/os2/dev/perl/perl-5.7.2.zip > >> and, more generally, where can I find latest apps >> in the unixos/2 site in which I must admit I am lost! > >The directory structure has been completely moved for some reason, so I >don't know where anything is any more and all the links I spent months >setting up no longer work either. > > >> Michel SUCH - Team OS/2 France - msuch at free.fr >> ICQ # 51654489 >> > > >-- >John > > > > Michel SUCH - Team OS/2 France - msuch at free.fr ICQ # 51654489 **= Email 28 ==========================** Date: Wed, 26 Jun 2002 16:09:55 +0100 From: csaba.raduly at sophos.com Subject: Re: Patch -p --0__=0FBBE170DFA3ED8A8f9e8a93df938690918c0FBBE170DFA3ED8A Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable On 24/06/2002 19:26:44 owner-os2-unix wrote: >On Mon, Jun 24, 2002 at 06:05:09PM +0100, csaba.raduly at sophos.com wrot= e: [snip] >Yes, I remember that - SLICEM.CMD - excellent utility! > Heh, I thought it was all mine :-) Took me some time to find it: I was searching for files with a .pl extension. Try this (renamed to .cmd, put it in the current dir *or* the path) (See attached file: diff_prefix.txt) -- Csaba R=E1duly, Software Engineer Sophos Anti= -Virus email: csaba.raduly at sophos.com http://www.sophos= .com US Support: +1 888 SOPHOS 9 UK Support: +44 1235 55= 9933= --0__=0FBBE170DFA3ED8A8f9e8a93df938690918c0FBBE170DFA3ED8A Content-type: application/octet-stream; name="=?iso-8859-1?Q?diff=5Fprefix.txt?=" Content-Disposition: attachment; filename="=?iso-8859-1?Q?diff=5Fprefix.txt?=" Content-transfer-encoding: base64 ZXh0cHJvYyBwZXJsIC13bFN4DQojIXBlcmwgLXdsU3gNCnVzZSBzdHJpY3Q7DQp1c2UgQ2FycDsN Cg0KbXkgQHBsdXNwbHVzcGx1czsNCm15IEBtaW51c21pbnVzbWludXM7DQoNCnN1YiBjb21tb25w cmVmaXgoQCkNCnsNCiAgICBteSAkcHJlZml4ID0gc2hpZnQgb3IgY29uZmVzcyAnTm8gYXJndW1l bnQgdG8gY29tbW9ucHJlZml4ICEnOw0KICAgIGZvcmVhY2ggbXkgJHMgKCBAXyApDQogICAgew0K ICAgICAgICBjaG9wICRwcmVmaXggd2hpbGUgaW5kZXgoICRzLCAkcHJlZml4ICkgPCAwOw0KICAg IH0NCiAgICAkcHJlZml4Ow0KfQ0KDQpzdWIgZGlyX2RlZXAoJCkNCnsNCiAgICAkXyA9IHNoaWZ0 IG9yIGNvbmZlc3MgJ05vIGFyZ3VtZW50IHRvIGRpcl9kZWVwJzsNCiAgICBteSAkbGVuZ3RoID0g MDsNCiAgICArKyRsZW5ndGggd2hpbGUoIHMhXlteL1xcXStbL1xcXSEhICk7DQogICAgJGxlbmd0 aDsNCn0NCiAgICAgICAgICAgICAgICAgDQoNCndoaWxlKCA8PiApDQp7DQogICAgbmV4dCB1bmxl c3MgIyAvXihbKy1dezN9KSguKykkLzsNCiAgICAgICAgbXkgKCRwLCR0KSA9IC9eKFwrXCtcK3wt LS0pICguKykkLzsNCiAgICANCiAgICAkdCA9fiBzIV5bYS16QS1aXTpbL1xcXSEhOw0KICAgIGlm KCAkcCBlcSAnLS0tJyApDQogICAgew0KICAgICAgICBwdXNoIEBtaW51c21pbnVzbWludXMsICR0 Ow0KICAgIH0NCiAgICBlbHNpZiggJHAgZXEgJysrKycgKQ0KICAgIHsNCiAgICAgICAgcHVzaCBA cGx1c3BsdXNwbHVzLCAkdDsNCiAgICB9DQogICAgZWxzZQ0KICAgIHsNCiAgICAgICAgZGllICJI dWggPyBgJF8nIjsNCiAgICB9DQogICAgDQp9DQoNCm15ICRwbHVzc2VzID0gQHBsdXNwbHVzcGx1 czsNCm15ICRtaW51c2VzID0gQG1pbnVzbWludXNtaW51czsNCg0KZGllICJObyAnKysrJyBvciAn LS0tJyBmb3VuZC4gTm90IGFuIHVuaWZpZWQgZGlmZiA/IiB1bmxlc3MgJHBsdXNzZXMgYW5kICRt aW51c2VzOw0Kd2FybiAiVW5lcXVhbCAoICskcGx1c3NlcyAtJG1pbnVzZXMgKSA/IEknbSBjb25m dXNlZC4iIGlmICRwbHVzc2VzICE9ICRtaW51c2VzOw0KDQpteSAkcGx1c19wcmVmaXggID0gY29t bW9ucHJlZml4IEBwbHVzcGx1c3BsdXM7DQpteSAkbWludXNfcHJlZml4ID0gY29tbW9ucHJlZml4 IEBtaW51c21pbnVzbWludXM7DQoNCiMgcHJpbnQgIiRwbHVzX3ByZWZpeFxuJG1pbnVzX3ByZWZp eCI7DQoNCm15ICRwbHVzX2RlZXAgPSBkaXJfZGVlcCAkcGx1c19wcmVmaXg7DQpteSAkbWludXNf ZGVlcCA9IGRpcl9kZWVwICRtaW51c19wcmVmaXg7DQoNCiNwcmludCAicmVjb21tZW5kIC1wICRw bHVzX2RlZXAsIEkgcmVwZWF0IC1wICRtaW51c19kZWVwIjsNCnByaW50ICJJZiB5b3UgYXJlIGlu IHRoZSBwcm9qZWN0IGJhc2UgZGlyZWN0b3J5LCB5b3Ugc2hvdWxkIHByb2JhYmx5IHVzZSAtcCAk cGx1c19kZWVwIjsNCnByaW50ICJJZiB5b3UgYXJlIGluIHRoZSBwYXJlbnQsIHVzZSBvbmUgbGVz cywgaS5lLiAtcCAiLCAkcGx1c19kZWVwIC0gMTsNCnByaW50ICJcbih0aGUgc291cmNlIGRpcnMg c3VnZ2VzdCAkbWludXNfZGVlcCwgb3Igb25lIGxlc3MpIjsNCiAgICANCg== --0__=0FBBE170DFA3ED8A8f9e8a93df938690918c0FBBE170DFA3ED8A-- **= Email 29 ==========================** Date: Wed, 26 Jun 2002 16:11:46 +0100 From: John Poltorak Subject: Re: Makeflags On Wed, Jun 26, 2002 at 12:47:24PM +0100, csaba.raduly at sophos.com wrote: > > On 26/06/2002 12:21:13 owner-os2-unix wrote: > > [snip] > > > >export AR=emxomfar > >make > > > >but Make failed with 'LINK386 : invalid library' > > > >It does work OK when I have this:- > > > >make AR=emxomfar > > > > Add the following to the makefile: > > say: > at echo AR is now '$(AR)' > > then do > > export AR=emxomfar > make say The way Make works must be a little strange. I don't it is enough to just set the envar $AR to emxomfar (ICBW), it appears to need the string 'AR=emxomfar' on the command line. I've managed to achieve what I want with this:- MAKEPARM="AR=emxomfar" make $MAKEPARM but it doesn't seem particularly elegent, although it does have the desired effect of building m4.exe. I still have no idea how this works or where it is necessary, and strangely enough I continue to get this error:- LINK386 : fatal error L1104: ..\lib\libm4.a : not valid library make[1]: *** [m4] Error 1 make[1]: Leaving directory `C:/unixos2/workdir/m4-1.4/src' make: *** [install] Error 1 end although it occurs after m4.exe has been created now. -- John **= Email 30 ==========================** Date: Wed, 26 Jun 2002 16:21:25 +0200 (CEST) From: Stefan Neis Subject: Re: unixos2 packages On Wed, 26 Jun 2002, Brian Havard wrote: > BTW, I have a patch for 0.9.7 that adds support for building OS/2 DLLs > instead of static libraries which may be of use for building a unixos2 > package. If anyone's interested I can put it up on my "Building OpenSSL" > page. Any chance to get the patch integrated into the official 0.9.7 release? Otherwise we'll likely see a number of incompatible DLL's being distributed within the months following the release as OpenSSL seems to be used more and more frequently... Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 31 ==========================** Date: Wed, 26 Jun 2002 16:23:56 +0200 (CDT) From: "Adrian Gschwend" Subject: Re: ssh in X (was: Re:Emacs & X-Export) On Wed, 26 Jun 2002 15:59:43 +0200 (CEST), Stefan Neis wrote: >"ssh my_solaris_box" opens an ssh session with X forwarding disabled >"ssh -X my_solaris_box" does print a message about correct usage and > does nothing - and it doesn't list a "-X" option, just "-x" for > turning off X11 forwarding... yes I guess you don't use OpenSSH 3.x, do you? The -X option is available in OpenSSH. Which window manager are you using? Must be a shell problem on my system cu Adrian -- Adrian Gschwend at OS/2 Netlabs ICQ: 22419590 ktk at netlabs.org ------- The OS/2 OpenSource Project: http://www.netlabs.org **= Email 32 ==========================** Date: Wed, 26 Jun 2002 17:08:16 +0100 From: John Poltorak Subject: Re: M4 build problem with texinfo On Wed, Jun 26, 2002 at 05:50:23PM +0200, Stefan Neis wrote: > On Tue, 25 Jun 2002, Thomas Dickey wrote: > > > On Tue, Jun 25, 2002 at 10:05:45PM +0100, John Poltorak wrote: > > > > > > Whilst building M4, I get the following error when creating the texinfo > > > docs:- > > > > I see stuff like this when someone's distributed a texinfo file that's > > newer than the texinfo executables (using features that weren't recognized > > by the older program). > > Maybe this time it's rather the other way round? texinfo being way to new > for M4 docs and having acquired a backward incompatible change over the > years? It seems unlikely that anybody could have a texinfo executable > that's older than the latest M4 distribution ... I guess that's possible, although I would expect makeinfo to be backwardly compatible with old texinfo files. I'll dig out an old copy and see if it makes any difference... If anyone has a copy of Linux installed, could you try building m4? I don't why it should work differently on Linux. > Regards, > Stefan > -- John **= Email 33 ==========================** Date: Wed, 26 Jun 2002 17:17:48 +0100 From: John Poltorak Subject: Perl: os2/Changes --FkOludkFz3jefP/C Content-Type: text/plain; charset=us-ascii I forwarding some new OS/2 patches which have just been submitted for Perl. Can anyone have a look though to see how significant any of them are? Are there any implications for building Perl? -- John --FkOludkFz3jefP/C Content-Type: message/rfc822 Received: from onion.perl.org by mail.eyup.org (IBM OS/2 SENDMAIL VERSION 2.03/2.0) id QAA624.27; Wed, 26 Jun 2002 16:54:37 +0100 Received: (qmail 28256 invoked by uid 1005); 26 Jun 2002 15:58:39 -0000 Mailing-List: contact perl5-porters-help at perl.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Delivered-To: mailing list perl5-porters at perl.org Received: (qmail 28233 invoked by uid 76); 26 Jun 2002 15:58:39 -0000 Received: from mathserv.math.ohio-state.edu (HELO mathserv.math.ohio-state.edu) (128.146.111.31) by onion.perl.org (qpsmtpd/0.07b) with SMTP; Wed Jun 26 15:58:39 2002 -0000 Received: from math.ohio-state.edu (math.ohio-state.edu [128.146.111.30]) by mathserv.math.ohio-state.edu (8.12.3/8.12.3) with ESMTP id g5QFs7rw030250 for ; Wed, 26 Jun 2002 11:54:07 -0400 Received: (from ilya at localhost) by math.ohio-state.edu (8.11.0/8.11.0) id g5QFs6406135 for perl5-porters at perl.org; Wed, 26 Jun 2002 11:54:06 -0400 (EDT) Date: Wed, 26 Jun 2002 11:54:06 -0400 From: Ilya Zakharevich To: Mailing list Perl5 Subject: [PATCH rc2] os2/Changes Message-ID: <20020626115406.A6091 at math.ohio-state.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-RAVMilter-Version: 8.3.2(snapshot 20020213) (mathserv) I analysed all the patches I sent to p5p during the last year, and (finally!) updated os2/Changes. Additionally, I corrected a misprint in a comment in os2/os2.c. Enjoy, Ilya *** ./os2/Changes~ Sat Jun 1 19:03:34 2002 --- ./os2/Changes Wed Jun 26 17:53:02 2002 *************** *** 335,341 **** A complete example of a mini-application added to OS2::REXX. README.os2 updated to reflect the current state of Perl. ! pre 5.6.2: aout build: kid bootstrap_* were not associated with XS. bldlevel did not contain enough info. extLibpath* was failing on the call of the second type. --- 335,341 ---- A complete example of a mini-application added to OS2::REXX. README.os2 updated to reflect the current state of Perl. ! pre 5.7.2: aout build: kid bootstrap_* were not associated with XS. bldlevel did not contain enough info. extLibpath* was failing on the call of the second type. *************** *** 371,373 **** --- 371,497 ---- window hierarchy inspection post a message to a window More robust getpriority() on older Warps. + + New C APIs for runtime loading of entry points from DLLs + (useful for entry points not present on older versions of + OS/2, or with DLLs not present on floppy-boot stripped down + setups): CallORD(), DeclFuncByORD(), DeclVoidFuncByORD(), + DeclOSFuncByORD(), DeclWinFuncByORD(), AssignFuncPByORD(). + + pre 5.7.3: + Testing with PERL_TEST_NOVREXX=1 in environment makes tests + noninteractive (VREXX test requires pressing a button on a dialog). + + New (ugly and voodooish) hack to work around a bug in EMX + runtime architecture: + + EMX.DLL is *not* initialized from its _DLL_InitTerm() + routine, but the initialization is postponed until + immediately before main() is called by the principal + executable (may be the initialization also happens during + InitTerm of -Zso -Zsys DLLs?). The only reason I can see is + to postpone the initialization until the "layout" structure + is available, so the type of the executable is known. + [Instead, one should have broken the initialization into two + steps, with no-layout-known initialization ASAP, and the + finishing touch done when "layout" is known.] + + It is due to this hack that -Zsys, -Zso etc. are needed so + often. + + If during initialization of the Perl runtime environment we + discover that EMX environment is not set up completely, this + can be because of either our DLL being called from an + uncompatible flavor of EMX executable, or from an + unrelated-to-EMX.DLL (e.g., -Zsys or compiled with a + different compiler) executable. In the first case only the + CRTL is not completely initialized, in the other case + EMX.DLL may be not initialized too. + + We detect which of these two situations takes place, then + explicitly call the initialization entry points of EMX.DLL + and of CRT. The large caveat is that the init-entry point + of EMX.DLL also moves the stack pointer (another defect of + EMX architecture, the init() and + set_exception_handlers_on_stack() entry points should have + been separated). Thus we need some inline-assembler to + compensate for this, and need to remove the installed + exception handler - it is useless anyway, since exception + handlers need to be on the stack. [This one is on the + stack, but will be overwritten on exit from the function.] + + We also install an extra hack to run our atexit() handlers + on termination of the process (since the principal + executable does not know about *this* CRTL, we need to do it + ourselves - and longjmp() out of the chain of exception + handlers at a proper moment :-(). + + The net result: Perl DLL can be now used with an arbitrary + application. PERLREXX DLL is provided which makes Perl usable + from any REXX-enabled application. + + New test targets added to test how well Perl DLL runs with + different flavors of executables (see all_harness etc). To + avoid waiting for the user button press, run with env + PERL_TEST_NOVREXX=1. + + Another hack: on init of Perl runtime environment, the + executable is tested for being an aout EMX executable. The + test is the same done by gdb, so although this test is very + voodoo, it should be pretty robust (the beginning of the + executable code - at 0x10000 - is tested for a known bit + pattern). The result is used to set $OS2::can_fork, which is + eventually used to set $Config::Config{can_fork}. + + REXX::eval_REXX() made reenterable. ADDRESS PERLEVAL + available for the run REXX code. PERLLASTERROR available. + + A .map file is created for the .dll. Now easier to debug the + failures which do not happen with a debugging executable. + + Duplicate libperl.lib as perl.lib etc. to make Embed happier. + + File::Spec better adjusted to OS/2 (still does not support aa:/dir/). + + New module OS::Process::Const with necessary constants for the + Perl calls which mimic OS/2 API calls. + + After at 14577: + $Config{pager} better (but needs work in the binary installer!). + + New API: OS2::dll_name([type], [\&sub]) + + New OS2::Process APIs: + + process_hwnd winTitle_set winTitle swTitle_set bothTitle_set + hWindowPos hWindowPos_set DesktopWindow + ActiveWindow_set + EnableWindow EnableWindowUpdate IsWindowEnabled + IsWindowVisible IsWindowShowing WindowPtr WindowULong + WindowUShort SetWindowBits SetWindowPtr + SetWindowULong + SetWindowUShort MPFROMSHORT MPVOID MPFROMCHAR + MPFROM2SHORT + MPFROMSH2CH MPFROMLONG + + OS::Process::Const symbols exportable from OS::Process too. + + OS::Process: prototypes on subroutines which do not naturally + take "vectors" as arguments (not backwards compatible!). + + New C API: SaveCroakWinError(), WinError_2_Perl_rc, + DeclWinFuncByORD_CACHE(), DeclWinFuncByORD_CACHE_survive(), + DeclWinFuncByORD_CACHE_resetError_survive(), + DeclWinFunc_CACHE(), DeclWinFunc_CACHE_resetError(), + DeclWinFunc_CACHE_survive(), + DeclWinFunc_CACHE_resetError_survive(); many new OS2 entry + points conveniently available via wrappers which will do the + necessary run-time dynalinking. + + After at 15047: + + makes PerlIO preserve the binary/text mode of filehandles + chosen by CRT library. (However, TTY handles still are not + clean, since switching them to TERMIO mode and back changes + the NL translation law at runtime, and PerlIO level does not + know this.) *** ./os2/os2.c~ Sat Jun 1 19:03:35 2002 --- ./os2/os2.c Wed Jun 26 17:04:25 2002 *************** *** 2468,2475 **** my_os_version() { static ULONG res; /* Cannot be on stack! */ ! /* Can't just call emx_init(), since it moves the stack pointer */ ! /* It also busts a lot of registers, so be extra careful */ __asm__( "pushf\n" "pusha\n" "call ___os_version\n" --- 2468,2475 ---- my_os_version() { static ULONG res; /* Cannot be on stack! */ ! /* Can't just call __os_version(), since it does not follow C ! calling convention: it busts a lot of registers, so be extra careful */ __asm__( "pushf\n" "pusha\n" "call ___os_version\n" --FkOludkFz3jefP/C-- **= Email 34 ==========================** Date: Wed, 26 Jun 2002 17:39:43 -0400 From: Thomas Dickey Subject: Re: UnixOS/2 environment On Wed, Jun 26, 2002 at 08:57:35PM +0000, Lyn St George wrote: > So as to hunt for headers, I've updated "which" to now search > for headers:) ftp://ftp.zolotek.net/os2/which-2.1.4_os2.zip can't read it. This is what I use (ymmv) http://invisible-island.net/conflict/ Usage: conflict [options] [list_of_files] Lists conflicts of executable files in current PATH. First instance in path (and those linked to it) are marked with "*", succeeding instances with "+" marks. Options are: -e name specify another environment variable than $PATH -p print pathnames only -r look for read-able files -t types look only for given file-types -v (verbose) show names found in each directory once: shows all directory names twice: shows all filenames thrice: shows trace of directory scanning -w look for write-able files -W number expand width of display by number of columns -x look for execut-able files (default) Also, C-preprocessor-style -I and -L options -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 35 ==========================** Date: Wed, 26 Jun 2002 17:45:24 +0200 (CEST) From: Stefan Neis Subject: Re: ssh in X (was: Re:Emacs & X-Export) On Wed, 26 Jun 2002, Adrian Gschwend wrote: > yes I guess you don't use OpenSSH 3.x, do you? Ah yes, you're right, thanks for clarifying why I did see a "-X" option under Linux but not under OS/2. ;-) > Which window manager are you using? Must be a > shell problem on my system Well, you could try to open an OS/2-window in PM and enter your "ssh -X whatever" and hopefully password and some commands there, maybe that will work around whatever problem you currently see. X windows from the remote box still should make it to your XFree86 screen. Switching around between XFree86 and PM is a bit annoying of course, but if it works that would give a hint at the real source of the problem (I suppose openssh has some problem with xterm or tty handling, that's a notorious problem with code that hasn't been ported with the idea of supporting both PM and XFree session in mind). For me, this works fine with ssh-1.2.30 (whatever that exactly is) and it works even better with HOB-X11. :-) Regards, Stefan **= Email 36 ==========================** Date: Wed, 26 Jun 2002 17:50:23 +0200 (CEST) From: Stefan Neis Subject: Re: M4 build problem with texinfo On Tue, 25 Jun 2002, Thomas Dickey wrote: > On Tue, Jun 25, 2002 at 10:05:45PM +0100, John Poltorak wrote: > > > > Whilst building M4, I get the following error when creating the texinfo > > docs:- > > I see stuff like this when someone's distributed a texinfo file that's > newer than the texinfo executables (using features that weren't recognized > by the older program). Maybe this time it's rather the other way round? texinfo being way to new for M4 docs and having acquired a backward incompatible change over the years? It seems unlikely that anybody could have a texinfo executable that's older than the latest M4 distribution ... Regards, Stefan **= Email 37 ==========================** Date: Wed, 26 Jun 2002 17:53:52 +1000 (EST) From: "Brian Havard" Subject: Re: unixos2 packages On Wed, 26 Jun 2002 08:40:41 +0200 (CDT), Adrian Gschwend wrote: >On Wed, 26 Jun 2002 11:44:34 +1000 (EST), Brian Havard wrote: > >>I've also got a patch for building it with Watcom C++ but I guess that's >>less likely to be of interest here :) > >hmm wouldn't say that :-), do you plan to compile apache 2.0 with >watcom in a longer term? I've thought about it but probably not as it would make a lot of trouble with modules (say PHP) built by gcc. It would also be very dificult, if not impossible, to get the configure script to work with Watcom as much of the OS/2 stuff in autoconf assumes emx gcc. -- ______________________________________________________________________________ | Brian Havard | "He is not the messiah! | | brianh at kheldar.apana.org.au | He's a very naughty boy!" - Life of Brian | ------------------------------------------------------------------------------ **= Email 38 ==========================** Date: Wed, 26 Jun 2002 17:59:19 +0100 From: csaba.raduly at sophos.com Subject: Re: Makeflags On 26/06/2002 17:03:04 owner-os2-unix wrote: >> with this:- >> >> MAKEPARM="AR=emxomfar" >> make $MAKEPARM >> >> but it doesn't seem particularly elegent, although it does have the >> desired effect of building m4.exe. >> >> I still have no idea how this works or where it is necessary, > >IIRC, make (at least GNUmake) is initialising AR,CC,CXX etc. from >hardcoded defaults, _not_ from the environment (unlike configure), >so you really need to pass different values via the command line. > When GNU make 3.74 is defining a variable and it's already defined, it checks to see if the new value is "stronger" than the existing one. If not, the variable is not changed. Default values ("hardcoded") are the weakest, so if a variable is defined from the environment, it wins against the default hardcoded values. Hence, any GNU make 3.74 or newer should use the environment value. [snip guess related to configure] Not every makefile is generated by ./configure :-) John, what happens if you add the following to the makefile: say: at echo AR is now '$(AR)' then do export AR=emxomfar make say -- Csaba Ráduly, Software Engineer Sophos Anti-Virus email: csaba.raduly at sophos.com http://www.sophos.com US Support: +1 888 SOPHOS 9 UK Support: +44 1235 559933 **= Email 39 ==========================** Date: Wed, 26 Jun 2002 18:03:04 +0200 (CEST) From: Stefan Neis Subject: Re: Makeflags > with this:- > > MAKEPARM="AR=emxomfar" > make $MAKEPARM > > but it doesn't seem particularly elegent, although it does have the > desired effect of building m4.exe. > > I still have no idea how this works or where it is necessary, IIRC, make (at least GNUmake) is initialising AR,CC,CXX etc. from hardcoded defaults, _not_ from the environment (unlike configure), so you really need to pass different values via the command line. The idea behind that behaviour (probably) is that you should set the relevant variables via running configure and want the makefile to be processed as is, without the environment (which you might change for running the next configure script) interfering with the rest of the build process... Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 40 ==========================** Date: Wed, 26 Jun 2002 18:12:32 +0200 (CEST) From: Stefan Neis Subject: Re: UnixOS/2 environment On Tue, 25 Jun 2002, Lyn St George wrote: > "In file included from perl.h:612, > from os2.c:30: > f:/emx/include/netinet/in.h:89: parse error before `u_long' > f:/usr/include/sys/socket.h:162: parse error before `u_short' > "os2.c: In function `file_type': > os2.c:583: `_emx_env' undeclared (first use in this function)" Sounds like some missing include to e.g. . As to why it is missing for you and apparently not for others, I'm lost. There's been some discussion about such a problem a few weeks ago, but I had the impression it was fixed in the latest release candidate for Perl-5.8.0. Regards, Stefan **= Email 41 ==========================** Date: Wed, 26 Jun 2002 18:25:54 +0100 From: csaba.raduly at sophos.com Subject: Re: Building Perl with VisualAge? On 26/06/2002 17:51:40 owner-os2-unix wrote: >Edwin Günthner wrote: >> >> just wondering: has anybody ever dared/tried to build >> Perl on OS/2 with a compiler that was not gcc or pgcc? > >It's doable but a fair amount of work, as it would require not only >setting up the build process for VA, but also fixing the source to >accommodate IBM C library idiosyncracies and limitations (including no >fork()). > Implementation is left as an exercise to the reader :-) Seriously, "fair amount of work" sounds like the understatement of the year in this mailinglist. The entire build system would need to be redesigned. First of all, you can probably kiss the forking version goodbye. There's heavy wizardry invoked by EMX to emulate fork() and it only works for a.out executables. Unless LIBEMU implements fork(), you'd need to reimplement a fair chunk of EMX. There's more than just fork() missing from VisualAge, e.g. popen() Besides, if you specify 'icc' as the compiler in Configure, ksh crashes :-( well, mine does ) -- Csaba Ráduly, Software Engineer Sophos Anti-Virus email: csaba.raduly at sophos.com http://www.sophos.com US Support: +1 888 SOPHOS 9 UK Support: +44 1235 559933 **= Email 42 ==========================** Date: Wed, 26 Jun 2002 19:02:25 +0100 (CET) From: "Michel SUCH" Subject: make 3.79.1 and (gettext-0_10_39-r2-bin.zip) The latest make does not seem to be able to load the intl.dll coming with this gettext. Where can I find one that does fine? ---------------------------- Michel SUCH TEAM OS/2 FRANCE ICQ # 51654489 **= Email 43 ==========================** Date: Wed, 26 Jun 2002 19:14:29 +1000 (EST) From: "Brian Havard" Subject: Re: unixos2 packages On Wed, 26 Jun 2002 09:31:39 +0100, John Poltorak wrote: >On Wed, Jun 26, 2002 at 11:44:34AM +1000, Brian Havard wrote: > >> BTW, I have a patch for 0.9.7 that adds support for building OS/2 DLLs >> instead of static libraries which may be of use for building a unixos2 >> package. If anyone's interested I can put it up on my "Building OpenSSL" >> page. > >Yes, please. > > >> I've also got a patch for building it with Watcom C++ but I guess that's >> less likely to be of interest here :) > >I think such interest is likely to grow quite a lot over the next year. Ok, I've put both up. See http://silk.apana.org.au/apache/building-openssl.html -- ______________________________________________________________________________ | Brian Havard | "He is not the messiah! | | brianh at kheldar.apana.org.au | He's a very naughty boy!" - Life of Brian | ------------------------------------------------------------------------------ **= Email 44 ==========================** Date: Wed, 26 Jun 2002 19:39:40 +0100 (CET) From: "Michel SUCH" Subject: Re: make 3.79.1 and (gettext-0_10_39-r2-bin.zip) Hmmm, forget it, I had an older intl.dll somewhere on my libpath. On Wed, 26 Jun 2002 19:02:25 +0100 (CET), Michel SUCH wrote: >The latest make does not seem to be able to load the intl.dll coming with >this gettext. >Where can I find one that does fine? >---------------------------- >Michel SUCH TEAM OS/2 FRANCE >ICQ # 51654489 > > > ---------------------------- Michel SUCH TEAM OS/2 FRANCE ICQ # 51654489 **= Email 45 ==========================** Date: Wed, 26 Jun 2002 20:38:16 +0200 From: Holger Veit Subject: Re: latest pearl On Wed, Jun 26, 2002 at 10:49:53AM -0400, Edwin Günthner wrote: > Hi, > > John pointed out this ZIP last week: > > ftp://borneo.gmd.de/pub/misc/XFree86OS2/alpha/emxtree.zip > > It is about 64 MB in size. Maybe I can use this > to repeat my question from yesterday: what exactly > is necessary to setup this ZIP file? > Just unzipping it and then adding the usual EMX > variables to config.sys? In order to get the main functionality to compile XFree86/OS2 - and this is the *only* purpose of this distribution, you need not much more than setting the EMX and XFree86/OS2 variables (you have to direct PERLLIB/PERL5LIB to the perl subdirectory in emx/lib). To repeat: this is a closed set of binaries and files that I used to compile XFree86 - it is somewhat outdatd and contains some bits and pieces (like already compiled EMX sources) which are not strictly necessary, but I was too lazy to separate this. In particular, even if it looks a bit like some UnixOS/2 or similar unix-like distribution, it is not, and never intends to be one. Holger -- Please update your tables to my new e-mail address: holger.veit$ais.fhg.de (replace the '$' with ' at ' -- spam-protection) **= Email 46 ==========================** Date: Wed, 26 Jun 2002 20:57:35 +0000 From: "Lyn St George" Subject: Re: UnixOS/2 environment On Wed, 26 Jun 2002 18:12:32 +0200 (CEST), Stefan Neis wrote: >On Tue, 25 Jun 2002, Lyn St George wrote: > >> "In file included from perl.h:612, >> from os2.c:30: >> f:/emx/include/netinet/in.h:89: parse error before `u_long' > >> f:/usr/include/sys/socket.h:162: parse error before `u_short' > >> "os2.c: In function `file_type': >> os2.c:583: `_emx_env' undeclared (first use in this function)" > >Sounds like some missing include to e.g. . As to why >it is missing for you and apparently not for others, I'm lost. >There's been some discussion about such a problem a few weeks ago, >but I had the impression it was fixed in the latest release candidate >for Perl-5.8.0. I'm also lost. Particularly when perl 5.6.1 builds cleanly. So as to hunt for headers, I've updated "which" to now search for headers:) ftp://ftp.zolotek.net/os2/which-2.1.4_os2.zip > Regards, > Stefan > > > - Cheers Lyn St George +--------------------------------------------------------------------------------- + http://www.zolotek.net .. eCommerce hosting, consulting + http://www.os2docs.org .. some 'How To' stuff ... +---------------------------------------------------------------------------------- **= Email 47 ==========================** Date: Wed, 26 Jun 2002 21:38:00 +0100 From: John Poltorak Subject: Re: M4 build problem with texinfo On Wed, Jun 26, 2002 at 05:50:23PM +0200, Stefan Neis wrote: > On Tue, 25 Jun 2002, Thomas Dickey wrote: > > > On Tue, Jun 25, 2002 at 10:05:45PM +0100, John Poltorak wrote: > > > > > > Whilst building M4, I get the following error when creating the texinfo > > > docs:- > > > > I see stuff like this when someone's distributed a texinfo file that's > > newer than the texinfo executables (using features that weren't recognized > > by the older program). > > Maybe this time it's rather the other way round? texinfo being way to new > for M4 docs and having acquired a backward incompatible change over the > years? It seems unlikely that anybody could have a texinfo executable > that's older than the latest M4 distribution ... I've tried it again with a different version of INFO, this time 3.11 rather than 4.0, so I may have uncovered a bug in the latest version. However the Make processing of the DOC sundirectory is completely different which I don't understand at all... Using the old version of INFO, I get:- making all in doc make[1]: Entering directory `C:/unixos2/workdir/m4-1.4/doc' echo " at set EDITION 1.4" > version.tmp echo " at set UPDATED `date '+%B %Y'`" >> version.tmp echo " at set VERSION 1.4" >> version.tmp if cmp -s version.tmp ./version.texi; then rm version.tmp; \ else mv version.tmp ./version.texi; fi date > ./stamp-vti make[1]: Leaving directory `C:/unixos2/workdir/m4-1.4/doc' With the new one I get:- making install in doc make[1]: Entering directory `C:/unixos2/workdir/m4-1.4/doc' cd . && makeinfo m4.texinfo m4.texinfo:282: warning: `.' or `,' must follow cross reference, not f. .. .. .. m4.texinfo:1625: warning: `.' or `,' must follow cross reference, not f. m4.texinfo:2889: warning: `.' or `,' must follow cross reference, not i. /bin/sh ./../mkinstalldirs c:/usr/local/info cd . && for file in m4.info*; do \ c:/usr/bin/install.exe -c -m 644 $file c:/usr/local/info/$file; \ done install-info --info-dir=c:/usr/local/info c:/usr/local/info/m4.info make[1]: Leaving directory `C:/unixos2/workdir/m4-1.4/doc' The Makefiles are identical, and I don't have a clue what is happening here. > Regards, > Stefan > -- John **= Email 48 ==========================** Date: Wed, 26 Jun 2002 21:46:15 +0100 From: John Poltorak Subject: Re: building automake 1.6.2 On Wed, Jun 26, 2002 at 10:10:27PM +0100, Michel SUCH wrote: > Maybe this has been answered before, at least I saw a John's message > about. > > I have successfully built autoconf 2.53. > Now, when trying to build automake 1.6.2, the configure script complains > that it would like autoconf 1.52 or higher. > Since I installed 1.53 I would guess it should be happy! > Are there some environment variable or something like this I missed? It should be findable by the current path. I normal restrict my path when doing builds to:- c:\usr\bin;c:\usr\local\bin;c:\emx\bin;c:\os2; with autoconf going in local\bin, so check that it installed and that it is on your current path when you run automake. You should be able to do that using:- sh autoconf --version > ---------------------------- > Michel SUCH TEAM OS/2 FRANCE > ICQ # 51654489 > -- John **= Email 49 ==========================** Date: Wed, 26 Jun 2002 21:50:46 +0100 From: John Poltorak Subject: Perl: finding a DLL --cvAwO79aycg55pYS Content-Type: text/plain; charset=us-ascii I'm forwarding a post from IlyaZ about a patch for finding a DLL from within Perl. Can someone give it a try? -- John --cvAwO79aycg55pYS Content-Type: message/rfc822 Received: from mathserv.math.ohio-state.edu by mail.eyup.org (IBM OS/2 SENDMAIL VERSION 2.03/2.0) id VAA633.32; Wed, 26 Jun 2002 21:44:52 +0100 Received: from math.ohio-state.edu (math.ohio-state.edu [128.146.111.30]) by mathserv.math.ohio-state.edu (8.12.3/8.12.3) with ESMTP id g5QKigrw019622 for ; Wed, 26 Jun 2002 16:44:51 -0400 Received: (from ilya at localhost) by math.ohio-state.edu (8.11.0/8.11.0) id g5QKifZ20845 for jp at eyup.org; Wed, 26 Jun 2002 16:44:41 -0400 (EDT) Date: Wed, 26 Jun 2002 16:44:41 -0400 From: Ilya Zakharevich To: jp at eyup.org Subject: finding a DLL Message-ID: <20020626164440.A20785 at math.ohio-state.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-RAVMilter-Version: 8.3.2(snapshot 20020213) (mathserv) Dear John, could you please check whether this patch achieves what is needed to fix tests: perl -MOS2::DLL -we "print OS2::DLL->load_locate(shift)" VREXX (I have no access to develop on OS/2 for several months). If it works, can you please upload this to p5p, and incorporate this into the tests? [Please do it as above, in a child Perl process, so that there is a chance to check loading using the *full* name.] $n = `$^X -I../lib -MOS2::DLL -we "print OS2::DLL->load_locate(shift)" VREXX`; Thanks, Ilya --cvAwO79aycg55pYS-- **= Email 50 ==========================** Date: Wed, 26 Jun 2002 22:10:27 +0100 (CET) From: "Michel SUCH" Subject: building automake 1.6.2 Maybe this has been answered before, at least I saw a John's message about. I have successfully built autoconf 2.53. Now, when trying to build automake 1.6.2, the configure script complains that it would like autoconf 1.52 or higher. Since I installed 1.53 I would guess it should be happy! Are there some environment variable or something like this I missed? ---------------------------- Michel SUCH TEAM OS/2 FRANCE ICQ # 51654489 **= Email 51 ==========================** Date: Wed, 26 Jun 2002 22:57:00 +0000 From: "Lyn St George" Subject: Re: UnixOS/2 environment On Wed, 26 Jun 2002 13:44:58 +0100, John Poltorak wrote: >> (plus crypt, openssl, other non-base things) > >crypt is something I need to incorporate. >Where do I get it from? Should be on os2docs.org -> Interchange - Cheers Lyn St George +--------------------------------------------------------------------------------- + http://www.zolotek.net .. eCommerce hosting, consulting + http://www.os2docs.org .. some 'How To' stuff ... +---------------------------------------------------------------------------------- **= Email 52 ==========================** Date: Wed, 26 Jun 2002 23:00:00 +0000 From: "Lyn St George" Subject: Re: UnixOS/2 environment On Wed, 26 Jun 2002 17:39:43 -0400, Thomas Dickey wrote: >On Wed, Jun 26, 2002 at 08:57:35PM +0000, Lyn St George wrote: >> So as to hunt for headers, I've updated "which" to now search >> for headers:) ftp://ftp.zolotek.net/os2/which-2.1.4_os2.zip Sorry, got sidetracked before I could finish moving it there. >can't read it. This is what I use (ymmv) > http://invisible-island.net/conflict/ > >Usage: conflict [options] [list_of_files] > >Lists conflicts of executable files in current PATH. >First instance in path (and those linked to it) are marked >with "*", succeeding instances with "+" marks. > >Options are: > -e name specify another environment variable than $PATH > -p print pathnames only > -r look for read-able files > -t types look only for given file-types > -v (verbose) show names found in each directory > once: shows all directory names > twice: shows all filenames > thrice: shows trace of directory scanning > -w look for write-able files > -W number expand width of display by number of columns > -x look for execut-able files (default) > >Also, C-preprocessor-style -I and -L options I'll get it. >-- >Thomas E. Dickey >http://invisible-island.net >ftp://invisible-island.net > > - Cheers Lyn St George +--------------------------------------------------------------------------------- + http://www.zolotek.net .. eCommerce hosting, consulting + http://www.os2docs.org .. some 'How To' stuff ... +---------------------------------------------------------------------------------- **= Email 53 ==========================** Date: Wed, 26 Jun 2002 23:08:05 +0100 (CET) From: "Michel SUCH" Subject: Re: building automake 1.6.2 On Wed, 26 Jun 2002 21:46:15 +0100, John Poltorak wrote: >On Wed, Jun 26, 2002 at 10:10:27PM +0100, Michel SUCH wrote: >> Maybe this has been answered before, at least I saw a John's message >> about. >> >> I have successfully built autoconf 2.53. >> Now, when trying to build automake 1.6.2, the configure script complains >> that it would like autoconf 1.52 or higher. >> Since I installed 1.53 I would guess it should be happy! >> Are there some environment variable or something like this I missed? > > >It should be findable by the current path. > >I normal restrict my path when doing builds to:- > >c:\usr\bin;c:\usr\local\bin;c:\emx\bin;c:\os2; > >with autoconf going in local\bin, so check that it installed and that it >is on your current path when you run automake. > >You should be able to do that using:- > >sh autoconf --version > when I run this with no change to my current configuration, I get: autoconf (GNU Autoconf) 2.53 So it should be good? > >> ---------------------------- >> Michel SUCH TEAM OS/2 FRANCE >> ICQ # 51654489 >> > >-- >John > > > ---------------------------- Michel SUCH TEAM OS/2 FRANCE ICQ # 51654489 **= Email 54 ==========================** Date: Wed, 26 Jun 2002 23:48:25 +0100 From: Thomas Hoffmann Subject: Re: %UNIXROOT% Some weeks ago the message which is cited below showed up on os2-unix. In the meantime I tried to install some unixos2 packages of software mentioned below (man, and as a prerequisite groff) and had to do add a lot SET statements to config.sys to get these software to work (because the defaults of GROFF*PATH are c:\os2\... or so). My question is: Has there been some progress with unixrootified versions of the software mentioned below or has the implementation of UNIXROOT in ports to be discussed further? Jun Sawataishi schrieb: > > >So how do you get a program to use %UNIXROOT%. Is it as simple as > >--prefix=$UNIXROOT/usr or do you have to hack the code? If so could > >I see an example Also what happens if %UNIXROOT% isn't defined? > >Dave > > Introduction of UNIXROOT env. var. has beed discussed a lot in this mailing > list. I think: When porting Open Source Softwares, we __must__ make a strong > effort to introcude UNIXROOT. > > Here I list OSSs for which I have modified source code to use UNIXROOT. > > OSS status > -------------------------------------------------------------- > - bash 2.05, 2.05a WF, IN > - a2ps 2.13b WF, IN > - man 1.5j WF, IN > - GNU groff 1.17.2 WF, IN > - Red Hat rpm 4.0.2 WF, IN > - VFlib 3.7.12 WF, IN > - TeX-Guy 1.2.4 WF, IN > WF: working fine in my machine > IN: writing instruction is not completed > ID: writing instruction completed, but not uploaded > > > I think we should not run configure with "-prefix=$UNIXROOT/usr". By doing this > path or directory may be hard-coded in executables. To avoid this risk, I use > a function "char *unixrootify(const *char)". > unixrootify returns ' getenv("UNIXROOT") + FOO ' if UNIXROOT is not empty, > if it is empty 'drive name of HOME + FOO '. > > c.f. > In Makefile: $(CC) -DFOO=\"/usr/share/foo\" ......... -c bar.c > > In bar.c > #define libdir FOO > ............... > From > f = FOO; > To > #ifndef __EMX__ > f = FOO; > #else > f = unixrootify(FOO); > #endif > > To install a program do like this. > > If Makefile suppourt DESTDIR: > $ make install DESTDIR=${UNIXROOT} > If not > $ make install prefix=${UNIXROOT}/usr datadir=${UNIXROOT}/usr/share \ > mandir=${UNIXROOT}/usr/share/man infodir=${UNIXROOT}/usr/share/info\ > .............. > > By using UNIXROOT env. var. in source code level, program can be run without > any env. vars which indicate location of files except for UNIXROOT. > > I think new emx library should contain function like unixrootify. > Already introduced ? > > #ifdef __EMX__ > char *unixrootify(char *src) > { > if (src[0] == '/') { > const char *unixroot = getenv("UNIXROOT"); > const char *home = getenv("HOME"); > char *buf; > buf = (char *)xmalloc(strlen(src) + 5); > if ( unixroot && *unixroot != '\0') { > if ( (strlen(unixroot) == 2 ) && (unixroot[1] == ':') ) { > sprintf(buf, "%s%s", unixroot, src); > return buf; > } > } else if ( home && home[0] != '\0') { > if ( strlen(home) > 2 && home[1] == ':' ) { > strcpy(buf, home); > buf[2] = '\0'; > strcat(buf, src); > return buf; > } > } else { > free(buf); > fprintf(stderr, "\nError: You should define UNIXROOT env var\n"); > fprintf(stderr, " for %s\n", src); > } > } > return src; > } > #endif /* __EMX__ */ > > Problem of UNIXROOT > > When a drive specified by UNIXROOT lacks enough space, one must install program > another drive. In such a case, he/she must make a wrapper script/batch file which > defines UNIXROOT diffrent from config.sys. > > A solution may be simple. > unixrootify() searches for UNIXROOT, UNIXROOT_1, UNIXROOT_2, ..... > > I'd like to discuss on UNIXROOT. > > # OS/2 is not a question, it's a solution. > # SAWATAISHI Jun > # http://www2s.biglobe.ne.jp/~vtgf3mpr/ -- Thomas Hoffmann Telephone: 49-351-4598831 thoffman at zappa.sax.de Dresden, Germany ..sig under construction ...