public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "david dot nospam dot hopwood at blueyonder dot co dot uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/20705] New: -pthread should enable all options required to use pthreads on all platforms Date: Thu, 31 Mar 2005 18:41:00 -0000 [thread overview] Message-ID: <20050331184113.20705.david.nospam.hopwood@blueyonder.co.uk> (raw) The lack of a portable option to enable pthreads is a significant annoyance. It is mentioned in bug 8888, and bug 18788 is also relevant, but those are separate bugs. See also the discussion in <http://groups.google.co.uk/groups?threadm=8764z82jd8.fsf%40qrnik.zagroda>. Workaround: use autoconf with <http://ac-archive.sourceforge.net/Installed_Packages/acx_pthread.html>. This is not suitable for all projects. -- Summary: -pthread should enable all options required to use pthreads on all platforms Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: david dot nospam dot hopwood at blueyonder dot co dot uk CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20705
next reply other threads:[~2005-03-31 18:41 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-03-31 18:41 david dot nospam dot hopwood at blueyonder dot co dot uk [this message] 2005-03-31 19:34 ` [Bug driver/20705] " pinskia at gcc dot gnu dot org 2005-03-31 22:04 ` david dot nospam dot hopwood at blueyonder dot co dot uk 2005-07-15 21:19 ` pinskia at gcc dot gnu dot org 2005-07-29 11:02 ` david dot nospam dot hopwood at blueyonder dot co dot uk 2005-07-29 11:47 ` david dot nospam dot hopwood at blueyonder dot co dot uk
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=20050331184113.20705.david.nospam.hopwood@blueyonder.co.uk \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).