public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nptl/14569] New: libpthread.a isn't linked in properly
Date: Mon, 10 Sep 2012 21:47:00 -0000	[thread overview]
Message-ID: <bug-14569-131@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=14569

             Bug #: 14569
           Summary: libpthread.a isn't linked in properly
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: nptl
        AssignedTo: unassigned@sourceware.org
        ReportedBy: hjl.tools@gmail.com
                CC: drepper.fsp@gmail.com
    Classification: Unclassified


[hjl@gnu-32 tmp]$  gcc tst-raise1-static.o -static -v -mx32 -pthread 
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.7.1/lto-wrapper
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla
--enable-bootstrap --enable-shared --enable-threads=posix
--enable-checking=release --disable-build-with-cxx
--disable-build-poststage1-with-cxx --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-gnu-unique-object
--enable-linker-build-id --with-linker-hash-style=gnu
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto --enable-plugin
--enable-initfini-array --enable-java-awt=gtk --disable-dssi
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre
--enable-libgcj-multifile --enable-java-maintainer-mode
--with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib
--with-ppl --with-cloog --with-tune=generic --with-arch_32=i686
--with-multilib-list=m32,m64,mx32 --build=x86_64-redhat-linux
Thread model: posix
gcc version 4.7.1 20120629 (Red Hat 4.7.1-1) (GCC) 
COMPILER_PATH=/usr/libexec/gcc/x86_64-redhat-linux/4.7.1/:/usr/libexec/gcc/x86_64-redhat-linux/4.7.1/:/usr/libexec/gcc/x86_64-redhat-linux/:/usr/lib/gcc/x86_64-redhat-linux/4.7.1/:/usr/lib/gcc/x86_64-redhat-linux/
LIBRARY_PATH=/usr/lib/gcc/x86_64-redhat-linux/4.7.1/x32/:/usr/lib/gcc/x86_64-redhat-linux/4.7.1/../../../../libx32/:/lib/../libx32/:/usr/lib/../libx32/:/usr/lib/gcc/x86_64-redhat-linux/4.7.1/:/usr/lib/gcc/x86_64-redhat-linux/4.7.1/../../../:/lib/:/usr/lib/
COLLECT_GCC_OPTIONS='-static' '-v' '-mx32' '-pthread' '-mtune=generic'
'-march=x86-64'
 /usr/libexec/gcc/x86_64-redhat-linux/4.7.1/collect2 --build-id --no-add-needed
--hash-style=gnu -m elf32_x86_64 -static
/usr/lib/gcc/x86_64-redhat-linux/4.7.1/../../../../libx32/crt1.o
/usr/lib/gcc/x86_64-redhat-linux/4.7.1/../../../../libx32/crti.o
/usr/lib/gcc/x86_64-redhat-linux/4.7.1/x32/crtbeginT.o
-L/usr/lib/gcc/x86_64-redhat-linux/4.7.1/x32
-L/usr/lib/gcc/x86_64-redhat-linux/4.7.1/../../../../libx32 -L/lib/../libx32
-L/usr/lib/../libx32 -L/usr/lib/gcc/x86_64-redhat-linux/4.7.1
-L/usr/lib/gcc/x86_64-redhat-linux/4.7.1/../../.. tst-raise1-static.o
--start-group -lgcc -lgcc_eh -lpthread -lc --end-group
/usr/lib/gcc/x86_64-redhat-linux/4.7.1/x32/crtend.o
/usr/lib/gcc/x86_64-redhat-linux/4.7.1/../../../../libx32/crtn.o
/usr/lib/gcc/x86_64-redhat-linux/4.7.1/../../../../libx32/libpthread.a(libpthread.o):
In function `sem_open':
(.text+0x6988): warning: the use of `mktemp' is dangerous, better use `mkstemp'

-lpthread is placed in --start-group -lgcc -lgcc_eh -lpthread -lc --end-group.
glibc tests should do the same.  It is important to properly test
statically linked libpthread.

-- 
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-09-10 21:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-10 21:47 hjl.tools at gmail dot com [this message]
2012-09-28  7:36 ` [Bug nptl/14569] " davem at davemloft dot net
2012-09-28  7:37 ` davem at davemloft dot net
2014-06-17  4:34 ` fweimer at redhat dot com
2015-09-15 15:37 ` cvs-commit at gcc dot gnu.org
2015-09-15 21:34 ` cvs-commit at gcc dot gnu.org
2015-09-16  0:12 ` cvs-commit at gcc dot gnu.org
2015-09-16 12:47 ` cvs-commit at gcc dot gnu.org
2015-09-16 12:54 ` cvs-commit at gcc dot gnu.org
2015-09-16 18:17 ` cvs-commit at gcc dot gnu.org
2015-09-16 19:43 ` cvs-commit at gcc dot gnu.org
2015-09-16 20:01 ` cvs-commit at gcc dot gnu.org
2015-09-24 15:52 ` cvs-commit at gcc dot gnu.org

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-14569-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).