public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nyh at math dot technion.ac.il" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/14327] New: pthread uses mktemp(), causing link-time warning
Date: Tue, 03 Jul 2012 13:43:00 -0000	[thread overview]
Message-ID: <bug-14327-131@http.sourceware.org/bugzilla/> (raw)

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.


             reply	other threads:[~2012-07-03 13:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03 13:43 nyh at math dot technion.ac.il [this message]
2012-07-03 13:55 ` [Bug libc/14327] " polacek at redhat dot com
2012-07-03 14:02 ` aj at suse dot de
2012-07-03 14:16 ` nyh at math dot technion.ac.il
2012-07-03 23:15 ` bugdal at aerifal dot cx
2013-01-16 14:59 ` schwab@linux-m68k.org
2013-05-15  9:45 ` schwab@linux-m68k.org
2014-06-13 18:50 ` fweimer at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-14327-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).