[MacPorts] #42582: Building p5.14-libapreq2 fails (upgrade)
MacPorts
noreply at macports.org
Sun Mar 16 14:54:05 PDT 2014
#42582: Building p5.14-libapreq2 fails (upgrade)
-----------------------------------------+--------------------------------
Reporter: st.graef@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.2.1
Resolution: | Keywords:
Port: p5.14-libapreq2, mod_perl2 |
-----------------------------------------+--------------------------------
Comment (by murrayeisenberg@…):
Replying to [comment:8 ryandesign@…]:
> "`sudo port -ns upgrade --force mod_perl2`" should rebuild mod_perl2 for
whatever perl you've made default. For me, mod_perl2 fails to build when
perl5.18 is default. Also, you cannot install p5-libapreq2 for perl5.18
because no p5.18-libapreq2 subport exists yet.
On 08/03/2014 01:03, Murray Eisenberg wrote:
Apparently at present, libapreq2 will not work with perl 5.18. Is that
correct?
(I'm using the MacPorts port of perl 5.18 under Mac OS X and install perl
modules, including those for apache2 support, using MacPorts. And I'm told
that the libapreq2 port available there has no perl 5.18-compatible sub-
port because libapreq2 itself is not yet compatible with perl 5.18.)
If so, this is to request a perl 5.18-compatible version of libapreq2.
[What's involved in creating that? (I'm not a Perl programmer but just
need libapreq2 -- actually, a MacPorts port of it -- for use with an
Apache server application.)
I received the following response when on the apreq-dev-
help at httpd.apache.org list I requested a perl 5.18-compatible version of
libapreq2, so that a MacPorts port could then be possible:
I didn't see any problems with perl-5.18 and libapreq2.
However, a trivial attempt to install mod_perl with Perl 5.18
(httpd-2.2.10) crashed. If you want to use the perl-glue for libapreq2
and mod_perl, that can be a problem. I have no idea if it's a
compatibility issue, or due to my not having compiled mod_perl in
several years now, and having borked something in my rusty toolchain.
Have you asked about this on the mod_perl users list at all?
I'm unsure what question to ask of the mod_perl users list or, more
generally, how to resolve the issue.
--
Ticket URL: <https://trac.macports.org/ticket/42582#comment:10>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list