net/avahi-app core dumps signal 11

[Robert_Burmeister]

> Robert Burmeister wrote:
>> This is a consequence of libiconv.so.3 being removed and its
>> functionality being moved into the base system with Clang. Leaving
>> the converters/libiconv port installed on FreeBSD 10 will cause 
>> errors, so your supposed to "pkg_delete -f libiconv" before
>> "portupgrade -fa". But, libgvfsdbus.so 
>> libgioremote-volume-monitor.so libavahi-glib.so.1 etc., are still
>> trying to link to libiconv.so.3 which breaks avahi-app. The
>> relevant ports need to be updated to use iconv from base when 
>> compiled on FreeBSD10+.
> 
> Thanks for the suggestion, but I believe this is not the cause of the
> SIGSEGV in avahi-daemon.
> 
> I was aware of the move of libiconv into the base system, and when I
> upgraded to 10.0-RELEASE, did exactly as you suggest: I removed the
> libiconv package and forced an upgrade of all ports, so that they'd
> link against the base system's libiconv.
> 
> I've further verified with ldd "/usr/local/lib/lib*.so*" that I have
> no shared libraries left in /usr/local/lib that were built with
> dependencies on the old /usr/local/lib/libiconv.so.3. (That is, this
> ldd command gives no "not found" errors.)
> 
> I therefore suspect that the cause lies elsewhere. Where exactly, I
> have unfortunately not yet ascertained. Other suggestions, anyone?

I noticed the ports giving problems have devel/gmake as a dependency.

A commit note for devel/gmake from 04 Sep 2013 states:

> Introduce ICONV_CONFIGURE_ARG variable defined at Uses/iconv.mk.
> It's value is "--with-libiconv-prefix=/usr/local" for systems
> before 100043 with ports libiconv and to use at systems post
> 100043 with base iconv it's value is "" (NULL).

Will check to see if this flag is being set properly after the current
recompile round.




--
View this message in context: http://freebsd.1045724.n5.nabble.com/net-avahi-app-core-dumps-signal-11-tp5878518p5880612.html
Sent from the freebsd-ports mailing list archive at Nabble.com.