You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Douglas Creager (Created) (JIRA)" <ji...@apache.org> on 2011/10/15 16:19:11 UTC
[jira] [Created] (AVRO-929) CMake doesn't set install_name on Mac
OS X
CMake doesn't set install_name on Mac OS X
------------------------------------------
Key: AVRO-929
URL: https://issues.apache.org/jira/browse/AVRO-929
Project: Avro
Issue Type: Bug
Components: c
Affects Versions: 1.6.0
Reporter: Douglas Creager
Assignee: Douglas Creager
On Mac OS X, you need to use install_name_tool to set the install_name property for any shared libraries, especially if they're installed into a non standard location. The CMake scripts don't do this by default:
{code}
$ otool -D /tmp/foobar/lib/libavro.22.0.0.dylib
/tmp/foobar/lib/libavro.22.0.0.dylib:
libavro.22.0.0.dylib
{code}
This means that anything that links with libavro can't find the library at runtime.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AVRO-929) CMake doesn't set install_name on Mac
OS X
Posted by "Douglas Creager (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Douglas Creager resolved AVRO-929.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
Checked into SVN trunk, revision 1183648
> CMake doesn't set install_name on Mac OS X
> ------------------------------------------
>
> Key: AVRO-929
> URL: https://issues.apache.org/jira/browse/AVRO-929
> Project: Avro
> Issue Type: Bug
> Components: c
> Affects Versions: 1.6.0
> Reporter: Douglas Creager
> Assignee: Douglas Creager
> Fix For: 1.6.0
>
>
> On Mac OS X, you need to use install_name_tool to set the install_name property for any shared libraries, especially if they're installed into a non standard location. The CMake scripts don't do this by default:
> {code}
> $ otool -D /tmp/foobar/lib/libavro.22.0.0.dylib
> /tmp/foobar/lib/libavro.22.0.0.dylib:
> libavro.22.0.0.dylib
> {code}
> This means that anything that links with libavro can't find the library at runtime.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira