From: Ruslan Shevchenko <Ruslan@Shevchenko.kiev.ua>
To: Andrey Slepuhin <pooh@msu.ru>
Cc: egcs@cygnus.com
Subject: Re: [Fwd: No C/C++ fundamental type 1 error.]
Date: Thu, 05 Feb 1998 13:49:00 -0000 [thread overview]
Message-ID: <34D8EF74.4237D896@Shevchenko.kiev.ua> (raw)
In-Reply-To: <XFMail.980205150931.pooh@msu.ru>
Andrey Slepuhin wrote:
> On 04-Feb-98 Ruslan Shevchenko wrote:
> > Anybody know, Teemu Torma's patch, for generating thread-safe
> > exception
> > handling code to egcs now intengrated in the main stream.
> >
> > (i.e. current egcs from CVS repositary have it ?)
>
> Yes, current development tree containes Teemu's patch, but you
> should carefully check if thread-safe versions of libstdc++
> and libgcc are generated for your target (otherwise, there is
> no much effort to do some tuning of configuration).
>
Sorry, but how to do this ? (I must looked at Makefile and shure, that
some variables are set ?
what ?)
I'm currently try to do it on two systems: SCO Open Server 5.04
and FreeBSD 2.2-stable.
> Andrey.
--
@=
//RSSH mailto://Ruslan@Shevchenko.Kiev.UA
next prev parent reply other threads:[~1998-02-05 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-05 2:28 Ruslan Shevchenko
1998-02-05 4:52 ` Andrey Slepuhin
1998-02-05 13:49 ` Ruslan Shevchenko [this message]
1998-02-05 12:42 Mike Stump
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=34D8EF74.4237D896@Shevchenko.kiev.ua \
--to=ruslan@shevchenko.kiev.ua \
--cc=egcs@cygnus.com \
--cc=pooh@msu.ru \
/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).