Re: Re: libc++ vs. libstdc++ usage in the ports tree

From: Jan Henrik Sylvester <me_at_janh.de>
Date: Wed, 27 Nov 2013 19:31:44 +0100
On 11/14/2013 15:45, Steve Kargl wrote:
> On Thu, Nov 14, 2013 at 09:54:52AM +0000, David Chisnall wrote:
>> On 13 Nov 2013, at 19:40, Dimitry Andric <dim_at_freebsd.org> wrote:
>>
>>> On the other hand, different C++ standard libraries simply cannot be
>>> mixed.  The internal implementations are usually completely different.
>>> This is not really news at all, certainly not to the ports people. :-)
>>
>> That said, it should still be possible to mix them in different
>> libraries.  The constraint from the wiki still applies: if you
>> don't use STL types at library boundaries, then it should still
>> work.  If you do, then the libc++ and libstdc++ symbols will be
>> mangled differently and so you will get link-time errors.
>>
>> In theory, if it links it should run...
>>
> 
> And in practice, it is broken.
> 
> http://lists.freebsd.org/pipermail/freebsd-current/2013-November/046565.html
> 
> QED

Trying to migrate to 10, I would like to keep octave. Have you found
anything new? Having build the port and all dependencies with standard
options, octave is segfaulting for me, too. Anyhow, I can run octave with:

env LD_PRELOAD=/usr/lib/libc++.so.1 octave

Some very light testing indicates that it is working. Of course, this is
not ideal.

Maybe this gives a clue how to fix the octave port properly.

Cheers,
Jan Henrik
Received on Wed Nov 27 2013 - 17:31:54 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:44 UTC