This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/47375] GETLOG not threadsafe, causes warnings/wrong-code with static linking
- From: "burnus at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 20 Jan 2011 13:38:48 +0000
- Subject: [Bug libfortran/47375] GETLOG not threadsafe, causes warnings/wrong-code with static linking
- Auto-submitted: auto-generated
- References: <bug-47375-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47375
--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-01-20 13:38:44 UTC ---
Documentation for getpwuid_r from POSIX:
http://pubs.opengroup.org/onlinepubs/009695399/functions/getpwuid.html
and for LINUX, which contains a getpwuid_r example:
http://www.kernel.org/doc/man-pages/online/pages/man3/getpwnam.3.html
(In reply to comment #2)
> I quickly tried to link a C program statically that uses getpwuid_r. It has the
> same problem. I guess it is unavoidable.
Seems so - but fortunately, the exact version requirements do not seem to be
that strict: using a -static-ally linked test case (from kernel.org, cf. link),
linked on a GLIBC 2.11.3 system worked on a system with glibc-2.5-49.el5_5.2.