-DDL_UNLOAD_ALL_AT_EXIT

2002-06-01 Thread Stas Bekman
I'm compiling a list of changes in Perl 5.6-5.8 that have some impact on mod_perl. Rafael Garcia-Suarez is reviewing this section and has asked whether -DDL_UNLOAD_ALL_AT_EXIT is of any use to mod_perl. from perl561delta: Perl can also optionally arrange to unload all extension shared

ANNOUNCE: mod_perl-1.99_02

2002-06-01 Thread Doug MacEachern
The URL http://perl.apache.org/dist/mod_perl-1.99_02.tar.gz has entered CPAN as file: $CPAN/authors/id/D/DO/DOUGM/mod_perl-1.99_02.tar.gz size: 378436 bytes md5: b08c12adc1a8ae4ce7a111f8d5fe0b43 Changes since 1.99_02: pass the PATH and TZ environment variables at startup by default

ANNOUNCE: mod_perl-1.27

2002-06-01 Thread Doug MacEachern
The URL http://perl.apache.org/dist/mod_perl-1.27.tar.gz has entered CPAN as file: $CPAN/authors/id/D/DO/DOUGM/mod_perl-1.27.tar.gz size: 372525 bytes md5: bd07f4f1065eb0d0a8d8004219357d8c Changes since 1.26: workaround Cwd bug in 5.8.0-RC1 that breaks apache configuration on solar

Re: Stacktrace for BusError: failed MODPERL-2 build on MacOSX(Apache/2.0.36 mod_perl/1.99_02-dev Perl/v5.6.1)

2002-06-01 Thread Doug MacEachern
On Sat, 1 Jun 2002, R Blake wrote: > [root@server]perl test.pl > Bus error ok, you should report this as a perlbug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: fixed -undefined suppress; now trouble with -bundle: failedMODPERL-2 build on MacOSX (Apache/2.0.36 mod_perl/1.99_02-dev Perl/v5.6.1)

2002-06-01 Thread Doug MacEachern
On Sat, 1 Jun 2002, R Blake wrote: > > ok. have you tried using -des -Dusethreads instead of the interactive > > Configure dialog? > > > > not yet. i strongly suggest trying that before going any further. the bus error for example might be related to use64bitint=define, which i'm pretty sure

Re: Stacktrace for BusError: failed MODPERL-2 build on MacOSX(Apache/2.0.36 mod_perl/1.99_02-dev Perl/v5.6.1)

2002-06-01 Thread R Blake
doug, [root@server]cat test.pl (your test script ) use strict; use Socket; my $localhost_addr = pack('C4', 127, 0, 0, 1); my $default_localhost = gethostbyaddr($localhost_addr, Socket::AF_INET()) || 'localhost'; print "localhost=$default_localhost\n"; [root@server]perl test.pl Bus error

Re: Stacktrace for BusError: failed MODPERL-2 build on MacOSX(Apache/2.0.36 mod_perl/1.99_02-dev Perl/v5.6.1)

2002-06-01 Thread Doug MacEachern
On Sat, 1 Jun 2002, R Blake wrote: > #7 0x004658b8 in Perl_pp_ghostent we call this in Apache::TestConfig::default_localhost, does the script below work for you or cause the same bus error? use strict; use Socket; my $localhost_addr = pack('C4', 127, 0, 0, 1); my $default_localhost = get

fixed -undefined suppress; now trouble with -bundle: failedMODPERL-2 build on MacOSX (Apache/2.0.36 mod_perl/1.99_02-dev Perl/v5.6.1)

2002-06-01 Thread R Blake
doug, > > ok. have you tried using -des -Dusethreads instead of the interactive > Configure dialog? > not yet. just finishing up the -undefined suppress problem in LDFLAGS ... unfortunately, although the -undefined suppress problem seems to have gone away, now make dies at: cc -flat_

Stacktrace for BusError: failed MODPERL-2 build on MacOSX(Apache/2.0.36 mod_perl/1.99_02-dev Perl/v5.6.1)

2002-06-01 Thread R Blake
doug, >> just curious, any comments re: the "bus error" i'd rec'd and the code i >> commented out (previous msg )? > > no ideas unless i can reproduce or you can post a stacktrace. > here's the invoke & resulting stack trace .. [root@server]perl Makefile.PL MP_AP_PREFIX=/usr/local/apa

