This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/14327] New: pthread uses mktemp(), causing link-time warning
- From: "nyh at math dot technion.ac.il" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Tue, 03 Jul 2012 13:43:10 +0000
- Subject: [Bug libc/14327] New: pthread uses mktemp(), causing link-time warning
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=14327
Bug #: 14327
Summary: pthread uses mktemp(), causing link-time warning
Product: glibc
Version: 2.15
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: unassigned@sourceware.org
ReportedBy: nyh@math.technion.ac.il
CC: drepper.fsp@gmail.com
Classification: Unclassified
When *statically* linking a program with -lpthread, I get the following
warning:
/usr/lib/gcc/x86_64-redhat-linux/4.7.0/../../../../lib64/libpthread.a(libpthread.o):
In function `sem_open':
(.text+0x67f8): warning: the use of `mktemp' is dangerous, better use `mkstemp'
This warning is annoying, because it implies there something wrong with
libpthread. Can glibc use mkstemp like the warning suggests? Or do something
else to avoid this warning from the linker?
I'm seeing this problem on Fedora 17, gcc 4.7.0, glibc 2.15.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.