Greetings,
I have moved a big collection of modules to mod_perl2 under PerlRun
and can see a great speedup, as hoped. But in some of these modules
programs are run that write something to STDOUT that is then captured
and processed - which doesnt work since STDOUT is tie'ed to Apache.
I saw sugges
I had something that sounds the same. Setting CCFLAGS didnt
work, but
sh ./Configure -de -Accflags='-fPIC' (etc)
did give a libperl that worked on AMD x86_64. With 5.10 though.
Niels L
Dan Axtell wrote:
You will need to compile perl with -fPIC on x86_64, I think I did it with:
ccflags='-fP
I dont have a good answer. But editing the Makefile may hide the real
error .. which error appears when not editing the Makefile, and Google
with that error, no hints? what happens if -Dloclibpth="/usr/lib64"
is omitted? and of curiosity, what was the reason for going back to
perl 5.8 from 5.10? (
Thats what I would do too. The CGI::Builder author seems to be
available to help (http://perl.4pro.net), perhaps for pay, but
maybe he wont charge for compile- and bug-fixing.
Niels
Dan Axtell wrote:
On Tuesday 26 August 2008 2:28:46 pm Niels Larsen wrote:
I dont have a good answer. But
I would like to thank those who helped me, Parrin Harkins and Jim
Brandt i think it was, move to mod_perl. Some of the result is here,
http://genomics.dk:8001/UTHCT
and I learned. I start Apache in CGI mode when adding and debugging,
and mod_perl mode when done. That is a pleasant way for me, an
llection easier. But, I am grateful for what exists of course.
While watching the language certainly, I'm moving from Apache/mod_perl
to Dancer/Nginx for speed and memory reason.
Ok, back to lurk-mode,
Niels Larsen
> [OT, ADVOCACY]
>
> I am partial to perl and CPAN, because the
