From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Fri, 24 Jan 2003 04:49:01 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 23 ************************************************** Thursday 23 January 2003 Number 23 ************************************************** Subjects for today 1 Perl question : Ted Sikora 2 Re: Multiple Autoconfs : John Poltorak 3 Re: popt.h : Thomas E. Dickey" 4 Re: openssl-0.9.7 : Stefan Neis 5 popt.h : John Poltorak 6 Re: Perl question : Lyn St George" 7 Re: Perl question : John Poltorak 8 Re: Re: openssl-0.9.7 : Stefan Neis 9 Re: popt.h : Stefan Neis 10 Re: Perl question : Ted Sikora 11 [Ux2bs] Help Getting Perl to Run : Hakan" 12 Help Getting Perl to Run : Hakan" **= Email 1 ==========================** Date: Fri, 24 Jan 2003 11:19:31 -0500 From: Ted Sikora Subject: Perl question I have Perl 5.6.1 installed in D:\Perl If I copy perl.exe to \usr\bin will perl still function properly? I need this to execute #!/usr/bin/perl scripts within a cgi program. Hate to have to rewrite everything. Has anyone had experience with the cpan DBI:: and DBD::mysql modules in OS/2? Do they function properly? -- Ted Sikora tsikora at ntplx.net **= Email 2 ==========================** Date: Fri, 24 Jan 2003 13:13:29 +0000 From: John Poltorak Subject: Re: Multiple Autoconfs On Wed, Jan 22, 2003 at 05:42:35AM -0500, Thomas Dickey wrote: > On Wed, Jan 22, 2003 at 09:57:41AM +0000, John Poltorak wrote: > > > > It is apparent that I need to have multiple versions of Autoconf to be > > able to build a wide variety of apps. > > > > Can anyone suggest the best way of setting up an environment for catering > > with having more than a single installation of Autoconf? > > I manipulate the program-prefix (also requires overriding the location > of the macros), e.g., > > #!/bin/sh > TOP=/usr/local > cfg-normal \ > --prefix=$TOP \ > --program-prefix=my- \ > --datadir=$TOP/share/my-autoconf \ > --sharedstatedir=$TOP/share/my-autoconf $* > > Some people find it simpler to install into entirely different directory > trees. Since the autoconf 2.5x series is interdependent with specific > versions of automake and libtool, that's what you'll have to do. For > instance, I have a set (all mutually incompatible ;-) for autoconf 2.54, > 2.65 and 2.56 undef /usr/local/TEST. Do you also have a set of automake's and do they need to be matched up with corresponding autoconf's ? > > Currently I have the most recent version in \usr\local\bin and v2.13 in > > \usr\local1\bin. How do people handle this on Unix? > > > > -- > > John > > > > -- > Thomas E. Dickey > http://invisible-island.net > ftp://invisible-island.net -- John **= Email 3 ==========================** Date: Fri, 24 Jan 2003 13:14:22 -0500 (EST) From: "Thomas E. Dickey" Subject: Re: popt.h On Fri, 24 Jan 2003, Stefan Neis wrote: > Hi, > > > Where can I find popt.h? > > On Linux systems - and maybe latest FreeBSD versions, not on e.g. OpenBSD > or any other Unix, AFAIK. I think I stumbled on that when trying to > compile vpctimed (Virtual PC time daemon to synchronize the guest PC's > clock with the host) on anything but Linux and FreeBSD. > > It's the header file for some library which provides functions for "easy" > parsing of command line options. Probably integrated into glibc, as Linux > people tend to put just about anything on earth into it. libpopt (originally associated with the rpm tool). > My solution (e.g. for OpenBSD) was to simply remove the whole option > parsing stuff and live with the restriction to always be running it with > the default options. That was OK in my case, but in general it won't > help, of course (but maybe that kind of radical approach is even OK for > logrotate). ;-) -- T.E.Dickey http://invisible-island.net ftp://invisible-island.net **= Email 4 ==========================** Date: Fri, 24 Jan 2003 13:57:26 +0100 (CET) From: Stefan Neis Subject: Re: openssl-0.9.7 Hi, Does anyone know the limit for symbol lengths in OMF modules? After getting that "symbol multiply defined" error on "emxomf -s -l crypto.a" I had a detailled look at the symbols in the ".a" file and the only explanation I see is that there are two different symbols with a common prefix that's long enough to have both truncated to the same symbol by emxomf. Fortunately, openssl is already delivering a hack to avoid that problem ("symhacks.h"), I'll play a bit with the possible settings in that file... Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 5 ==========================** Date: Fri, 24 Jan 2003 16:47:14 +0000 From: John Poltorak Subject: popt.h Where can I find popt.h? I'm trying to build LOGROTATE which expects it to be on the INCLUDE path but I don't have it anywhere. -- John **= Email 6 ==========================** Date: Fri, 24 Jan 2003 17:41:49 +0000 From: "Lyn St George" Subject: Re: Perl question On Fri, 24 Jan 2003 11:19:31 -0500, Ted Sikora wrote: >I have Perl 5.6.1 installed in D:\Perl If I copy perl.exe to \usr\bin >will perl still function properly? I need this to execute >#!/usr/bin/perl scripts within a cgi program. Hate to have to rewrite >everything. You will also need to copy the lib/ tree, for at INC. > >Has anyone had experience with the cpan DBI:: and DBD::mysql modules >in OS/2? Do they function properly? No. I tried to get them working once but ran out of time. The default test that comes with the modules is deficient, and acknowleged as such by the author. If you run the other tests then you will see it fail with a SIGSEGV. My notes prove to be rather too cryptic to be useful this far removed from the events;/ >-- >Ted Sikora >tsikora at ntplx.net > > > > - Cheers Lyn St George +--------------------------------------------------------------------------------- + http://www.zolotek.net .. eCommerce hosting, consulting + http://www.os2docs.org .. some 'How To' stuff ... +---------------------------------------------------------------------------------- **= Email 7 ==========================** Date: Fri, 24 Jan 2003 17:59:45 +0000 From: John Poltorak Subject: Re: Perl question On Fri, Jan 24, 2003 at 05:41:49PM +0000, Lyn St George wrote: > On Fri, 24 Jan 2003 11:19:31 -0500, Ted Sikora wrote: > > >I have Perl 5.6.1 installed in D:\Perl If I copy perl.exe to \usr\bin > >will perl still function properly? I need this to execute > >#!/usr/bin/perl scripts within a cgi program. Hate to have to rewrite > >everything. > > You will also need to copy the lib/ tree, for at INC. The chances are that you have environment variable pointing at the installed Perl lib... The hard code paths are likely to be something like f:\emx so would be unlikely to work without the variable. If perl.exe is on your path and and perl*.dll is on the libpath, you should be OK as long as the variable is set correctly. > >-- > >Ted Sikora > >tsikora at ntplx.net > > > > > > > > > > - > Cheers > Lyn St George > +--------------------------------------------------------------------------------- > + http://www.zolotek.net .. eCommerce hosting, consulting > + http://www.os2docs.org .. some 'How To' stuff ... > +---------------------------------------------------------------------------------- > -- John **= Email 8 ==========================** Date: Fri, 24 Jan 2003 18:03:29 +0100 (CET) From: Stefan Neis Subject: Re: Re: openssl-0.9.7 On Fri, 24 Jan 2003, Stefan Neis wrote: > Hi, > > Does anyone know the limit for symbol lengths in OMF modules? > After getting that "symbol multiply defined" error on > "emxomf -s -l crypto.a" I had a detailled look at the symbols > in the ".a" file and the only explanation I see is that there > are two different symbols with a common prefix that's long > enough to have both truncated to the same symbol by emxomf. After some experimenting it turns out that I was wrong (especially since openssl-0.9.7 already handles the problem with upper and lower case names in symbacks.h which the snapshot from last march which I looked at didn't do yet). The real problem apparently is that "emxomf" doesn't like .a files which contain files whose names contain a "\", whereas "/" is OK. The following works for me: mkdir tmp ar x crypto.a rm crypto.a ar ru crypto.a *.o tmp/*.o rm -rf tmp *.o emxomf -s -l crypto.a i.e. create the directory "tmp" as "ar x" is unhappy if it doesn't exist already, extract all the .o files from crypto.a (some will be put into the current directory, some into the subdirectory "tmp"), remove the old archive, create a new archive, this time with names like "tmp/something.o" instead of "tmp\something.o", remove all the .o files you got by extracting the original crypto.a, run emxomf). Perhaps the makefiles can be changed to put names with "/" instead of "\" into the .a files? I realize that ssl.a does the exact some things and doesn't cause any problems with emxomf, so maybe the thing that makes the difference is the fact that in ssl.a, _all_ files have a "tmp\" prefix, whereas only _some_ (or even most) have it in crypto.a. Anyway, it looks like it really is an emxomf bug, but working around it seems easier than fixing it ... Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 9 ==========================** Date: Fri, 24 Jan 2003 18:15:01 +0100 (CET) From: Stefan Neis Subject: Re: popt.h Hi, > Where can I find popt.h? On Linux systems - and maybe latest FreeBSD versions, not on e.g. OpenBSD or any other Unix, AFAIK. I think I stumbled on that when trying to compile vpctimed (Virtual PC time daemon to synchronize the guest PC's clock with the host) on anything but Linux and FreeBSD. It's the header file for some library which provides functions for "easy" parsing of command line options. Probably integrated into glibc, as Linux people tend to put just about anything on earth into it. Anyway, the header itself won't help you, you'd also need an implementation of the three or four functions that are declared in there. My solution (e.g. for OpenBSD) was to simply remove the whole option parsing stuff and live with the restriction to always be running it with the default options. That was OK in my case, but in general it won't help, of course (but maybe that kind of radical approach is even OK for logrotate). HTH, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 10 ==========================** Date: Fri, 24 Jan 2003 18:50:45 -0500 From: Ted Sikora Subject: Re: Perl question IanM wrote: > Hi Ted > > >>I have Perl 5.6.1 installed in D:\Perl If I copy perl.exe to \usr\bin >>will perl still function properly? I need this to execute >>#!/usr/bin/perl scripts within a cgi program. Hate to have to rewrite >>everything. > > > I use gibbchg *.pl "#!/usr/bin/perl" "#!d:/usr/bin/perl.exe to do > global replaces down directory's, I must admit to also having > the perl exe's in my usr/bin, and the perl dll's in /usr/dll as > well. > > >>Has anyone had experience with the cpan DBI:: and DBD::mysql modules >>in OS/2? Do they function properly? > > > Works well for me :-) > I use PERL v5.7.2 on one server > > But on another server with a large full blown MySQL app I've > had to use PERL v5.00553 with > http://www.os2site.com/sw/apps/database/mysql/dbi-dbdmysql.zip Thanks should make things easier. > > I could never get this particular app to work with more recent versions > of PERL which had already compiled dbi-dbd in for OS/2. > > I have not tried the latest versions of PERL simply as my stuff > works, and if it aint broke, dont mess with it (hmm, thats why I That's what I keep telling people but do I follow my own advice.... no > still use OS/2 :-) > > Cheers > IanM > http://www.os2site.com/ > > > I will not be pushed, filed, stamped, briefed, debriefed, or numbered! > > -- Ted Sikora tsikora at ntplx.net **= Email 11 ==========================** Date: Fri, 24 Jan 2003 21:57:57 -0500 (EST) From: "Hakan" Subject: [Ux2bs] Help Getting Perl to Run I am new to perl but need to have it on my machine in order to use swish-e to index websites. I downloaded perl from Hobbes (perl-5.7.2.zip), unpacked it to d:\perl and read the instructions in readme.os2. Apparently you also need to have not only EMX on your system (which I had since earlier) but also gcc2952m.dll which I went to Henry Sobotka's site to download. After modifying PATH to include d:\perl\bin;d:\perl\bin\5.7.2; and LIBPATH to include d:\perl\lib;d:\perl\lib\5.7.2; and adding: SET PERLLIB_PREFIX=d:/Perl/lib;d:\Perl\lib SET PERL_BADFREE=0 SET PERL_BADLANG=0 SET PERL_SH_DIR=d:\Perl\bin to config.sys I was hoping I would finally be ready to run. No such luck. The program testperl.cmd bombs out with the following message: [D:\perl\bin]testperl ECHO is off. Testing perl... Getting version... ECHO is off. Process terminated by SIGILL core dumped SYS1808: The process has stopped. The software diagnostic code (exception code) is 001C. Process terminated by SIGILL core dumped SYS1808: The process has stopped. The software diagnostic code (exception code) is 001C. Cannot start perl !!! Please check that you have perl on PATH, and (if you do not use perl_.exe) that perl.dll is on LIBPATH. ... Keep in mind that changes to config.sys DO NOT take effect until reboot, and LIBPATH can be changed ONLY from config.sys. Per the instructions with perl 5.7.2 "These binaries are highly optimized (-O6) for Pentium Pro or equivalent (i686) machines, but in theory should run on anything down to a 386." I am trying to run it on a Cyrix 586-100 which I understand has the Pentium instruction set but behaves like a 486 and ought to run perl. The machine has W4 + FP15 installed. Can anyone point out what else I need to do to get perl up and running? Many thanks. Hakan _______________________________________________ UX2BS mailing list UX2BS at powerusersbbs.net http://powerusersbbs.net/mailman/listinfo/ux2bs **= Email 12 ==========================** Date: Fri, 24 Jan 2003 21:57:57 -0500 (EST) From: "Hakan" Subject: Help Getting Perl to Run I am new to perl but need to have it on my machine in order to use swish-e to index websites. I downloaded perl from Hobbes (perl-5.7.2.zip), unpacked it to d:\perl and read the instructions in readme.os2. Apparently you also need to have not only EMX on your system (which I had since earlier) but also gcc2952m.dll which I went to Henry Sobotka's site to download. After modifying PATH to include d:\perl\bin;d:\perl\bin\5.7.2; and LIBPATH to include d:\perl\lib;d:\perl\lib\5.7.2; and adding: SET PERLLIB_PREFIX=d:/Perl/lib;d:\Perl\lib SET PERL_BADFREE=0 SET PERL_BADLANG=0 SET PERL_SH_DIR=d:\Perl\bin to config.sys I was hoping I would finally be ready to run. No such luck. The program testperl.cmd bombs out with the following message: [D:\perl\bin]testperl ECHO is off. Testing perl... Getting version... ECHO is off. Process terminated by SIGILL core dumped SYS1808: The process has stopped. The software diagnostic code (exception code) is 001C. Process terminated by SIGILL core dumped SYS1808: The process has stopped. The software diagnostic code (exception code) is 001C. Cannot start perl !!! Please check that you have perl on PATH, and (if you do not use perl_.exe) that perl.dll is on LIBPATH. ... Keep in mind that changes to config.sys DO NOT take effect until reboot, and LIBPATH can be changed ONLY from config.sys. Per the instructions with perl 5.7.2 "These binaries are highly optimized (-O6) for Pentium Pro or equivalent (i686) machines, but in theory should run on anything down to a 386." I am trying to run it on a Cyrix 586-100 which I understand has the Pentium instruction set but behaves like a 486 and ought to run perl. The machine has W4 + FP15 installed. Can anyone point out what else I need to do to get perl up and running? Many thanks. Hakan