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

Gordon Sim commented on QPID-4702:
----------------------------------

The following patch has been confirmed to fix the problem where reported, and 
does not break platforms on which the issue wasn't observed. It is not however 
strictly correct as it involves the libraries being listed twice in the link 
command, once before and once after the .o files.

{noformat}
Index: src/ssl.cmake
===================================================================
--- src/ssl.cmake       (revision 1464148)
+++ src/ssl.cmake       (working copy)
@@ -72,6 +72,9 @@
         )
 
     add_library (sslcommon SHARED ${sslcommon_SOURCES})
+    foreach(f ${NSS_LIBRARIES})
+      target_link_libraries (sslcommon ${f})
+    endforeach(f)
     target_link_libraries (sslcommon qpidcommon)
     set_target_properties (sslcommon PROPERTIES
                            VERSION ${sslcommon_version}
{noformat}
                
> cmake build of ssl support does not work on certain platforms
> -------------------------------------------------------------
>
>                 Key: QPID-4702
>                 URL: https://issues.apache.org/jira/browse/QPID-4702
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker, C++ Client
>    Affects Versions: 0.20, 0.22
>            Reporter: Gordon Sim
>            Assignee: Gordon Sim
>
> This is a result of the order of libraries and object files passed to the 
> linker. The libraries must follow the .o files that require them or they will 
> be ignored (assumed not needed).

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