public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: mengel@users.sourceforge.net
To: gcc-gnats@gcc.gnu.org
Subject: target/9330: small alphaev56-dec-osf5.1 --enable-threads=posix problem
Date: Wed, 15 Jan 2003 18:06:00 -0000	[thread overview]
Message-ID: <20030115175844.32613.qmail@sources.redhat.com> (raw)


>Number:         9330
>Category:       target
>Synopsis:       small alphaev56-dec-osf5.1 --enable-threads=posix problem
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jan 15 10:06:00 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Marc Mengel
>Release:        unknown-1.0
>Organization:
>Environment:
alphaev56-dec-osf5.1 configured with --enable-threads=posix
>Description:
alphaev56-dec-osf5.1 configured with --enable-threads=posix
The /usr/include/pthreads.h file triggers an #error directive
if _REENTRANT is not defined when you include it.

I suggest the attached patch, which #defines _REENTRANT in gthr_posix.h when __osf__ is defined, just before including
pthread.h
>How-To-Repeat:
On a DEC Unix, er,Compaq Tru-64, er whatever they call
it now, where cc -V reports:
Compaq C V6.4-014 on Compaq Tru64 UNIX V5.1A (Rev. 1885)
do:
-----
configure --enable-threads=posix
make bootstrap
------
You get an #error trip when including pthreads.h
>Fix:
Apply attached patch to #define _REENTRANT
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="diff"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="diff"

KioqIGd0aHItcG9zaXguaC5vcmlnCVdlZCBKYW4gMTUgMTE6NDY6MTEgMjAwMwotLS0gZ3Roci1w
b3NpeC5oCVdlZCBKYW4gMTUgMTE6Mjk6MjAgMjAwMwoqKioqKioqKioqKioqKioKKioqIDM0LDM5
ICoqKioKLS0tIDM0LDQzIC0tLS0KICAKICAjZGVmaW5lIF9fR1RIUkVBRFMgMQogIAorICNpZmRl
ZiBfX29zZl9fCisgI2RlZmluZSBfUkVFTlRSQU5UCisgI2VuZGlmCisgCiAgI2luY2x1ZGUgPHB0
aHJlYWQuaD4KICAKICB0eXBlZGVmIHB0aHJlYWRfa2V5X3QgX19ndGhyZWFkX2tleV90Owo=


                 reply	other threads:[~2003-01-15 18:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030115175844.32613.qmail@sources.redhat.com \
    --to=mengel@users.sourceforge.net \
    --cc=gcc-gnats@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).