From: Oleg <oleg_inconnu@myrealbox.com>
To: gcc-help@gcc.gnu.org
Subject: g++-3.2 with STLport
Date: Mon, 16 Sep 2002 10:45:00 -0000 [thread overview]
Message-ID: <200209161745.NAA04193@dewberry.cc.columbia.edu> (raw)
Help!
I'm using g++-3.2 that I compiled from source with all default options, and
I'm trying to get it to work with STLport. I tried different configurations,
and while I can compile STLport, I can not use it: either static linking
fails, or programs don't run.
I understand that there are different views on how threads should be
implemented, and the issue of changed ABI. This adds to the different
configurations for compiling g++, multiplied by the different ways to compile
STLport, multiplied by the different ways in which STLport can be configured
after and before compilation, multiplied by the different ways to use it,
resulting in the complexity that I couldn't handle so far.
AFAIK many g++ users and developers use i*86 Debian, like myself. I suspect
that some people also use STLport. If you managed to use g++-3.2 and STLport
on this or similar system and can give me a hint as to how you've done that,
I'll be very grateful.
Thanks in advance for your time.
Oleg
reply other threads:[~2002-09-16 17:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200209161745.NAA04193@dewberry.cc.columbia.edu \
--to=oleg_inconnu@myrealbox.com \
--cc=gcc-help@gcc.gnu.org \
/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).