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>
...
<snip>
-v would be a lot more interesting and useful here than --version
<snip>
Yep .. that works like a charm.
I'm curious why these are failing:
Yes indeed and that is the reason for this email/post to our favorite
over flowing maillist of joy. :)
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
This is a default out of the box install of Devuan Linux which is just a
really fantastic Linux distro based on the Debian goodness. However the
Microsoft SystemD has been entirely removed.
OKay .. so I will get off the damn soapbox. This is a default nothing
fancy install with the initial build-essentials stuff so I can bootstrap
what I want where I want and then maybe ( silly dream? ) get the NVidia
CUDA stuff working. That was the plan and I need my own Linux kernel and
that means I may as well bootstrap GCC also. The NVidia drivers on Linux
are really gnarly if you go with a kernel past 6.1.x at all.
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 shall refrain from that silly --libdir option.
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.
Which I did. However there are some tests that fail strangely.
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?
t$ find . -type f -name libstdc++.log
./x86_64-linux-gnu/libstdc++-v3/testsuite/libstdc++.log
t$
t$ wc -l ./x86_64-linux-gnu/libstdc++-v3/testsuite/libstdc++.log
115033 ./x86_64-linux-gnu/libstdc++-v3/testsuite/libstdc++.log
t$
Yikes .... 115033 lines.
t$
t$ grep '^FAIL' ./x86_64-linux-gnu/libstdc++-v3/testsuite/libstdc++.log
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/exceptions.cc -std=gnu++20 execution test
FAIL: std/time/exceptions.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
t$
No idea why these are failing.
I think the timezone data is complete but who knows ?
t$ ls -abp /usr/share/zoneinfo/
./ EET Hongkong Mexico/ ROK
../ Egypt HST MST Singapore
Africa/ Eire Iceland MST7MDT Turkey
America/ EST Indian/ Navajo tzdata.zi
Antarctica/ EST5EDT Iran NZ UCT
Arctic/ Etc/ iso3166.tab NZ-CHAT Universal
Asia/ Europe/ Israel Pacific/ US/
Atlantic/ Factory Jamaica Poland UTC
Australia/ GB Japan Portugal WET
Brazil/ GB-Eire Kwajalein posix/ W-SU
Canada/ GMT leapseconds posixrules zone1970.tab
CET GMT+0 leap-seconds.list PRC zone.tab
Chile/ GMT-0 Libya PST8PDT Zulu
CST6CDT GMT0 localtime right/
Cuba Greenwich MET ROC
t$
The machine has localtime linked to UTC for reasons of sanity :
t$ ls -lad /etc/localtime
lrwxrwxrwx 1 root root 27 Mar 6 00:35 /etc/localtime ->
/usr/share/zoneinfo/Etc/UTC
t$
Generally I have my TZ env var set to GMT0 :
t$ echo $TZ
GMT0
t$
Perhaps I should have that as UTC ?
I have ntpd running and getting time from four awesome servers :
t$ ntpq -pn -4 172.16.35.6
remote refid st t when poll reach
delay offset jitter
===========================================================================================
+209.87.233.53 209.87.233.52 2 u 720 1024 337
38.5701 -0.3270 4.7857
+132.246.11.227 132.246.11.231 2 u 180 1024 377
24.7986 0.9726 3.2881
+128.100.100.128 206.108.0.133 2 u 573 1024 357
17.5598 0.2807 5.0049
*2602:fde5:2a::13 .PTP0. 1 u 946 1024 377
18.4070 1.5502 3.1148
t$
There is even a stratum 1 clock source in there.
So is there a way to run a single test and just get all the verbosity
one could ask for?
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
