Re: Base libc++ missing symbol

On Mon, 2 Oct 2023 23:53:42 +0200
Dimitry Andric <dim@FreeBSD.org> wrote:

> On 2 Oct 2023, at 22:00, Joel Bodenmann <jbo@FreeBSD.org> wrote:
> > 
> > It seems like I finally managed to hose a FreeBSD system.
> > The machine in question is my workstation at home. It has been running
> > stable/13 without any problems. Yesterday I've updated to
> > ef295f69abbffb3447771a30df6906ca56a5d0c0 and since then I'm getting an
> > undefined symbol on anything using Qt:
> > 
> > ld-elf.so.1: /usr/local/lib/qt5/libQt5Widgets.so.5: Undefined symbol
> > "_ZTVNSt3__13pmr25monotonic_buffer_resourceE"
> > 
> > Unless I'm missing something, it would seem like my base libc++
> > is missing the pmr::monotonic_buffer_resource symbol.
> 
> It should be in libc++.so.1, you can check this with grep. If it is not
> there, there might have been some issue installing a newly built copy of
> libc++.so.1 into your file system? You could check if there is a
> memory_resource.pico file in your /usr/obj; it should typically be in
> /usr/obj/usr/src/amd64.amd64/lib/libc++. The libc++.so.1 file in that
> directory should definitely have the symbol.
> 
> Another possibility is that Qt is doing something strange when loading
> their shared libraries. It has been known to perform weird tricks...
> 
> -Dimitry

Qt (at least 5) has mysteryous oddness on updates.

Sometimes deleting or moving outside any library paths Qt related files
in /usr/local/lib/pkg is sufficient.

Sometimes requires all Qt ports (any of ones included in its metaport)
to be fully rebuilt in exactly correct order.

Sometimes even doing both is insufficient and rebuilding base is forced.

See Bug 268652 [1] for details. I'm intentionally keep this opened, as
this problem randomly happenes on Qt5 updates (not everytime).


[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268652

-- 
Tomoaki AOKI    <junchoon@dec.sakura.ne.jp>