On 3/11/25 15:24, Jonathan Wakely wrote:
On Tue, 11 Mar 2025 at 15:55, Dennis Clarke wrote:
On 3/11/25 05:48, Jonathan Wakely wrote:
On Tue, 11 Mar 2025 at 01:17, Dennis Clarke via Gcc-help
<gcc-help@xxxxxxxxxxx> wrote:
<snip>
...
triton$ which g++
/opt/bw/gcc14/bin/g++
<more snippage>
Well that tells a story right there.
Indeed!
$ realpath -m /opt/bw/lib/gcc/x86_64-linux-gnu/14.2.0/../../../../../../include/c++/14.2.0
/include/c++/14.2.0
That's not where they're installed.
Yup ... I see it now.
* * * looks to be a good compiler * * *
see https://gcc.gnu.org/pipermail/gcc-testresults/2025-March/840512.html
I'm curious why these are failing:
FAIL: std/time/exceptions.cc -std=gnu++20 execution test
FAIL: std/time/exceptions.cc -std=gnu++26 execution test
FAIL: std/time/time_zone/get_info_local.cc -std=gnu++20 execution test
FAIL: std/time/time_zone/get_info_local.cc -std=gnu++26 execution test
FAIL: std/time/time_zone/get_info_sys.cc -std=gnu++20 execution test
FAIL: std/time/time_zone/get_info_sys.cc -std=gnu++26 execution test
FAIL: std/time/tzdb/1.cc -std=gnu++20 execution test
FAIL: std/time/tzdb/1.cc -std=gnu++26 execution test
FAIL: std/time/zoned_time/1.cc -std=gnu++20 execution test
FAIL: std/time/zoned_time/1.cc -std=gnu++26 execution test
FAIL: std/time/zoned_time/custom.cc -std=gnu++20 execution test
FAIL: std/time/zoned_time/custom.cc -std=gnu++26 execution test
FAIL: std/time/zoned_time/io.cc -std=gnu++20 execution test
FAIL: std/time/zoned_time/io.cc -std=gnu++26 execution test
FAIL: libstdc++-prettyprinters/chrono.cc execution test
FAIL: libstdc++-prettyprinters/chrono.cc execution test
Good question. However I think the real issue was way back in the
configure stage where I had --libdir=/opt/bw/lib in there. That
really is not needed.
Yup. The testresults are run against the just-built compiler in the
build tree, before it's installed. So they aren't affected by any
oddities in the installation layout. The headers can always be found
in the build tree because they're at predictable locations.
I'm a bit surprised it broke though, I would expect the implicit
include paths to take the --libdir setting into account. That seems
like a bug, albeit not a very high priority one because --libdir not
being a subdirectory of --prefix is probably uncommon.
I am going to re-bootstrap without that.
I see from your follow-up that it fixed your original issue. I'm still
curious why all the C++ time zone tests fail. Do you have an
incomplete/modified tzdata file on the system? If no tzdata files are
found, then a bundled copy of tzdata should get used, so if they're
failing that suggests your system does have the data but it's
incomplete.
Could you please look in the
x86_64-pc-linux-gnu/libstdc++-v3/testsuite/libstdc++.log file and
search for ^FAIL and see what the errors are?
I will dig into that and look around. Thank you kind Sir !
--
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
