public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/8888: Linking shared libraries with -pthread fails to link to libpthread
Date: Tue, 10 Dec 2002 06:46:00 -0000	[thread overview]
Message-ID: <20021210144625.18966.qmail@sources.redhat.com> (raw)

The following reply was made to PR other/8888; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Sebastian Wilhelmi <wilhelmi@ira.uka.de>
Cc: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>
Subject: Re: other/8888: Linking shared libraries with -pthread fails to link
 to libpthread
Date: Tue, 10 Dec 2002 08:44:55 -0600 (CST)

 > the man page for gcc-3.2 says:
 > 
 >        -pthread
 >            Adds support for multithreading with the pthreads library.
 >            This option sets flags for both the preprocessor and linker.
 
 Sorry, I overlooked this (the gcc2.95 info pages have no documentation on 
 -pthread whatsoever). Nevertheless, it does not say specifically that it 
 links with libpthread. It might just select thread-safe variants of other 
 libraries, in case there are different versions.
 
 Though...
 
 > Also for non-shared binaries gcc does the right thing now, but not for
 > shared objects, why is that?
 
 ...this seems inconsistent. I will thus reopen the report.
 
 To workaround, you could of course just pass "-pthread -lpthread" on the 
 linker line. This is basically also what I always do.
 
 > P.S.: I have no write access to GNATS, so I could only write this
 > e-mail, or is there some way to attach that message to the bug report?
 
 As long as you CC: gcc-gnats@gcc.gnu.org, everything is fine.
 
 Regards
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth
 
 


             reply	other threads:[~2002-12-10 14:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10  6:46 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-10 20:39 bangerth
2003-03-09 17:36 Hans-Peter Nilsson
2002-12-10 11:46 Joseph S. Myers
2002-12-10 11:46 Wolfgang Bangerth
2002-12-10 11:40 bangerth
2002-12-10 11:36 Wolfgang Bangerth
2002-12-10 11:06 Joseph S. Myers
2002-12-10  6:48 bangerth
2002-12-10  6:36 Sebastian Wilhelmi
2002-12-10  6:13 bangerth
2002-12-10  4:16 wilhelmi

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=20021210144625.18966.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /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).