Bug 181489 - [ports/graphics/djvulibre] Fix build error on 10-current
Summary: [ports/graphics/djvulibre] Fix build error on 10-current
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Brendan Fabeny
Depends on:
Reported: 2013-08-23 17:40 UTC by Norikatsu Shigemura
Modified: 2014-03-04 19:37 UTC (History)
0 users

See Also:

file.diff (770 bytes, patch)
2013-08-23 17:40 UTC, Norikatsu Shigemura
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Norikatsu Shigemura freebsd_committer 2013-08-23 17:40:00 UTC
djvulibre is depends on converters/iconv, but no use.
In 10-current, unfortunatly, djvulibre can find iconv functions.
As a result, djvulibre has build error like following.

--- bzz ---
libtool: link: clang++ -o .libs/bzz -DHAVE_CONFIG_H -I.. -I.. -I../libdjvu -I. -DNDEBUG -Wall -Wno-non-virtual-dtor -I/usr/local/include -I/usr/local/include -D_THREAD_SAFE -DTHREADMODEL=POSIXTHREADS -O2 -pipe -fvectorize -march=corei7 -fno-strict-aliasing bzz.o -pthread  ../libdjvu/.libs/libdjvulibre.so -L/usr/local/lib /usr/local/lib/libjpeg.so -lm -pthread -Wl,-rpath -Wl,/usr/local/lib
./libdjvu/.libs/libdjvulibre.so: undefined reference to `libiconv'
./libdjvu/.libs/libdjvulibre.so: undefined reference to `libiconv_close'
./libdjvu/.libs/libdjvulibre.so: undefined reference to `libiconv_open'
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
*** [bzz] Error code 1

Fix: At least, in this time, no longer use iconv.  So disable dependency on iconv.
And preserve effect of stock iconv.

Patch attached with submission follows:
How-To-Repeat: On 10-current, /usr/include/iconv.h is exists, and undef __LIBICONV_COMPAT on /usr/include/_libiconv_compat.h.

$ cd /usr/ports/graphics/djvulibre/
$ make
checking iconv.h usability... yes
checking iconv.h presence... yes
checking for iconv... yes
Comment 1 Edwin Groothuis freebsd_committer 2013-08-23 17:40:07 UTC
Responsible Changed
From-To: freebsd-ports-bugs->bf

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 Tijl Coosemans freebsd_committer 2014-03-04 19:36:21 UTC
State Changed
From-To: open->closed

This problem appears to have been fixed in r328492.