From: Eric Botcazou <ebotcazou@libertysurf.fr>
To: Josh <sundog@mindspring.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Bootstrap failure on Sparc Solaris2.8
Date: Tue, 27 May 2003 19:13:00 -0000 [thread overview]
Message-ID: <200305272102.52792.ebotcazou@libertysurf.fr> (raw)
In-Reply-To: <2441889.1054058536778.JavaMail.nobody@wamui08.slb.atl.earthlink.net>
> There is in fact a pthread.h header file in my $(objdir)/gcc/include
> directory
Ok, this means that at least one fix was applied to the header. Now could you
post the definitions of the two macros at stake, i.e
PTHREAD_MUTEX_INITIALIZER
and
PTHREAD_COND_INITIALIZER,
as they appear in this header file, including any surrounding #if/#endif?
--
Eric Botcazou
next prev parent reply other threads:[~2003-05-27 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 18:08 Josh
2003-05-27 19:13 ` Eric Botcazou [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-28 20:43 Josh Loeb
2003-05-28 20:53 ` Albert Chin
2003-05-27 17:08 Josh
2003-05-27 17:51 ` Eric Botcazou
2003-05-23 13:59 Josh
2003-05-23 16:14 ` Eric Botcazou
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=200305272102.52792.ebotcazou@libertysurf.fr \
--to=ebotcazou@libertysurf.fr \
--cc=gcc@gcc.gnu.org \
--cc=sundog@mindspring.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).