From: David Edelsohn <dje@watson.ibm.com>
To: "Shlom Marom" <devshlom@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Exception handling on AIX5.3 with gcc 3.4.6
Date: Thu, 20 Mar 2008 17:23:00 -0000 [thread overview]
Message-ID: <200803201723.m2KHNOTa037394@makai.watson.ibm.com> (raw)
In-Reply-To: <c8cc0fd10803200828h393a87ecl5c69f4d5c80375c5@mail.gmail.com>
>>>>> Shlom Marom writes:
> I need to find a way to fully support exception handling and
> statically link libgcc, since I don't want to distribute it with my
> libs and executables, as part of my products
One cannot build a static C++ application that uses exceptions and
is built with G++ on AIX.
David
prev parent reply other threads:[~2008-03-20 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 15:28 Shlom Marom
2008-03-20 16:36 ` Brian Dessent
2008-03-21 23:36 ` Shlom Marom
2008-03-22 3:26 ` Brian Dessent
2008-03-23 9:22 ` Shlom Marom
2008-03-26 1:26 ` Ian Lance Taylor
2008-03-20 17:23 ` David Edelsohn [this message]
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=200803201723.m2KHNOTa037394@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=devshlom@gmail.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).