Stas Bekman wrote:
Steve Hay wrote:
[...]
Having a pointer to where the mod_perl.lib library was
installed would be useful. I'm not sure calling it
MODPERL_STATIC_LIB_LOCATION would be the best thing on
Win32, as it's not a static library as such, but something
could be come up with ...
Well
Randy Kobes wrote:
On Fri, 12 Sep 2003, Steve Hay wrote:
Hi,
Has anybody else got mp2 (CVS) working with recent perl-5.8.1's on Windows?
I've got it building, but I can't start the Apache server at all. (It's
fine without the mod_perl bits in the httpd.conf file.)
See this thread on p5p
Randy Kobes wrote:
On Mon, 15 Sep 2003, Steve Hay wrote:
PS. Randy: How do you that stacktrace output that you've
posted? Is that using MSVC++, or something else?
Hi Steve,
I'm using MSVC++ ... When a problem like this occurs,
an offer is made to call up the VC++ debugger, where
Randy Kobes wrote:
On Thu, 11 Sep 2003, Geoffrey Young wrote:
The problem you described before with the missing symbols
can be resolved by linking against the mod_perl.lib built
when you build mod_perl.so. This can be done by adding in
a LIBS attribute to WriteMakefile() in Makefile.PL with a
Hi,
Has anybody else got mp2 (CVS) working with recent perl-5.8.1's on Windows?
I've got it building, but I can't start the Apache server at all. (It's
fine without the mod_perl bits in the httpd.conf file.)
See this thread on p5p for what I'm getting:
Stas Bekman wrote:
Randy Kobes wrote:
On Fri, 12 Sep 2003, Steve Hay wrote:
I believe that mod_perl 2 now installs the mod_perl.lib
somewhere to solve that kind of problem. Is there an
option in the mod_perl 1 build process to thave that
library installed, or could that be added to the next
Hi,
I posted this problem the other day, deep inside a thread about
something else, and didn't get any replies; maybe nobody spotted it?
Does anybody have Apache::Dispatch working on Windows with Perl 5.8.0?
Randy?
I'm trying to build it on Windows XP (MSVC++ 6) with Perl 5.8.0 / Apache
Steve Hay wrote:
Thomas Klausner wrote:
Hi!
On Mon, Sep 08, 2003 at 04:51:55PM +0100, Steve Hay wrote:
The project is going to be written as a series of mod_perl handlers
- one for the main home page, and others for various
sub-components. Each handler is implemented by a separate module
Marc Slagle wrote:
On Mon, 2003-09-08 at 11:51, Steve Hay wrote:
It also needs to have access to various static resources (images,
stylesheets, JavaScript libraries etc.).
Thus, I want to have something like this:
/myproject [mp1]
/myproject/component1 [mp1]
/myproject
Perrin Harkins wrote:
On Mon, 2003-09-08 at 11:51, Steve Hay wrote:
Thus, I want to have something like this:
/myproject [mp1]
/myproject/component1 [mp1]
/myproject/component2 [mp1]
...
/myproject/images [static]
/myproject/javascript [static]
/myproject
petersm wrote:
Steve Hay [EMAIL PROTECTED] wrote
Location /myproject
SetHandler perl-script
PerlHandler MyProject-dispatcher
/Location
LocationMatch ^/myproject/(images|javascript|stylesheets)
SetHandler default-handler
/LocationMatch
Correct me if I'm wrong, but can't you just
Hi,
I'm having trouble deciding what the best plan is for the arrangement of
the components of a new project that I'm starting.
The project is going to be written as a series of mod_perl handlers -
one for the main home page, and others for various sub-components.
Each handler is implemented
Jean-Sebastien Guay wrote:
Steve,
and the good news for you is that I've reproduced your problem.
GREAT! Thank you so much for persevering through this! So do you have a
traceback or some info that the developers might be able to use to track
this down?
Not sure how to get a stack
Jean-Sebastien Guay wrote:
Steve,
How did you build Apache 2?
I downloaded the binaries... Sorry, can't help there.
Please keep me posted as to your progress.
OK, I've now got Apache 2 building (with a little off-list help from
Randy Kobes - the secret is to use the .zip sources
Sreeji K Das wrote:
I tried to compile mod_perl-1.28 with perl maint.
20512 (http://www.iki.fi/jhi/[EMAIL PROTECTED]). I had a
build failure (different errors each time trying to
build).
Have you tried http://www.iki.fi/jhi/[EMAIL PROTECTED] ? That snapshot
worked OK for me on WinXP.
- Steve
Jean-Sebastien Guay wrote:
So, did anyone have time to check this out? This is pretty major for me,
I can't implement mod_perl at my site until I find out what is causing
this crash and fix it. And I really have no idea what could be causing
it.
I'm using CGI.pm 2.98, Template-Toolkit 2.10,
Jean-Sebastien Guay wrote:
Can't get http://whitestar02.webhop.org/Files/ApacheCrash.zip
it resolves to an internal address: 192.168.0.3
Darn, looks like my web server didn't come back up right last night.
I'll have to be there to fix it, because ssh doesn't get through either.
Here's
Michael G Schwern wrote:
The problem is likely the MY::dynamic hack in c/Makefile.PL. 6.05 and
previous had this:
dynamic :: Makefile $(INST_DYNAMIC) $(INST_BOOT)
6.06_01 and up have this
dynamic :: $(FIRST_MAKEFILE) $(INST_DYNAMIC) $(INST_BOOT)
for some reason, MY::dynamic is trying to lop
Michael G Schwern wrote:
On Mon, Aug 04, 2003 at 08:46:27AM +0100, Steve Hay wrote:
I tried changing the s/// to:
$string =~ s{ \$\(INST_DYNAMIC\)}{}g;
$string =~ s{ \$\(INST_BOOT\)}{}g;
(I've dropped the trailing spaces in the patterns), which produced:
dynamic :: $(FIRST_MAKEFILE
Michael G Schwern wrote:
On Mon, Aug 04, 2003 at 09:35:55AM +0100, Steve Hay wrote:
Somehow, it has contrived to disappear! It always used to exist there,
which is why it didn't occur to me to check :-( I must have lost it
somewhere along the line when shoe-horning earlier MakeMaker's
Michael G Schwern wrote:
On Thu, Jul 31, 2003 at 03:23:36PM +0100, Steve Hay wrote:
This patch finally fixes it for me:
I'm glad you guys got it working, but there's still the problem of why
MakeMaker's behavior changed. Since I tend not to touch the XS building
code much its likely
Steve Hay wrote:
Michael G Schwern wrote:
If I could see the Makefiles from 6.03 and 6.12 I might be able to
figure out
what's different. Also, if you could try various alpha versions between
those two, show the Makefiles and whether or not they exhibited the
behavior that would help alot
Steve Hay wrote:
This bug evidently goes back a long way: MM 6.06_02 fails in the same
way as 6.13.
I tried to use MM 6.06_01, but it wouldn't build itself (don't know
how to make 'C:\perl5\libNAME'). Instead, I knife-and-forked it into
place, but when I tried to use it to build libapreq, I
Michael G Schwern wrote:
On Fri, Aug 01, 2003 at 10:03:20AM +0100, Steve Hay wrote:
This bug evidently goes back a long way: MM 6.06_02 fails in the same
way as 6.13.
I tried to use MM 6.06_01, but it wouldn't build itself (don't know
how to make 'C:\perl5\libNAME'). Instead, I knife
Steve Hay wrote:
Randy Kobes wrote:
On Tue, 29 Jul 2003, Steve Hay wrote:
Is anybody going to take a serious look at the problem that I
previously
reported with Apache-print()'s handling of UTF-8 data in Perl 5.8?
The patch that I sent
(http://marc.theaimsgroup.com/?l=apache-modperlm
Stas Bekman wrote:
Jarkko has just released perl-5.8.1-RC3. Quite a few things have
changed since 5.8.0. So it's *very* important that you test your code
with this release and immediatelly report to p5p if you have any
problems, since Jarkko wants to release 5.8.1 any moment now.
BAD NEWS:
Stas Bekman wrote:
Here is what happens:
MM 6.03 used to create libapreq.a but not libapreq.so, libapreq.a was
just a by product and never was intented to be installed. Request.so
was statically linking libapreq.a into it.
Now with 6.12 it creates both libapreq.so and libapreq.so, so when
Stas Bekman wrote:
Steve Hay wrote:
Stas Bekman wrote:
Stas Bekman wrote:
Steve Hay wrote:
Stas Bekman wrote:
Here is what happens:
MM 6.03 used to create libapreq.a but not libapreq.so, libapreq.a
was just a by product and never was intented to be installed.
Request.so was statically
Is anybody going to take a serious look at the problem that I previously
reported with Apache-print()'s handling of UTF-8 data in Perl 5.8?
The patch that I sent
(http://marc.theaimsgroup.com/?l=apache-modperlm=105912130001046w=2)
seems to fix it for me on Windows as long as I've got perl
Stas Bekman wrote:
Steve Hay wrote:
Is anybody going to take a serious look at the problem that I
previously reported with Apache-print()'s handling of UTF-8 data in
Perl 5.8?
Steve,
At the moment I'm busy fixing things for p5.8.1 for which mod_perl 2.0
is one of the showstoppers
Randy Kobes wrote:
On Tue, 29 Jul 2003, Steve Hay wrote:
Is anybody going to take a serious look at the problem that I previously
reported with Apache-print()'s handling of UTF-8 data in Perl 5.8?
The patch that I sent
(http://marc.theaimsgroup.com/?l=apache-modperlm=105912130001046w=2)
seems
Steve Hay wrote:
Stas Bekman wrote:
I have attempted to shoe-horn this into mod_perl's print() method (in
src/modules/perl/Apache.xs). Here's the diff against mod_perl 1.28:
[Unfortunately, I've had to comment-out the first part of that if
block, because I got an unresolved external symbol
Stas Bekman wrote:
Steve Hay wrote:
It's only Perl 5.8 that has the special UTF-8 flag which the
functions above all operate with respect to. If a Perl variable
contains a sequence of bytes that make up a valid UTF-8 character,
but the string is not flagged with Perl's special flag
Hi Stas,
Stas Bekman wrote:
Steve Hay wrote:
Hi,
I've just spent quite a while tracking down a problem with a web page
generated by a mod_perl program in which 8-bit ISO-8859-1 characters
were not being shown properly. The software runs via
Apache::Registry, and works fine under mod_cgi
Stas Bekman wrote:
I have attempted to shoe-horn this into mod_perl's print() method (in
src/modules/perl/Apache.xs). Here's the diff against mod_perl
1.28: [Unfortunately, I've had to comment-out the first part of that
if block, because I got an unresolved external symbol error
relating to
Hi,
I've just spent quite a while tracking down a problem with a web page
generated by a mod_perl program in which 8-bit ISO-8859-1 characters
were not being shown properly. The software runs via Apache::Registry,
and works fine under mod_cgi.
It turns out that the problem is due to a
Hi Randy,
Randy Kobes wrote:
On Thu, 3 Jul 2003, Steve Hay wrote:
Philippe M. Chiasson wrote:
The URL
http://perl.apache.org/dist/mod_perl-1.28.tar.gz
has entered CPAN
I still get the same test failures that I reported before when
RC2 was announced:
modules/request...FAILED
Hi Philippe,
Philippe M. Chiasson wrote:
The URL
http://perl.apache.org/dist/mod_perl-1.28.tar.gz
has entered CPAN
I still get the same test failures that I reported before when RC2 was
announced:
modules/request...FAILED tests 3-8
Failed 6/10 tests, 40.00% okay
Setup: Windows
Hi Randy,
Randy Kobes wrote:
On Tue, 24 Jun 2003, Steve Hay wrote:
Philippe M. Chiasson wrote:
On Tue, 2003-06-24 at 23:00, Steve Hay wrote:
Philippe M. Chiasson wrote:
Now bringing you the second mod_perl 1.28 release candidate.
[snip]
Windows XP, Apache
Philippe M. Chiasson wrote:
Now bringing you the second mod_perl 1.28 release candidate.
[snip]
Please give this release a spin and report back any problems or failed tests to:
[EMAIL PROTECTED] as soon as possible. The more platforms configurations, the
merrier!
Windows XP, Apache 1.3.27, Perl
Philippe M. Chiasson wrote:
On Tue, 2003-06-24 at 23:00, Steve Hay wrote:
Philippe M. Chiasson wrote:
Now bringing you the second mod_perl 1.28 release candidate.
[snip]
Please give this release a spin and report back any problems or failed tests to:
[EMAIL PROTECTED] as soon as possible
Terra Info wrote:
2) a probable answer anyhow-
[...] Check to see if the user you run apache under is allowed to
interact with the desktop. It should be in the services CPL applet
under the entry for that service. Check that and restart the service.
A related problem that I stumbled upon
Randy Kobes wrote:
On Mon, 16 Dec 2002, Steve Hay wrote:
Is there some other way, for Win32, to achieve what the
PERL_USELARGEFILES=0 hack tried to do?
This seems hard to do without recompiling either the standard
Apache sources (to enable large_files support) or else the
standard
Hi,
I'm having trouble compiling mod_perl 1.27 (with Apache 1.3.27 / Perl
5.8.0) on Windows (XP SP1 with MS VC++ 6.0 SP5).
It builds fine with Perl 5.8.0 standard sources, but I'm just trying to
upgrade my Perl to the slightly patched sources that ActivePerl Build
804 uses. I've built Perl
Randy Kobes wrote:
On Mon, 16 Dec 2002, Steve Hay wrote:
I'm having trouble compiling mod_perl 1.27 (with Apache 1.3.27 / Perl
5.8.0) on Windows (XP SP1 with MS VC++ 6.0 SP5).
It builds fine with Perl 5.8.0 standard sources, but I'm just trying to
upgrade my Perl to the slightly patched
e::Registry did this for me when it does its
stuff with my script), so I'm stuck with the warning (or else "use
vars").
Is there some reason why the warning gets emitted with "our" inside
print_power_of_2()? Was I just lucky that this particular example
worked and I should really heed the warning, or is the warning actually
bogus?
Is there any way I can use "our" rather than "use vars" and not get
these warnings?
- Steve Hay
Bill Moseley wrote:
At 02:02 PM 02/26/01 +, Steve Hay wrote:
I have a script which I wish to run under either mod_perl or CGI which does
little more than display content and I would like it to stop when the user
presses Stop, but I can't get it working.
You need to do different things
es no difference if I take out the first "$SIG{PIPE} = \handler;" line
(and rely on mod_perl to handle the SIGPIPE for me as Stas described above)
and/or put the "PerlFixupHandler Apache::SIG" directive in my httpd.conf.
Can anybody help/explain?
I'm running Apache/1.3.17 and mod_perl/1.25 on Windows NT 4.
Cheers,
Steve Hay
filters aren't
working. The filters hooks all live in yylex, which get called
indirectly by perl_parse."
Is there anyone familiar with both Filter and mod_perl who could shed
any more light on what's going on here?
Thanks,
Steve Hay
Hello2Goodbye.pm
filtertest.pl
erl??? Does mod_perl
need the EAPI like mod_ssl does (at least on Win32)???
Steve Hay
. This is the default compiler mode.
The machine I was building on was Solaris 2.4 with the Sun Compiler v3.0
in which the cc manpage says "-Xt" ('transition') is the default. I
also have a Solaris 2.6 machine with the Sun Compiler v4.0 which says,
like the snippet above, that "-Xa" is the default.
Steve Hay
Steve Hay wrote:
I'm having a problem compiling mod_perl 1.23 (with Apache 1.3.12 / Perl
5.6.0) as a DSO using APXS on Solaris 2.4.
In case anyone is interested...
I've solved my own problem (just as well, really). If I re-compile
everything with the -Xa compiler flag then it all works out
at these locations in the install directory works
fine, thus removing the need to keep the build directory floating about.
This presumably means that I can now ditch the build directory and still
be able to build mod_perl 1.24 when it comes using only my Apache
install directory.
- Steve Hay
I'm having problems using "CGI::Carp qw(fatalsToBrowser);" in modperl
scripts.
Below are three short scripts and their output under Apache/CGI
and Apache/modperl. All three of them produce (more or less) useful
output under Apache/CGI, but only the last one does under Apache/modperl.
The first
Sorry! Here it is again in text/plain this time...
(My mail client doesn't ask whether I want to send in text or HTML,
hence the slip. Maybe *I* should get a new one!)
---
I'm having problems using "CGI::Carp qw(fatalsToBrowser);" in modperl
scripts.
Below are three short scripts and their
the Makefile in the mysql sub-directory to change:
OTHERLDFLAGS = -LD:\mysql/lib/opt
to:
OTHERLDFLAGS = -LIBPATH:D:\mysql/lib/opt
None of this was necessary on my Solaris 2.6 box, however, where everything
went like a dream...
- Steve Hay
) : error
C2373: 'win32_closedir' : redefinition; different type modifiers
D:\perl5\lib\CORE\win32iop.h(121) : see declaration of
'win32_closedir'
Any ideas, anyone?
Has anyone else got 5.6.0 / 1.3.12 / 1.22 going on NT 4?
Steve Hay
"G.W. Haywood" wrote:
Come to think of it, NT probably wasn't the best idea you ever had
either.
I agree, but we're selling a web application and most of our customers
want it on NT.
Unfortunately, now I can't get (the Apache side of) mod_perl to
compile.
You aren't alone. You really
...
Steve Hay
Randy Kobes wrote:
On Thu, 30 Mar 2000, Steve Hay wrote:
Has anyone else got 5.6.0 / 1.3.12 / 1.22 going on NT 4?
Hi,
There's a couple things you can do -
- add the flag /D "WIN32IOP_H" - this handles the win32_opendir
and similar errors.
- for the mode_t error,
kefile options:
CFG = Optimize
USE_PERLCRT
PERL_MALLOC
- Apache 1.3.12 built with VC++ 6
- mod_perl 1.22 built with VC++ 6
- D: is a local disk which I have full access to
I've found that the problem goes away if I downgrade to Apache 1.3.6 and
keep everything else the same!
Steve Hay
want to re-direct it to a file - and the difference between the one which
works and the one which doesn't work is not mod_perl: it's the Apache version!
Am I also correct in thinking that configuring Perl with sfio is only an
option on Unix (which, BTW, doesn't have my problem anyway!)?
Help!
Steve Hay
61 matches
Mail list logo