Bug 237919 - devel/libunwind: libunwind-ptrace.so: undefined reference to lzma_index_size
Summary: devel/libunwind: libunwind-ptrace.so: undefined reference to lzma_index_size
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Sunpoet Po-Chuan Hsieh
URL:
Keywords:
Depends on: 246390
Blocks:
  Show dependency treegraph
 
Reported: 2019-05-16 08:35 UTC by Yuri Victorovich
Modified: 2020-05-17 18:16 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (danilo)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yuri Victorovich freebsd_committer 2019-05-16 08:35:26 UTC
One new port breaks:

> ld: error: /usr/local/lib/libunwind-ptrace.so: undefined reference to lzma_index_size
> ld: error: /usr/local/lib/libunwind-ptrace.so: undefined reference to lzma_stream_buffer_decode
> ld: error: /usr/local/lib/libunwind-ptrace.so: undefined reference to lzma_index_end
> ld: error: /usr/local/lib/libunwind-ptrace.so: undefined reference to lzma_stream_footer_decode
> ld: error: /usr/local/lib/libunwind-ptrace.so: undefined reference to lzma_index_uncompressed_size
> ld: error: /usr/local/lib/libunwind-ptrace.so: undefined reference to lzma_index_buffer_decode


This means that /usr/lib/liblzma.so needs to be added to link lines.
Comment 1 Yuri Victorovich freebsd_committer 2019-05-16 08:35:47 UTC
libunwind-20170615
Comment 2 Walter Schwarzenfeld freebsd_triage 2019-09-07 09:45:20 UTC
Maintainer feedback!
Comment 3 Danilo Egea Gondolfo freebsd_committer 2019-09-08 11:25:58 UTC
In what case that happens? How can I reproduce this issue?

As far as I can tell, the configure script will find the liblzma automatically and link the libs against it.
Comment 4 Sunpoet Po-Chuan Hsieh freebsd_committer 2020-05-17 18:16:50 UTC
libunwind 1.4.0 landed. Please update ports tree and try again. Feel free to reopen this PR if problem still exists. Thanks!