From: Andrey Slepuhin <pooh@msu.ru>
To: law@cygnus.com
Cc: egcs@cygnus.com
Subject: egcs install docs: --enable-threads
Date: Tue, 02 Dec 1997 18:18:00 -0000 [thread overview]
Message-ID: <3484A610.53A37970@msu.ru> (raw)
Hi,
Looking at "Configuring egcs-1.00" I found an option
--enable-threads. Indeed, this option does nothing on
most platforms. For example, on my AIX box thread
support is always included and is enabled by -mthreads
compiler flag. But I must manually patch configuration
files to receive thread-safe versions of libgcc and
libstdc++ (and --enable-threads option doesn't help with
this). As I do this using multilib configuration, I also
must remove all cpu-specific targets (I don't need them,
and they make bootstrapping process too long). It would
be good if multilib configuration will be more flexible
or if --enable-threads option will enable creation of
thread-safe versions of libraries without multilib.
Any ideas?
Andrey.
next reply other threads:[~1997-12-02 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-02 18:18 Andrey Slepuhin [this message]
1997-12-02 16:29 ` Jeffrey A Law
1997-12-02 23:24 ` Oleg Krivosheev
1997-12-02 22:54 ` 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=3484A610.53A37970@msu.ru \
--to=pooh@msu.ru \
--cc=egcs@cygnus.com \
--cc=law@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).