Re: iconv in base breaks multiple ports

2013/10/22 Tijl Coosemans <tijl_at_coosemans.org>:
> On Mon, 21 Oct 2013 22:34:45 +0200 Ulrich Spörlein wrote:
>> On Mon, 2013-10-21 at 13:18:55 +0200, Tilman Keskinöz wrote:
>>> * Ulrich Spörlein [Sun, 20 Oct 2013 20:27:23 +0200]:
>>>> ever since that iconv thing replaced the ports version, I run into
>>>> trouble with several ports that I have installed on a -CURRENT (now
>>>> stable/10 system).
>>>>
>>>> These are not compile-time errors, but crashes or limited functionality
>>>> where I blame iconv :)
>>>>
>>>> 1. www/newsbeuter crashes during startup, somewhere in the stfl code
>>>> that deals with wide char functions.
>>>>
>>>> Is my system hexed? I've rebuilt the ports/packages a dozen times now.
>>>> Am I seeing ghosts?
>>>
>>> I don't run Current, but according to the pkg-fallout mails i am
>>> receiving, newsbeuter shouldn't even compile on CURRENT. Maybe there are
>>> some stale files on your system?
>>>
>>> There is also an update in the PR system, you might want to try,
>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/182896
>>
>> Right, I had to set USE_GCC=any and muck with -liconv flags of course to
>> get it to build.
>
> Hmm, does this mean you still have libiconv installed?  Because then
> your crashes may be because some libraries use libc iconv and others
> libiconv iconv.

No no, the port just blindly links against libiconv and I had to patch
that, obviously. My system is clean of any libiconv-from-ports.

But as a next step, I shall now build base w/o iconv and bring back
libiconv from ports to see if that fixes my issues.

ttyl
Uli