Re: Base libc++ missing symbol

2023-10-10 Thread Konstantin Belousov
On Tue, Oct 10, 2023 at 06:53:00PM -0700, Alan Somers wrote: > On Tue, Oct 10, 2023 at 3:10 PM Tomoaki AOKI > wrote: > > > > On Tue, 10 Oct 2023 18:09:04 + > > jbo@insane.engineer wrote: > > > > > I've updated to commit c11f71789d7d8f741243c21add8d7c5f0ecea03e > > > and the problem is still p

Re: Base libc++ missing symbol

2023-10-10 Thread Alan Somers
On Tue, Oct 10, 2023 at 3:10 PM Tomoaki AOKI wrote: > > On Tue, 10 Oct 2023 18:09:04 + > jbo@insane.engineer wrote: > > > I've updated to commit c11f71789d7d8f741243c21add8d7c5f0ecea03e > > and the problem is still present. > > > > > So far I've never reproduced your problem or anything like i

Re: Base libc++ missing symbol

2023-10-10 Thread Tomoaki AOKI
On Tue, 10 Oct 2023 18:09:04 + jbo@insane.engineer wrote: > I've updated to commit c11f71789d7d8f741243c21add8d7c5f0ecea03e > and the problem is still present. > > > So far I've never reproduced your problem or anything like it. > > > > (I prefer testing official builds for problem isolation

Re: Base libc++ missing symbol

2023-10-10 Thread Alan Somers
BTW, this same problem is already in bugzilla at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272642 . I too am experiencing it, on a system that I upgraded with freebsd-update from 13.2-RELEASE to 14.0-BETA4. And I'm at a loss to understand what's going on, because elfdump -a /lib/libc++.so

Re: Base libc++ missing symbol

2023-10-10 Thread jbo
I've updated to commit c11f71789d7d8f741243c21add8d7c5f0ecea03e and the problem is still present. > So far I've never reproduced your problem or anything like it. > > (I prefer testing official builds for problem isolation. If > only my personal builds fail, then it is likely my build's > problem

Re: Base libc++ missing symbol

2023-10-08 Thread Mark Millard
wrote on Date: Sun, 08 Oct 2023 18:13:16 UTC : > > The procedure of seeing if the a.out is produced without complaint > > might still be useful. > > The program compiles & links fine, but then also fails to run: > > ld-elf.so.1: Undefined symbol "_ZTVNSt3__13pmr25monotonic_buffer_resourceE" >

Re: Base libc++ missing symbol

2023-10-08 Thread jbo
> The procedure of seeing if the a.out is produced without complaint > might still be useful. The program compiles & links fine, but then also fails to run: ld-elf.so.1: Undefined symbol "_ZTVNSt3__13pmr25monotonic_buffer_resourceE" referenced from COPY relocation in /usr/home/jbo/junk/a.out I

Re: Base libc++ missing symbol

2023-10-03 Thread Tomoaki AOKI
On Mon, 2 Oct 2023 23:53:42 +0200 Dimitry Andric wrote: > On 2 Oct 2023, at 22:00, Joel Bodenmann 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'v

Re: Base libc++ missing symbol

2023-10-02 Thread Mark Millard
On Oct 2, 2023, at 15:56, Mark Millard wrote: > Joel Bodenmann wrote on > Date: Mon, 02 Oct 2023 20:00:29 UTC : > >> 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

RE: Base libc++ missing symbol

2023-10-02 Thread Mark Millard
Joel Bodenmann wrote on Date: Mon, 02 Oct 2023 20:00:29 UTC : > 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

Re: Base libc++ missing symbol

2023-10-02 Thread Dimitry Andric
On 2 Oct 2023, at 22:00, Joel Bodenmann 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 th

Base libc++ missing symbol

2023-10-02 Thread Joel Bodenmann
Hi, 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 Q