public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "G. Sumner Hayes" <sumner@collegium.adsl.net.cmu.edu>
To: egcs@cygnus.com
Subject: Re: Possible Showstopper
Date: Thu, 04 Dec 1997 18:45:00 -0000	[thread overview]
Message-ID: <19971204214913.48297@collegium.adsl.net.cmu.edu> (raw)

Andreas Jaeger (aj@arthur.rhein-neckar.de) wrote:
> --- /usr/glibc/glibc-2.0.5/glibc-2.0.5c-src/linuxthreads/sysdeps/pthread/libc-lock.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 */

Applying this patch does not fix things here on Red Hat 5.0.  I still
need to link all C++ programs against the pthreads library.

Should egcs and/or glibc be rebuilt after applying this?

-Sumner

-- 
rage, rage against the dying of the light

             reply	other threads:[~1997-12-04 18:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-04 18:45 G. Sumner Hayes [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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-04  3:06     ` Andreas Jaeger
1997-12-03  5:14 ` Neal Becker

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=19971204214913.48297@collegium.adsl.net.cmu.edu \
    --to=sumner@collegium.adsl.net.cmu.edu \
    --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).