public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ljrittle@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	harri.pasanen@trema.com, ljrittle@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: bootstrap/3314: --enable-threads does not seem to be working for HP-UX 11.00
Date: Thu, 21 Jun 2001 14:34:00 -0000	[thread overview]
Message-ID: <20010621213400.29361.qmail@sourceware.cygnus.com> (raw)

Synopsis: --enable-threads does not seem to be working for HP-UX 11.00

Responsible-Changed-From-To: unassigned->ljrittle
Responsible-Changed-By: ljrittle
Responsible-Changed-When: Thu Jun 21 14:33:59 2001
Responsible-Changed-Why:
    Mine.
State-Changed-From-To: open->analyzed
State-Changed-By: ljrittle
State-Changed-When: Thu Jun 21 14:33:59 2001
State-Changed-Why:
    This is known but not well-documented behavior.
    On the mainline in gcc/doc/install.texi, the issue is
    now clarified:
    
      In general, the best (and, in many cases, the only known) threading
      model available will be configured for use.  Beware that on some
      systems, gcc has not been taught what threading models are generally
      available for the system.  In this case, @option{--enable-threads} is an
      alias for @option{--enable-threads=single}.
    
    It would be better to abort the early configuration with
    an error in this case than to silently drop a user-provided
    switch, but the patches to make that so have not been
    fully submitted or applied yet.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3314&database=gcc


             reply	other threads:[~2001-06-21 14:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-21 14:34 ljrittle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14  8:16 Dara Hazeghi
2002-02-18 15:01 ljrittle
2002-01-15  8:46 Craig Rodrigues
2002-01-14 19:16 Craig Rodrigues
2001-06-21  1:36 harri.pasanen

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=20010621213400.29361.qmail@sourceware.cygnus.com \
    --to=ljrittle@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=harri.pasanen@trema.com \
    --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).