From: hjl@lucon.org (H.J. Lu)
To: egcs@cygnus.com
Subject: A new libstdc++ patch for linux/glibc 2
Date: Wed, 14 Jan 1998 23:17:00 -0000 [thread overview]
Message-ID: <m0xsfPR-0004ecC@ocean.lucon.org> (raw)
Hi,
Please ignore my last patch and use this one instead. My
STL patch is still needed.
--
H.J. Lu (hjl@gnu.org)
---
Wed Jan 14 15:25:05 1998 H.J. Lu (hjl@gnu.org)
* config/linux.mt: Don't define _PTHREADS, but define
_IO_MTSAFE_IO.
Index: config/linux.mt
===================================================================
RCS file: /home/work/cvs/gnu/egcs/libstdc++/config/linux.mt,v
retrieving revision 1.1.1.1
diff -u -r1.1.1.1 linux.mt
--- linux.mt 1997/09/17 20:12:42 1.1.1.1
+++ linux.mt 1998/01/15 02:47:10
@@ -1 +1,2 @@
-MT_CFLAGS = -D_PTHREADS
+# tell we want the mt-safe version
+MT_CFLAGS = -D_IO_MTSAFE_IO
next reply other threads:[~1998-01-14 23:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-14 23:17 H.J. Lu [this message]
1998-01-16 1:51 ` Byeong-ryeol Kim
1998-01-16 19:49 ` H.J. Lu
1998-02-01 12:40 Jeffrey A Law
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=m0xsfPR-0004ecC@ocean.lucon.org \
--to=hjl@lucon.org \
--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).