Opened 4 years ago
Last modified 4 years ago
#60938 closed defect
exiv2 @0.27.3_0: undefined symbols _libiconv — at Initial Version
Reported by: | parafin | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.6.3 |
Keywords: | Cc: | ||
Port: | exiv2 |
Description
exiv2 0.27.3_0 fails to build with the following error:
:info:build Undefined symbols for architecture x86_64: :info:build "_libiconv", referenced from: :info:build Exiv2::convertStringCharset(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >&, char const*, char const*) in convert.cpp.o :info:build "_libiconv_close", referenced from: :info:build Exiv2::convertStringCharset(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >&, char const*, char const*) in convert.cpp.o :info:build "_libiconv_open", referenced from: :info:build Exiv2::convertStringCharset(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >&, char const*, char const*) in convert.cpp.o :info:build ld: symbol(s) not found for architecture x86_64
Full build log is attached.
The problem seems to be that exiv2 finds and links to system libiconv, which uses iconv prefix for exported symbols instead of libiconv. But libiconv installed by macports uses libiconv prefix and its header gets pulled into include path before system one it seems. I'm not sure how/why it worked before... When building manually this doesn't happen, so maybe new macports version (it got upgraded from 2.6.2 to 2.6.3) now force /opt/local/include into include path?..
Note: See
TracTickets for help on using
tickets.
build log