public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@dm.cobaltmicro.com>
To: law@cygnus.com
Cc: parkes@sierravista.com, egcs@cygnus.com
Subject: Re: configure --disable-threads
Date: Tue, 03 Nov 1998 23:34:00 -0000	[thread overview]
Message-ID: <199811040413.UAA17274@dm.cobaltmicro.com> (raw)
In-Reply-To: <5865.910152172@upchuck>

   Date: Tue, 03 Nov 1998 21:02:52 -0700
   From: Jeffrey A Law <law@upchuck.cygnus.com>

   David -- the issue at hand is if --disable-threads or
   --enable-threads=no is specified that the sparc & PA port will try
   to use pthreads if pthread.h exists because enable_threads as an
   empty value in the configure cases for the sparc & PA targets.

   It sounds a little backwards to me, but I don't know if that was
   the behavior you intended or not :-)

It does indeed seem hokey.

What I imagine is being attempted is that if nothing was specified
about the matter on the configure command line, and pthread.h exists,
the user probably wants thread support enabled in the build  by
default.

I suppose there is a better way to achieve this than what we are doing
now.

Note that only the sparc solaris targets do this, and in fact I never
put that weird code there pertaining to this.

Later,
David S. Miller
davem@dm.cobaltmicro.com

      reply	other threads:[~1998-11-03 23:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-27  9:04 Steven Parkes
1998-10-30  7:31 ` Jeffrey A Law
1998-11-02 19:39   ` Steven Parkes
1998-11-03 23:34     ` Jeffrey A Law
1998-11-03 23:34       ` David S. Miller [this message]

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=199811040413.UAA17274@dm.cobaltmicro.com \
    --to=davem@dm.cobaltmicro.com \
    --cc=egcs@cygnus.com \
    --cc=law@cygnus.com \
    --cc=parkes@sierravista.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).