Re: Build modperl2 when modperl1 is already installed

2002-06-01 Thread Doug MacEachern
On Sun, 2 Jun 2002, Gerald Richter wrote: > I don't use this option, because it's not the default and I want to test the > default case (at least for the moment) and when I last tried it (ok, this > was long ago) it didn't work, because it is not the default and it seems > that at this time nobo

Re: $ENV{PATH}

2002-06-01 Thread Doug MacEachern
On Sun, 2 Jun 2002, Gerald Richter wrote: > my problem arises in the startup.pl, which does a > > require Cwd ; > > which complains about an undefined $ENV{PATH}. Would it make sense to copy > the above code to modperl_env_configure_server, so it's also available at > startup? i see, 1.x had

Re: Build modperl2 when modperl1 is already installed

2002-06-01 Thread Gerald Richter
Hi, > > i'd rather not add this, simply because i'd like to see as few build > options as possible in 2.0. the pile of build options in 1.x has led to a > great deal of confusion and mess. you should instead use the > MP_INST_APACHE2=1 option, then you can use the modperl-2.0/blib with > PerlMod

Re: $ENV{PATH}

2002-06-01 Thread Gerald Richter
> > > > I realized that $ENV{PATH} isn't set anymore under mod_perl 2.0. > > it will only be set if you configure SetHandler perl-script, which calls > ap_add_common_vars, which does: > if (!(env_path = getenv("PATH"))) { > env_path = DEFAULT_PATH; > } > apr_table_addn(e, "PATH", apr_p

Re: Build modperl2 when modperl1 is already installed

2002-06-01 Thread Doug MacEachern
On Sat, 1 Jun 2002, Gerald Richter wrote: > Hi, > > Makefile.PL doesn't run when mod_perl 1.x is already installed. I like to be > able to do it anyway, so I can afterwards set PERL5LIB to mod_perl's blib, > so I don't need to maintain another Perl installation (I already have enough > different

Re: $ENV{PATH}

2002-06-01 Thread Doug MacEachern
On Sat, 1 Jun 2002, Gerald Richter wrote: > Hi, > > I realized that $ENV{PATH} isn't set anymore under mod_perl 2.0. it will only be set if you configure SetHandler perl-script, which calls ap_add_common_vars, which does: if (!(env_path = getenv("PATH"))) { env_path = DEFAULT_PATH;

Re: failed MODPERL-2 build on MacOSX (Apache/2.0.36 mod_perl/1.99_02-devPerl/v5.6.1)

2002-06-01 Thread Doug MacEachern
On Sat, 1 Jun 2002, Per Einar Ellefsen wrote: > You'll have to register a project... But why don't you just go ahead and > register mod_perl? That doesn't imply anything, you can remove the CVS > repository and point everything to the mod_perl website. Then you can take > advantage of the com

Re: failed MODPERL-2 build on MacOSX (Apache/2.0.36 mod_perl/1.99_02-devPerl/v5.6.1)

2002-06-01 Thread Doug MacEachern
On Fri, 31 May 2002, R Blake wrote: > OSX uses (usually) an HFS partition (read problems with case sensitivity!) > so > specifying "-Dfirstmakefile=GNUmakefile" simply sidesteps the problems > known to occur with "Makefile" vs. "makefile" .. ok. have you tried using -des -Dusethreads inst

Build modperl2 when modperl1 is already installed

2002-06-01 Thread Gerald Richter
Hi, Makefile.PL doesn't run when mod_perl 1.x is already installed. I like to be able to do it anyway, so I can afterwards set PERL5LIB to mod_perl's blib, so I don't need to maintain another Perl installation (I already have enough different versions on my system :-). So I added a MP_FORCE=1 opt

$ENV{PATH}

2002-06-01 Thread Gerald Richter
Hi, I realized that $ENV{PATH} isn't set anymore under mod_perl 2.0. This causes a undefined value warning when I do a require Cwd ; since Cwd searches the PATH. I guess there will be more modules that likes to see something in PATH. I personaly can simply workround this by do a PerlPassEnv PATH,