You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/09/29 15:13:34 UTC

[jira] [Commented] (PROTON-465) FindPerlLibs.cmake module in Proton behaves differently to Qpid's Perl detection

    [ https://issues.apache.org/jira/browse/PROTON-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151665#comment-14151665 ] 

ASF subversion and git services commented on PROTON-465:
--------------------------------------------------------

Commit 1628177 from [~mcpierce] in branch 'proton/trunk'
[ https://svn.apache.org/r1628177 ]

PROTON-465: FindPerlLibs fails on Ubuntu 12

If the search for libperl.so fails using the standard search in CMake,
then this alternative tool kicks in and searchs other known locations
for the file.

> 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
>
> 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)