public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Gard, Torbjörn" <torbjorn.gard@streamserve.com> To: dje@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: c++/4235 Date: Mon, 10 Sep 2001 01:16:00 -0000 [thread overview] Message-ID: <20010910081601.12504.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR c++/4235; it has been noted by GNATS. From: =?iso-8859-1?Q?=22Gard=2C_Torbj=F6rn=22?= <torbjorn.gard@streamserve.com> To: "'gcc-gnats@gcc.gnu.org'" <gcc-gnats@gcc.gnu.org>, "'gcc-prs@gcc.gnu.org'" <gcc-prs@gcc.gnu.org>, =?iso-8859-1?Q?=22Gard=2C?= =?iso-8859-1?Q?_Torbj=F6rn=22?= <torbjorn.gard@streamserve.com>, "'gcc-bugs@gcc.gnu.org'" <gcc-bugs@gcc.gnu.org>, "'dje@gcc.gnu.org'" <dje@gcc.gnu.org>, "Nilsson, Thomas" <thomas.nilsson@streamserve.com> Cc: Subject: Re: c++/4235 Date: Mon, 10 Sep 2001 10:06:03 +0200 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview&pr=3D4235&database=3Dg= cc Hello > Fix: Install shared libraries (both libgcc_s_*.a and libstdc++.a > with chmod a+x,o-r mode so that the shared objects are loaded > into the process private segment. GCC exception handling > places private data in the library preventing it from being > shared. I have tried this fix without success. Either the linker or the loader = fails to read the libraries. A possible solution using this method would at best be called a work = around and not a fix. And certainly the PR should not be closed until a real = solution exists. It should be noted also that the problem exists in AIX 4.3.3 as well as = AIX 4.2.0. Please reopen this problem report! regards Torbj=F6rn Gard StreamServe
next reply other threads:[~2001-09-10 1:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-09-10 1:16 Gard, Torbjörn [this message] 2001-09-11 1:26 c++/4235 Nilsson, Thomas
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=20010910081601.12504.qmail@sourceware.cygnus.com \ --to=torbjorn.gard@streamserve.com \ --cc=dje@gcc.gnu.org \ --cc=gcc-prs@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: linkBe 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).