Re: modperl 2.0
On Sun, Aug 12, 2001 at 03:49:30PM -0400, Barrie Slaymaker wrote: On Sun, Aug 12, 2001 at 08:39:09AM -0600, The Doctor wrote: I will try, but this indicates to me that perl 5.6 is geared towards Linux without consideration for BSD/OS and related OSes. Huh? I don't follow. Neither would Tom Baker ;-). We're discussing different ways of installing Perl so that later versions and earlier versions can coexist (and even cooperate, see below). Since most (all common?) OSs don't deal with library versioning issues transparently, it's up to the app (perl in this case). Most apps don't bother. The Perl config gurus try very hard to make it so that multiple versions will coexist by default and even to make it so that newer versions will hunt back through previous versions' library trees for libraries so you don't have to install multiple copies of libraries just to have multiple versions of Perl able to call the same libraries. It's not perfect, but it seems to work pretty well. On a wide variety of platforms. If it isn't installed to use this version number in it's library path(s), that's ok too, but don't blame Perl's design; that's an installer's decision, I believe. - Barrie This is not going well with me as this forces to stay at perl 5.00503 until BSD/OS comes up with the new perl distrubution.
Re: modperl 2.0
On Sun, Aug 12, 2001 at 03:49:30PM -0400, Barrie Slaymaker wrote: On Sun, Aug 12, 2001 at 08:39:09AM -0600, The Doctor wrote: I will try, but this indicates to me that perl 5.6 is geared towards Linux without consideration for BSD/OS and related OSes. Huh? I don't follow. Neither would Tom Baker ;-). We're discussing different ways of installing Perl so that later versions and earlier versions can coexist (and even cooperate, see below). Since most (all common?) OSs don't deal with library versioning issues transparently, it's up to the app (perl in this case). Most apps don't bother. The Perl config gurus try very hard to make it so that multiple versions will coexist by default and even to make it so that newer versions will hunt back through previous versions' library trees for libraries so you don't have to install multiple copies of libraries just to have multiple versions of Perl able to call the same libraries. It's not perfect, but it seems to work pretty well. On a wide variety of platforms. If it isn't installed to use this version number in it's library path(s), that's ok too, but don't blame Perl's design; that's an installer's decision, I believe. perl 5.6.1 calling itself perl 5.6.0 Come off of it!
Re: modperl 2.0
On Sun, Aug 12, 2001 at 03:46:24PM -0600, The Doctor wrote: This is not going well with me as this forces to stay at perl 5.00503 until BSD/OS comes up with the new perl distrubution. Again, I don't follow. What leads you to that conclusion? - Barrie
Re: modperl 2.0
On Sun, Aug 12, 2001 at 03:47:09PM -0600, The Doctor wrote: perl 5.6.1 calling itself perl 5.6.0 Come off of it! I don't know where you got that idea.
Re: modperl 2.0
On Sun, Aug 12, 2001 at 05:50:01PM -0400, Barrie Slaymaker wrote: On Sun, Aug 12, 2001 at 03:46:24PM -0600, The Doctor wrote: This is not going well with me as this forces to stay at perl 5.00503 until BSD/OS comes up with the new perl distrubution. Again, I don't follow. What leads you to that conclusion? Unless Te perl group can identify this 5.6.X problem at this level, I will have to wait for BSD/OS to release 4.3 with WE HOPE perl 5.6.1 .
Re: modperl 2.0
On Sun, 12 Aug 2001, The Doctor wrote: On Sun, Aug 12, 2001 at 05:51:22PM -0400, Barrie Slaymaker wrote: On Sun, Aug 12, 2001 at 03:47:09PM -0600, The Doctor wrote: perl 5.6.1 calling itself perl 5.6.0 Come off of it! I don't know where you got that idea. When I ran perl 5.6.1 it was identifying itself as perl 5.6.0 . Identity crisis?? A) This is fairly OT at this point. B) You have a broken Perl installation. This is neither the fault of Perl nor mod_perl. It _may_ be the fault of the BSD packaging folks, or someone may have simply screwed up your install on the machine you're using. The easiest thing might be to download the 5.6.1 tarball and install from scratch. Or you could continue being obnoxious on an unrelated list and giving Barrie shit when he's just trying to help you. -dave /*== www.urth.org We await the New Sun ==*/
Re: modperl 2.0
On Sun, Aug 12, 2001 at 03:55:26PM -0600, The Doctor wrote: When I ran perl 5.6.1 it was identifying itself as perl 5.6.0 . Identity crisis?? Dunno, but you can bet it's not right. Care to post the command and results? Sounds like a symlink problem, you might want to use some combination of the ls -l, whence or hash, sum and strings commands to figure out what's right. I can promise you that perl 5.6.1 properly reports itself and that you'd have to edit it somehow to make it say otherwise (and I'm not proposing that somebody did). Whatever perls are running around that box are pretty screwed up, but the good news is it should be pretty easy to fix once the problem is hunted down... - Barrie
[ANNOUNCE] HTTP::WebTest 1.05
The following message is a courtesy copy of an article that has been posted to comp.lang.perl.announce as well. The uploaded file HTTP-WebTest-1.05.tar.gz has entered CPAN as file: $CPAN/authors/id/I/IL/ILYAM/HTTP-WebTest-1.05.tar.gz size: 60698 bytes md5: 8c9b0742f34310f41e35cca8fc1bdc36 NAME HTTP::WebTest - Test remote URLs or local web files DESCRIPTION This module runs tests on remote URLs or local web files containing Perl/JSP/HTML/JavaScript/etc. and generates a detailed test report. The test specifications can be read from a parameter file or input as method arguments. If you are testing a local file, Apache is started on a private/dynamic port with a configuration file in a temporary directory. The module displays the test results on the terminal by default or directs them to a file. The module optionally e-mails the test results. Each URL/web file is tested by fetching it from the web server using a local instance of an HTTP user agent. The basic test is simply whether or not the fetch was successful. You may also test using literal strings or regular expressions that are either required to exist or forbidden to exist in the fetched page. You may also specify tests for the minimum and maximum number of bytes in the returned page. You may also specify tests for the minimum and maximum web server response time. If you are testing a local file, the module checks the error log in the temporary directory before and after the file is fetched from Apache. If messages are written to the error log during the fetch, the module flags this as an error and writes the messages to the output test report. Changes since 1.04: * Installation of http-webtest directory is optional now for Unix platforms. It is completely disabled on Win32 platform. * Mentioned in docs that this module should work on Win32 platform. Bug reports from this platform would be appreciated. * Do not use environment variable WEBTEST_LIB in 'wt' script. It seems to be needed only for debuging purposes and it was a source of many Perl warnings if it was not defined. * Sample Apache config file bundled with this module now contains directives to disable usage of apache access and resource config files. * Use File::Temp for sane creation of temporary directories. * Removed section 'CHANGES' from HTTP::WebTest POD docs since it became too long. Anybody interested in changes should consult this file. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | Ilya Martynov (http://martynov.org/)| | GnuPG 1024D/323BDEE6 D7F7 561E 4C1D 8A15 8E80 E4AE BE1A 53EB 323B DEE6 | | AGAVA Software Company (http://www.agava.com/) | -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
problems building apache + mod_perl + mod_ssl on FreeBSD 4.3
Hi all, I am trying to build mod_perl-1.26 for Apache 1.3.20 with mod_ssl 2.8.4 on FreeBSD. The version of perl that I have installed on this machine is 5.6.1 If I build just mod_perl and Apache, the build goes fine. The problem only exists if I add mod_ssl to the mix. To configure Apache, I have used the following command : ./configure --prefix=/usr/apache_admin --enable-module=all \ --enable-shared=max --enable-module=ssl \ --activate-module=src/modules/perl/libperl.a --enable-module=perl \ --disable-shared=ssl --disable-shared=perl I am using the mod_ssl installation instructions as follows : cd mod_ssl-2.8.4-1.3.20 ./configure --with-apache=../apache_1.3.20 cd ../mod_perl-1.26 perl Makefile.pl EVERYTHING=1 APACHE_SRC=../apache_1.3.20/src \ USE_APACI=1 PREP_HTTPD=1 DO_HTTPD=1 make make install cd ../apache_1.3.20 then I use the configure line described above. The configure goes fine in the Apache directory. The make breaks with the following error though : gcc -funsigned-char -DMOD_SSL=208104 -DMOD_PERL -DUSE_PERL_SSI -fno-strict-aliasing -I/usr/local/include -DEAPI -DUSE_EXPAT -I./lib/expat-lite `./apaci` -L/usr/lib -Wl,-E -o httpd buildmark.o modules.o modules/standard/libstandard.a modules/ssl/libssl.a modules/perl/libperl.a main/libmain.a ./os/unix/libos.a ap/libap.a lib/expat-lite/libexpat.a -lcrypt -lssl -lcrypto -Wl,-E -L/usr/local/lib /usr/local/lib/perl5/5.6.1/i386-freebsd/auto/DynaLoader/DynaLoader.a -L/usr/local/lib/perl5/5.6.1/i386-freebsd/CORE -lperl -lm -lc -lcrypt -liconv -lutil /usr/local/lib/perl5/5.6.1/i386-freebsd/auto/DynaLoader/DynaLoader.a(DynaLoader.o): In function `SaveError': DynaLoader.o(.text+0x159): undefined reference to `Perl_vmess' *** Error code 1 Stop in /home/waynep/src/apache_1.3.20/src. *** Error code 1 I'm pretty sure that this worked with apache 1.3.19 and the previous version of mod_ssl. Like I say, this only happens if mod_ssl is included in the mix. If I just do mod_perl and Apache, it works ok. Any assistance would be much appreciated! TIA, -- - Wayne Pascoe | Be nice to your daemons. [EMAIL PROTECTED] | http://www.penguinpowered.org.uk |
problems building apache + mod_perl + mod_ssl on FreeBSD 4.3
Sorry if this appears twice. My mailserver says that it was accepted, but it has not shown up on the list yet... Hi all, I am trying to build mod_perl-1.26 for Apache 1.3.20 with mod_ssl 2.8.4 on FreeBSD. The version of perl that I have installed on this machine is 5.6.1 If I build just mod_perl and Apache, the build goes fine. The problem only exists if I add mod_ssl to the mix. To configure Apache, I have used the following command : ./configure --prefix=/usr/apache_admin --enable-module=all \ --enable-shared=max --enable-module=ssl \ --activate-module=src/modules/perl/libperl.a --enable-module=perl \ --disable-shared=ssl --disable-shared=perl I am using the mod_ssl installation instructions as follows : cd mod_ssl-2.8.4-1.3.20 ./configure --with-apache=../apache_1.3.20 cd ../mod_perl-1.26 perl Makefile.pl EVERYTHING=1 APACHE_SRC=../apache_1.3.20/src \ USE_APACI=1 PREP_HTTPD=1 DO_HTTPD=1 make make install cd ../apache_1.3.20 then I use the configure line described above. The configure goes fine in the Apache directory. The make breaks with the following error though : gcc -funsigned-char -DMOD_SSL=208104 -DMOD_PERL -DUSE_PERL_SSI -fno-strict-aliasing -I/usr/local/include -DEAPI -DUSE_EXPAT -I./lib/expat-lite `./apaci` -L/usr/lib -Wl,-E -o httpd buildmark.o modules.o modules/standard/libstandard.a modules/ssl/libssl.a modules/perl/libperl.a main/libmain.a ./os/unix/libos.a ap/libap.a lib/expat-lite/libexpat.a -lcrypt -lssl -lcrypto -Wl,-E -L/usr/local/lib /usr/local/lib/perl5/5.6.1/i386-freebsd/auto/DynaLoader/DynaLoader.a -L/usr/local/lib/perl5/5.6.1/i386-freebsd/CORE -lperl -lm -lc -lcrypt -liconv -lutil /usr/local/lib/perl5/5.6.1/i386-freebsd/auto/DynaLoader/DynaLoader.a(DynaLoader.o): In function `SaveError': DynaLoader.o(.text+0x159): undefined reference to `Perl_vmess' *** Error code 1 Stop in /home/waynep/src/apache_1.3.20/src. *** Error code 1 I'm pretty sure that this worked with apache 1.3.19 and the previous version of mod_ssl. Like I say, this only happens if mod_ssl is included in the mix. If I just do mod_perl and Apache, it works ok. Any assistance would be much appreciated! TIA, -- - Wayne Pascoe | You cannot apply a technological [EMAIL PROTECTED] | solution to a sociological problem. http://www.penguinpowered.org.uk | (Edwards' Law) |
[ANNOUNCE] HTTP::WebTest 1.06
The following message is a courtesy copy of an article that has been posted to comp.lang.perl.announce,comp.lang.perl.modules as well. The URL http://martynov.org/tgz/HTTP-WebTest-1.06.tar.gz has entered CPAN as file: $CPAN/authors/id/I/IL/ILYAM/HTTP-WebTest-1.06.tar.gz size: 60811 bytes md5: 991300e6ea655d90b34b8fcadde3e9fd NAME HTTP::WebTest - Test remote URLs or local web files DESCRIPTION This module runs tests on remote URLs or local web files containing Perl/JSP/HTML/JavaScript/etc. and generates a detailed test report. The test specifications can be read from a parameter file or input as method arguments. If you are testing a local file, Apache is started on a private/dynamic port with a configuration file in a temporary directory. The module displays the test results on the terminal by default or directs them to a file. The module optionally e-mails the test results. Each URL/web file is tested by fetching it from the web server using a local instance of an HTTP user agent. The basic test is simply whether or not the fetch was successful. You may also test using literal strings or regular expressions that are either required to exist or forbidden to exist in the fetched page. You may also specify tests for the minimum and maximum number of bytes in the returned page. You may also specify tests for the minimum and maximum web server response time. If you are testing a local file, the module checks the error log in the temporary directory before and after the file is fetched from Apache. If messages are written to the error log during the fetch, the module flags this as an error and writes the messages to the output test report. Changes since 1.05: * Some files required for local web files testing mode were missing in last HTTP-WebTest distributions. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | Ilya Martynov (http://martynov.org/)| | GnuPG 1024D/323BDEE6 D7F7 561E 4C1D 8A15 8E80 E4AE BE1A 53EB 323B DEE6 | | AGAVA Software Company (http://www.agava.com/) | -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Re: modperl 2.0
On Sun, Aug 12, 2001 at 07:18:11PM -0400, Barrie Slaymaker wrote: On Sun, Aug 12, 2001 at 03:55:26PM -0600, The Doctor wrote: When I ran perl 5.6.1 it was identifying itself as perl 5.6.0 . Identity crisis?? Dunno, but you can bet it's not right. Care to post the command and results? Sounds like a symlink problem, you might want to use some combination of the ls -l, whence or hash, sum and strings commands to figure out what's right. I can promise you that perl 5.6.1 properly reports itself and that you'd have to edit it somehow to make it say otherwise (and I'm not proposing that somebody did). Whatever perls are running around that box are pretty screwed up, but the good news is it should be pretty easy to fix once the problem is hunted down... This is beter than the perl people. I promise I will. Mail me on Thursday as a reminder.
Re: knowledge base
On Sun, Aug 12, 2001 at 02:44:27PM +0800, Stas Bekman wrote: On Sat, 11 Aug 2001, Jim Smith wrote: I am thinking about splitting this into two projects: backend repository modules and frontend web interface. My strength is on the backend stuff. This allows for multiple frontends to be designed without affecting the backend. For example, if someone's favorite environment was Mason, then that could be the frontend. Otherwise, someone else might want a command line interface. This also allows for other things to be put between the two, such as an XML-RPC layer, if that was appropriate. it'd be nice if you could put together some really simple frontend, so others can build on top of it some more advanced once. You need some frontend anyway in order to test it. I'll probably start with some simple CLI scripts for testing the backend stuff. Basicly, whatever I am using for development. cool. When did you say we get to play with this system? :) I'll probably aim for November/December for the backend and May for a frontend (for TAMU). I have a couple other projects going at the same time at work and I'm basically a one-man shop for this kind of stuff. I should be able to put in a fair amount of time after this month. Alpha/beta code will be available before the dates I mentioned. --jim
Re: modperl 2.0
On Sun, 12 Aug 2001, Barrie Slaymaker wrote:
On Sun, Aug 12, 2001 at 08:39:09AM -0600, The Doctor wrote:
I will try, but this indicates to me that perl 5.6 is geared towards
Linux without consideration for BSD/OS and related OSes.
Huh? I don't follow. Neither would Tom Baker ;-).
I think the guy got confused because in your examples you've used
copy-n-paste from your OS, which is linux :)
and when I install (say) 5.6.1 here, it would be at:
/usr/local/lib/perl5/5.6.1/i686-linux/Config.pm
By comparison, the error message above is reporting:
/usr/libdata/perl5/i386-bsdos/Config.pm
so this is fine, on linux this is called /i{3|4|5|6}86-linux/ whereas on
BSD this will be /i{3|4|5|6}86-bsdos/ or similar :)
but this all goes off-topic here.
_
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://apachetoday.com http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
Re: perl 5.6.1 compiling problem.
On Sun, 12 Aug 2001, erb wrote: While trying to compile 5.6.1 w/ dynamic support for mod_perl, I ran into this problem.. looks like you've sent this email to the wrong address. This is mod_perl list, not perl one. See http://lists.perl.org/ to find Perl related lists. when you post to the right forum, make sure to provide more information, than just the error. Making DynaLoader (static) Makefile out-of-date with respect to ../../lib/Config.pm ../../config.h Cleaning current config before rebuilding Makefile... make -f Makefile.old clean /dev/null 21 || /bin/sh -c true ../../miniperl -I../../lib -I../../lib Makefile.PL INSTALLDIRS=perl LIBPERL_A=libperl.a /usr/libexec/ld-elf.so.1: Cannot open ./libperl.a *** Error code 1 Stop in /usr/local/src/perl-5.6.1/ext/DynaLoader. make config failed, continuing anyway... make: don't know how to make all. Stop *** Error code 2 Stop in /usr/local/src/perl-5.6.1. any ideas? _ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://apachetoday.com http://eXtropia.com/ http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
Re: problems building apache + mod_perl + mod_ssl on FreeBSD 4.3
On 12 Aug 2001, Wayne Pascoe wrote: Hi all, I am trying to build mod_perl-1.26 for Apache 1.3.20 with mod_ssl 2.8.4 on FreeBSD. The version of perl that I have installed on this machine is 5.6.1 If I build just mod_perl and Apache, the build goes fine. The problem only exists if I add mod_ssl to the mix. see http://perl.apache.org/guide/install.html#mod_perl_and_mod_ssl_openssl_ Thanks for the link. I have followed the instructions there, and it looks to me like the mod_perl configuration does the Apache configuration for me if I use these instructions. Is this correct? yup, via APACI_ARGS In any event, doing a make in the mod_perl-1.26 directory still produces this error : I don't have freebsd to try, but have you tried first to follow exactly the steps as they are in the guide, without changing anything? Does it work for you? It does work for me on linux. _ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://apachetoday.com http://eXtropia.com/ http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
cvs commit: modperl-2.0/util getdiff.pl
sbekman 01/08/12 19:18:38
Added: util getdiff.pl
Log:
patch generator utility
Revision ChangesPath
1.1 modperl-2.0/util/getdiff.pl
Index: getdiff.pl
===
#!/usr/bin/perl -w
# this script creates a diff against CVS
# and against /dev/null for all files in ARGV
# and prints it to STDOUT
#
# e.g.
# getdiff.pl t/modules/newtest t/response/TestModules/NewTest.pm \
# newtest.patch
#
# the generated patch can be applied with
# patch -p0 newtest.patch
# cvs diff
my $o = `cvs diff`;
# strip '? filename' cvs lines for unknown files
$o =~ s/^\?.*\n//gm;
for (@ARGV) {
$o .= \n;
$o .= `diff -u /dev/null $_`
}
print $o;
