[
https://issues.apache.org/jira/browse/PROTON-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165460#comment-14165460
]
Darryl L. Pierce commented on PROTON-465:
-----------------------------------------
The new update should fix this problem entirely. And in the process I also
fixed the name of our module so that it didn't conflict with the CMake built-in
module, which caused it to never use the default. So now if CMake fails only
then will our module kick in. If it doesn't find perl.h or the shared library
for linking, then the build will turn off Perl bindings and show a warning only.
> FindPerlLibs.cmake module in Proton behaves differently to Qpid's Perl
> detection
> --------------------------------------------------------------------------------
>
> Key: PROTON-465
> URL: https://issues.apache.org/jira/browse/PROTON-465
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-c
> Affects Versions: 0.5
> Environment: Ubuntu 11.10 (at least)
> Reporter: Fraser Adams
> Assignee: Darryl L. Pierce
> Priority: Minor
> Fix For: 0.8
>
>
> With Proton when I do cmake .. it barfs with
> -- Trying alternative search for Perl
> -- PerlLibs Not Found
> Though I can get it to play nicely by doing
> cmake .. -DPERL_LIBRARY=`locate -n 1 libperl.so`
> This might not be so unreasonable as I'm using a fairly old version of Ubuntu
> that needs upgrading, however the Perl detection on Qpid works perfectly well
> for me (and I'd assume for others too) which suggests that it's possibly more
> thorough.
> At the very least it would seem sensible to maintain consistency with the
> cmake modules across various Qpid components.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
