public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@arthur.rhein-neckar.de>
To: egcs@cygnus.com
Subject: Re: Possible Showstopper
Date: Thu, 04 Dec 1997 03:06:00 -0000	[thread overview]
Message-ID: <u8afehzc7g.fsf@arthur.rhein-neckar.de> (raw)
In-Reply-To: <199712031733.JAA25765@atrus.synopsys.com>

>>>>> Joe Buck writes:

>> In message < 199712022253.OAA06067@supernova.earthlink.net >you write:
>> > 
>> > The new 971201 snapshot did not fix the problem I am having on my
>> > RedHat 5.0 system (i686-pc-linux-gnu).  In particular, make check
>> > fails horribly for many C++ tests, like this:
>> With RedHat only being out for 2 days I think the way to go is to make a minor
>> release in a week or so to fix this specific problem.
>> 
>> > At the very least, something needs to go in the release notes about
>> > this.
>> Agreed.

 > Will it work around the problem if users add -lpthread to their link
 > line?
That might work but is unneccassary.
 > (Yes, it sucks that we got burned by 5.0, but we did want to support
 > popular Linux distributions).

A better solution is to change
linuxthreads/sysdeps/pthread/libc-lock.h (it's installed as
/usr/include/libc-lock.h) with the following patch (it's a bug in the
current glibc 2.0.5c):

Andreas

--- /usr/glibc/glibc-2.0.5/glibc-2.0.5c-src/linuxthreads/sysdeps/pthread/libc-lo
ck.h    Mon Aug 18 16:01:50 1997
+++ linuxthreads/sysdeps/pthread/libc-lock.h    Wed Nov 19 00:47:11 1997

@@ -166,6 +166,11 @@
 /* We need portable names for some functions.  E.g., when they are
    used as argument to __libc_cleanup_region_start.  */
 # define __libc_mutex_unlock __pthread_mutex_unlock
+#else
+# ifdef __ELF__
+#  pragma weak _pthread_cleanup_push_defer
+#  pragma weak _pthread_cleanup_pop_restore
+# endif
 #endif
 
 #endif /* bits/libc-lock.h */


-- 
 Andreas Jaeger   aj@arthur.rhein-neckar.de    jaeger@informatik.uni-kl.de
  for pgp-key finger ajaeger@alma.student.uni-kl.de
    http://www.student.uni-kl.de/~ajaeger/

  parent reply	other threads:[~1997-12-04  3:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-02 21:17 Mark Mitchell
1997-12-02 22:54 ` Jeffrey A Law
1997-12-03 10:46   ` Joe Buck
1997-12-03 12:54     ` Jeffrey A Law
1997-12-03 15:32       ` Mark Mitchell
1997-12-03 16:29       ` genattr Error code 139 Dax Kelson
1997-12-03 20:29         ` Jeffrey A Law
1997-12-04  3:06     ` Andreas Jaeger [this message]
1997-12-03  5:14 ` Possible Showstopper Neal Becker
1997-12-04 18:45 G. Sumner Hayes
1997-12-05  4:21 ` Wolfram Gloger
1997-12-05  8:27   ` Paul Henning
1997-12-05  8:27 ` Andreas Jaeger
1997-12-05  8:27   ` G. Sumner Hayes

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=u8afehzc7g.fsf@arthur.rhein-neckar.de \
    --to=aj@arthur.rhein-neckar.de \
    --cc=egcs@cygnus.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).