Hi,
It took a while for this to sink into my weak little brain, but I did
almost exactly as you said and life is good! I ended up putting the new
Perl in /opt and linking /usr/local/bin/perl to it.
I read some stuff that scared me away from trying to replace the existing
5.6.1 perl.
Thanks for
On Fri, Sep 24, 2004 at 02:45:14PM -0400, Perrin Harkins wrote:
> On Wed, 2004-09-22 at 23:58, Ryan Underwood wrote:
> > I might have figured it out. The program wasn't closing STDOUT at the
> > end of printing stuff to the client. Is this a known boo-boo?
>
> I don't normally touch STDOUT or S
Hi,
I just realized I have no idea what you just told me because of that
Configure in the command line.
I did find this in the INSTALL which makes some sense:
On most systems, both Perl and Apache+mod_perl must be built using the
same compiler. Sometimes Perl's configuration will choose one
comp
At 01:42 PM 9/24/2004, John D Groenveld wrote:
In message <[EMAIL PROTECTED]>, Eric
writes
:
>Which sounds like the answer to my problem except I don't know how to
>correctly make these changes so that gcc flags are used instead of Solaris
>compiler flags. I am guessing that mod_perl is being a li
On Fri, 24 Sep 2004, Matthew Hodgson wrote:
Stas Bekman wrote:
Matthew, please try the current cvs, Philippe has been working hard on
improving the static build since _16 was released.
http://perl.apache.org/download/source.html#Development_mod_perl_2_0_Source_Distribution
Okay, my previous build
In message <[EMAIL PROTECTED]>, Eric writes
:
>Which sounds like the answer to my problem except I don't know how to
>correctly make these changes so that gcc flags are used instead of Solaris
>compiler flags. I am guessing that mod_perl is being a little too smart for
As root,
# rm /usr/bin/pe
Hi,
I have installed: gcc -v
Reading specs from /opt/sfw/gcc-3/lib/gcc-lib/i386-pc-solaris2.9/3.3.2/specs
Configured with: ../gcc-3.3.2/configure --prefix=/opt/sfw/gcc-3
--with-ld=/usr/ccs/bin/ld --with-as=/usr/ccs/bin/as --without-gnu-ld
--without-gnu-as --enable-shared
Thread model: posix
gcc v
On Wed, 2004-09-22 at 23:58, Ryan Underwood wrote:
> I might have figured it out. The program wasn't closing STDOUT at the
> end of printing stuff to the client. Is this a known boo-boo?
I don't normally touch STDOUT or STDERR directly at all. Has the
problem reappeared since you did this?
- P
On Thu, 23 Sep 2004, Stas Bekman wrote:
Matthew Hodgson wrote:
Stas Bekman wrote:
Matthew, please try the current cvs, Philippe has been working hard on
improving the static build since _16 was released.
http://perl.apache.org/download/source.html#Development_mod_perl_2_0_Source_Distribution
---
Yesterday I submitted a bug report titled
"The "cannot find -lapr-0" and ""undefined symbol:
apr_bucket_setaside_notimpl" problems again" and
you said
Jon, please try the current cvs:
http://perl.apache.org/download/source.html#Development_mod_perl_2_0_Source_Distribution
I just did. The linking
Steve Hay wrote:
>Jan Dubois wrote:
>
>
>>The other issue you are seeing is that CoInitialize() needs to be called
>>in each *thread* that wants to make COM calls. To do this properly, the
>>module needs to provide a CLONE method if you are using Perl threads in
>>5.8.x.
>>
>>
>>
>That's no
11 matches
Mail list logo
