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

Keith Wall commented on QPID-3723:
----------------------------------

This exact same problem seems to exist on the Ubuntu slaves of Apache Jenkins 
CI (recently upgrade to 12.04).   As I short term measure I've made the 
Qpid-Python-Cpp-Test and Qpid-Python-Cpp-Test jobs use Fraser's patch.  What is 
the long term solution to this problem?  
                
> qpid 0.12 make fails on Linux Mint 12 (I think derived from Ubuntu 11.10) 
> --------------------------------------------------------------------------
>
>                 Key: QPID-3723
>                 URL: https://issues.apache.org/jira/browse/QPID-3723
>             Project: Qpid
>          Issue Type: Bug
>          Components: Build Tools
>    Affects Versions: 0.12, 0.19
>         Environment: qpid 0.12 C++
> make fails on Linux Mint 12 but will probably also have issues with any very 
> recent gcc version.
>            Reporter: Fraser Adams
>         Attachments: fix-explicit-link-problem.patch
>
>
> make for qpid 0.12 fails in a number of places.
> See the following mailing list thread for more details:
> http://qpid.2158936.n2.nabble.com/qpid-0-12-make-fails-on-Linux-Mint-12-I-think-derived-from-Ubuntu-11-10-td7140482.html
> I believe this relates to changes made to the linker behaviour for recent gcc 
> versions so I suspect that this issue isn't limited to Linux Mint 12. See 
> http://fedoraproject.org/wiki/UnderstandingDSOLinkChange (this is a Fedora 
> page and I'm using Mint but the symptoms seem identical). 
> I've put together a patch for this which I'll attach when the Jira gets 
> created.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to