mediatomb
Kevin Oberman
rkoberman at gmail.com
Tue Feb 11 23:29:49 UTC 2014
On Tue, Feb 11, 2014 at 2:55 PM, jcv <jv at yeaguy.com> wrote:
>
>
> On Tue, 11 Feb 2014, Kevin Oberman wrote:
>
> On Tue, Feb 11, 2014 at 12:16 PM, jcv <jv at yeaguy.com> wrote:
>> Hi - I am seeing alot of emails regarding libiconv.. Is there a
>> work
>> around for mediatomb per chance??
>>
>> ===> Building for mediatomb-0.12.1_11
>> --- all ---
>> /usr/bin/make all-recursive
>> --- all-recursive ---
>> Making all in tombupnp
>> --- all-recursive ---
>> Making all in build
>> Making all in build
>> --- mediatomb ---
>> c++ -I../src -I../tombupnp/ixml/inc -I../tombupnp/threadutil/inc
>> -I../tombupnp/upnp/inc -I.. -I/usr/local/include/mysql -pipe
>> -fno-strict-aliasing -g -DNDEBUG -I/usr/local/include
>> -I/usr/local/include -I/usr/local/include -D_THREAD_SAFE
>> -I/usr/local/include -I/usr/local/include -I/usr/local/include
>> -I/usr/local/include -O2 -pipe -fno-strict-aliasing -pthread
>> -lmagic -o mediatomb mediatomb-main.o libmediatomb.a
>> ../tombupnp/build/libtombupnp.a -L/usr/local/lib
>> -L/usr/local/lib
>> -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib
>> -L/usr/local/lib -pthread -L/usr/local/lib/mysql
>> -lmysqlclient_r
>> -pthread -lm -L/usr/local/lib -ljs -lmagic -lid3 -lexif -lz
>> -lrt -D_THREAD_SAFE -pthread -lavformat -lavutil
>> -lffmpegthumbnailer -lexpat -lmp4v2 -L/usr/local/lib -lcurl
>> -lssl -lcrypto -L/usr/lib -lgssapi -lheimntlm -lkrb5 -lhx509
>> -lcom_err
>> -lcrypto -lasn1 -lwind -lheimbase -lroken -lcrypt -pthread -lz
>> -lcurl
>> /usr/bin/ld: : invalid DSO for symbol `libiconv_open' definition
>> //usr/local/lib/libiconv.so.3: could not read symbols: Bad value
>> c++: error: linker command failed with exit code 1 (use -v to see
>> invocation)
>> *** [mediatomb] Error code 1
>>
>> make[4]: stopped in
>> /usr/ports/net/mediatomb/work/mediatomb-0.12.1/build
>> 1 error
>>
>> make[4]: stopped in
>> /usr/ports/net/mediatomb/work/mediatomb-0.12.1/build
>> *** [all-recursive] Error code 1
>>
>> make[3]: stopped in /usr/ports/net/mediatomb/work/mediatomb-0.12.1
>> 1 error
>>
>> make[3]: stopped in /usr/ports/net/mediatomb/work/mediatomb-0.12.1
>> *** [all] Error code 2
>>
>> make[2]: stopped in /usr/ports/net/mediatomb/work/mediatomb-0.12.1
>> 1 error
>>
>> make[2]: stopped in /usr/ports/net/mediatomb/work/mediatomb-0.12.1
>> ===> Compilation failed unexpectedly.
>> Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the
>> failure to
>> the maintainer.
>> *** Error code 1
>>
>> Stop.
>> make[1]: stopped in /usr/ports/net/mediatomb
>> *** Error code 1
>>
>> Stop.
>> make: stopped in /usr/ports/net/mediatomb
>> root at yeaguy:/usr/ports/net/mediatomb #
>>
>>
>> OK. What version of FreeBSD? Do you have the iconv port installed?
>>
>> I have mediatomb running fine under 10.0-RELEASE without the iconv port.
>>
>> While the base libiconv is fully POSIX compliant, the port version (GNU
>> iconv) has
>> several non-POSIX extensions that a few ports require. I have had no
>> issues with
>> mediatomb using base iconv, but your port build was clearly trying to use
>> a ports
>> version, /usr/local/lib/libiconv.so.3. The error at least implies that
>> the library
>> is corrupt.
>>
>> If you don't have libiconv installed, libiconv.so.3 is a remnant from
>> pre-upgrade,
>> so you should delete it. If you are not running 10.0, 10-STABLE (recent),
>> or HEAD,
>> you should re-install the port.
>> --
>> R. Kevin Oberman, Network Engineer, Retired
>> E-mail: rkoberman at gmail.com
>>
>>
>>
> Here is my current setup:
>
> [vic at yeaguy ~] uname -a
> FreeBSD yeaguy.com 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan
> 16 22:34:59 UTC 2014 root at snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC
> amd64
>
> [vic at yeaguy ~] pkg info | grep libic
> libical-1.0 Implementation of the IETF Calendaring and
> Scheduling protocols
> libiconv-1.14_1 A character set conversion library
> [vic at yeaguy ~]
>
> [vic at yeaguy ~] locate libiconv.so.3
> /usr/local/lib/libiconv.so.3
> [vic at yeaguy ~]
And what, if anything, do you get get from 'pkg info -r libiconv-1.14_1'?
When you went to 10.0, did you rebuild all ports and delete libiconv as
recommended? I suspect that it should have been deleted, but, as I
mentioned, a few ports use the extensions in the GNU iconv, so it is
possible that you need it. With over 1100 ports installed, I hav enot hit
on one that requires the port.
--
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkoberman at gmail.com
More information about the freebsd-ports
mailing list