On Thu, 30 Dec 2004, William McKee wrote:
> Hi folks,
>
> I'm trying to recompile Perl and Apache/mod_perl on a Debian Sarge
> system using the following versions:
>
> Perl 5.8.6
> Apache 1.3.33
> mod_perl 1.29
>
> I am compiling mod_perl statically (using Apachetoolbox) with the
> following
William McKee wrote:
On Fri, Dec 31, 2004 at 02:02:59PM -0500, Stas Bekman wrote:
Thanks William, I've committed that with a few tweaks. Especially the last
para. Please check that it still makes sense.
Looks fine except for a couple of typos (dangling quote mark and
mispelled 'should'). Also, no
On Fri, Dec 31, 2004 at 02:02:59PM -0500, Stas Bekman wrote:
> Thanks William, I've committed that with a few tweaks. Especially the last
> para. Please check that it still makes sense.
Looks fine except for a couple of typos (dangling quote mark and
mispelled 'should'). Also, now that I'm a bit
William McKee wrote:
Thanks for the clear explanation of *.a and *.so files, Stas. I'm
starting to grok how it works together.
I've attached the diff to the install docs to this message which
incorporates some of your notes about .so and .a files. I found this
information hard to find while browsin
Thanks for the clear explanation of *.a and *.so files, Stas. I'm
starting to grok how it works together.
I've attached the diff to the install docs to this message which
incorporates some of your notes about .so and .a files. I found this
information hard to find while browsing Google, Perlmonks
William McKee wrote:
On Thu, Dec 30, 2004 at 05:57:07PM -0500, Stas Bekman wrote:
During compilation of mod_perl, I was seeing undefined reference errors
which are nicely described on the install page[1]. The prescription
suggests rebuilding Perl with dynamic linking; apparently the version
that's
On Thu, Dec 30, 2004 at 05:57:07PM -0500, Stas Bekman wrote:
> >During compilation of mod_perl, I was seeing undefined reference errors
> >which are nicely described on the install page[1]. The prescription
> >suggests rebuilding Perl with dynamic linking; apparently the version
> >that's shipped w
On Thu, Dec 30, 2004 at 07:32:19PM -0500, Stas Bekman wrote:
> >Hmm, that's what I thought too and was creating a symlink from
> >/usr/lib/libperl.so to the newly created one. I was still getting
> >strange behavior though so moved them all out of /usr/lib. Seems a bit
> >better now.
>
> If the ap
William McKee wrote:
On Thu, Dec 30, 2004 at 07:00:36PM -0500, Stas Bekman wrote:
I'm guessing that this goes for any libperl.so, e.g. libperl.so.5.6 or
libperl.so.5.8. If so then it would explain the weird behavior that I've
been getting when compiling mod_perl.
Normally in addition to libperl.so.
On Thu, Dec 30, 2004 at 07:00:36PM -0500, Stas Bekman wrote:
> >I'm guessing that this goes for any libperl.so, e.g. libperl.so.5.6 or
> >libperl.so.5.8. If so then it would explain the weird behavior that I've
> >been getting when compiling mod_perl.
>
> Normally in addition to libperl.so.5.8 the
William McKee wrote:
On Thu, Dec 30, 2004 at 05:57:07PM -0500, Stas Bekman wrote:
As [2] explains you have more than one libperl.so and the wrong one gets
loaded. libperl.so should *not* be in /usr/lib or any other globally seen
loader path if you want to have more than one perl on the same syste
On Thu, Dec 30, 2004 at 05:57:07PM -0500, Stas Bekman wrote:
> As [2] explains you have more than one libperl.so and the wrong one gets
> loaded. libperl.so should *not* be in /usr/lib or any other globally seen
> loader path if you want to have more than one perl on the same system.
> Unfortuna
William McKee wrote:
Hi folks,
I'm trying to recompile Perl and Apache/mod_perl on a Debian Sarge
system using the following versions:
Perl 5.8.6
Apache 1.3.33
mod_perl 1.29
I am compiling mod_perl statically (using Apachetoolbox) with the
following options:
APACHE_PREFIX=/usr/local/apache
13 matches
Mail list logo
