From nobody Tue Oct 10 18:09:04 2023 X-Original-To: stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4S4kSF26Ndz4x6cD for ; Tue, 10 Oct 2023 18:09:17 +0000 (UTC) (envelope-from jbo@insane.engineer) Received: from mail-4323.proton.ch (mail-4323.proton.ch [185.70.43.23]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4S4kSC1WBfz3Hkx for ; Tue, 10 Oct 2023 18:09:14 +0000 (UTC) (envelope-from jbo@insane.engineer) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=insane.engineer header.s=protonmail2 header.b="E50V/kbj"; spf=pass (mx1.freebsd.org: domain of jbo@insane.engineer designates 185.70.43.23 as permitted sender) smtp.mailfrom=jbo@insane.engineer; dmarc=pass (policy=none) header.from=insane.engineer DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=insane.engineer; s=protonmail2; t=1696961351; x=1697220551; bh=Sl6hgVXKCsZS8RIO13wusDCfUhkWxD58JXMv1GxiCe0=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=E50V/kbj8jqxUV9znLWzMLwHSW1vyJ/AXq1YUhyQpE52hycu+uNsImoRLq0mK0Axc IJEJRWowus4malGAhfW25liRag1Ii2U0UJSvXuT0uqnba1/LIp83QCUBesR8N6OqWN eJLMycotSawrOzhxTszMTqIGPKNLNq2YrqIuM1HVb+CLPNQZZxnljjISyQnqmHlRFI Uvd5L+QWBHj72LqrfS50IjWqpl6yX4eZPHuoCyQ9qqUCbIHMx0NEXi9SteQ7vcGkB4 wNkW+WpJ6R/gJPB9FnOo7iUEzaebqT9X3ToeEE1KR1oCC1d7DZousAnooKFeQpqArl 7mkS+52E6/chg== Date: Tue, 10 Oct 2023 18:09:04 +0000 To: Mark Millard From: jbo@insane.engineer Cc: "stable@freebsd.org" Subject: Re: Base libc++ missing symbol Message-ID: In-Reply-To: <4A3F045F-3379-4651-9099-3319E4C326EE@yahoo.com> References: <4A3F045F-3379-4651-9099-3319E4C326EE.ref@yahoo.com> <4A3F045F-3379-4651-9099-3319E4C326EE@yahoo.com> Feedback-ID: 40997969:user:proton List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.40 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[insane.engineer,none]; RWL_MAILSPIKE_EXCELLENT(-0.40)[185.70.43.23:from]; R_SPF_ALLOW(-0.20)[+ip4:185.70.43.0/24]; R_DKIM_ALLOW(-0.20)[insane.engineer:s=protonmail2]; MIME_GOOD(-0.10)[text/plain]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[stable@freebsd.org]; FREEMAIL_TO(0.00)[yahoo.com]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ZERO(0.00)[0]; TO_DN_EQ_ADDR_SOME(0.00)[]; DKIM_TRACE(0.00)[insane.engineer:+]; RCPT_COUNT_TWO(0.00)[2]; FREEFALL_USER(0.00)[jbo]; ARC_NA(0.00)[]; FROM_NO_DN(0.00)[]; TO_DN_SOME(0.00)[]; ASN(0.00)[asn:62371, ipnet:185.70.43.0/24, country:CH]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4S4kSC1WBfz3Hkx I've updated to commit c11f71789d7d8f741243c21add8d7c5f0ecea03e and the problem is still present. > So far I've never reproduced your problem or anything like it. >=20 > (I prefer testing official builds for problem isolation. If > only my personal builds fail, then it is likely my build's > problem.) Yeah, I couldn't reproduce this either. I have no clue what is going on here. I'm honestly a bit lost on this one. I have not encountered anything like this before. None of my other machines are=20 displaying this problem wile running on the same stable/13 branch (and one machine even on the exact same commit). Current system info: # uname -apKU FreeBSD beefy02 13.2-STABLE FreeBSD 13.2-STABLE stable/13-n256520-c11f71789= d7d GENERIC amd64 amd64 1302508 1302508 # freebsd-version -kru 13.2-STABLE 13.2-STABLE 13.2-STABLE # c++ --version FreeBSD clang version 16.0.6 (https://github.com/llvm/llvm-project.git llvm= org-16.0.6-0-g7cbf1a259152) Target: x86_64-unknown-freebsd13.2 Thread model: posix InstalledDir: /usr/bin ------- Original Message ------- On Monday, October 9th, 2023 at 08:35, Mark Millard wro= te: >=20 >=20 > wrote on >=20 > Date: Sun, 08 Oct 2023 18:13:16 UTC : >=20 > > > The procedure of seeing if the a.out is produced without complaint > > > might still be useful. > >=20 > > The program compiles & links fine, but then also fails to run: > >=20 > > ld-elf.so.1: Undefined symbol "_ZTVNSt3__13pmr25monotonic_buffer_resour= ceE" referenced from COPY relocation in /usr/home/jbo/junk/a.out >=20 >=20 > Well, for stable/13 's recent snapshot, freshly dd'd to USB3 media, > so an official build, not a personal one that might be odd in some way: >=20 > # uname -apKU > FreeBSD generic 13.2-STABLE FreeBSD 13.2-STABLE stable/13-n256505-2464d8c= 5e296 GENERIC arm64 aarch64 1302508 1302508 >=20 > (So, after 2023-Oct-01's ef295f69abbf that you originally referenced: 202= 3-Oct-04's 2464d8c5e296.) >=20 > # c++ -v > FreeBSD clang version 16.0.6 (https://github.com/llvm/llvm-project.git ll= vmorg-16.0.6-0-g7cbf1a259152) > Target: aarch64-unknown-freebsd13.2 > Thread model: posix > InstalledDir: /usr/bin >=20 > # c++ -std=3Dc++17 -pedantic -O2 monotonic_buffer_resource.cpp >=20 > # ./a.out > t1 (default std alloc): 1.827 sec; t1/t1: 1.000 > t2 (default pmr alloc): 1.818 sec; t1/t2: 1.005 > t3 (pmr alloc no buf): 0.920 sec; t1/t3: 1.986 > t4 (pmr alloc and buf): 0.606 sec; t1/t4: 3.015 >=20 > The example is from in an aarch64 context. It does not > agree with your report. >=20 > > I made no progress on this. >=20 >=20 > So far I've never reproduced your problem or anything like it. >=20 > (I prefer testing official builds for problem isolation. If > only my personal builds fail, then it is likely my build's > problem.) >=20 > > I have reinstalled world twice (from different > > commits) and I re-installed all packages multiple times (also from diff= erent > > ports tree commits). >=20 >=20 > I suggest trying the most recent stable/13 snapshot build at > the time of the experiment. >=20 > No packages are used/needed for the monotonic_buffer_resource.cpp > test. This fits well with using a snapshot context for such a > test. >=20 > > Any other wild ideas on how to fix this? >=20 >=20 > I've no evidence about your stable/13 build/install. But the > official snapshot that I tried worked just fine. >=20 > > None of my other machines have any > > issues whatsoever running on the same or similar stable/13 commit and u= sing > > the same poudriere repository. >=20 >=20 > That, with my results, tends to suggest you have one odd ball > context that has a problematical FreeBSD build/install. Again, > I've no evidence to work with relative to that build/install. >=20 > > This is certainly not Qt5 related. I run into the exact same issue with > > anything that uses Qt6. >=20 > > Furthermore, the test program we built experiences > > the same issue without any involvement of the Qt libraries. >=20 >=20 >=20 > There was no problem for my testing of monotonic_buffer_resource.cpp > via the recent official snapshot build of stable/13 . >=20 > I've not tried to test Qt5 or Qt6, sticking with the simpler/smaller > context that you also report as failing in the odd context. I suggest > avoiding Qt5/Qt6 testing until you have a context with the > monotonic_buffer_resource.cpp test working. >=20 > =3D=3D=3D > Mark Millard > marklmi at yahoo.com