On 2021-03-11 12:12, Oleg Smolsky wrote:
On 2021-03-11 10:01, Florian Weimer wrote:
* Oleg Smolsky via Gcc-help:
Clearly the new build is not quite the same as the old one... but
which one is correct for Linux/x86-64? And what controls this
variance? It looks like glibc does not have a flag to control TLS any
more...
You need to figure out why _GLIBCXX_HAVE_TLS was not detected at
configure time. See config/tls.m4. There is likely something in
config.log.
Thank you for the pointers, Florian and Jonathan!
I'm trying to figure out where the new build went awry. So far I have
these crumbs:
....
I have another data point - I am able to build GCC fully and correctly
(with TLS) on another VM using the same recipe. The difference between
these VMs is the kernel package. The working case uses the stock Ubuntu
kernel and the broken case uses a newer package (seemingly official).
The working case: linux-image-4.4.0-83-generic and the corresponding
"headers" package.
The broken case: linux-image-4.15.0-99-generic and no kernel headers (I
install them into the sysroot anyway).
Is there a way to figure out whether it's GCC that thinks there is no
TLS support or GLibc?
Thanks!
Oleg.
