* Florian Weimer: > <limits.h> is included indirectly in the #pragma GCC visibility hidden > block. With glibc 2.34, <limits.h> needs a declaration of the sysconf > function, and including it under hidden visibility turns other calls > to sysconf into hidden references, leading to a linker failure. > > libgomp/ChangeLog: > > * libgomp.h: Include <limits.h>. > > --- > libgomp/libgomp.h | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/libgomp/libgomp.h b/libgomp/libgomp.h > index 8d25dc8e2a8..1fe209429d1 100644 > --- a/libgomp/libgomp.h > +++ b/libgomp/libgomp.h > @@ -46,6 +46,7 @@ > #include "libgomp-plugin.h" > #include "gomp-constants.h" > > +#include <limits.h> > #ifdef HAVE_PTHREAD_H > #include <pthread.h> > #endif
I think this is a real libgomp bug, but if this glibc patch is accepted, at least libgomp will build again: Reduce <limits.h> pollution due to dynamic PTHREAD_STACK_MIN <https://sourceware.org/pipermail/libc-alpha/2021-July/128940.html> So while I still think libgomp should be fixed, it won't need backporting to release branches (assuming the glibc workaround goes in, of course). Thanks, Florian
