From: Robert A Nesius <rnesius@ichips.intel.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: libstdc++ requiring '.' on aix?
Date: Sun, 29 Apr 2001 19:01:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.30.0104291900400.13885-100000@plxw0032.pdx.intel.com> (raw)
In-Reply-To: <oritmbmzld.fsf@guarana.lsd.ic.unicamp.br>
I've confirmed the problem below to be fixed in gcc 2.95.3 on AIX 4.1.4!
-Rob
On 15 Feb 2001, Alexandre Oliva wrote:
> On Feb 15, 2001, Robert A Nesius <rnesius@ichips.intel.com> wrote:
>
> > [pdx206]-> src 47> ./aspell
> > Could not load program ./aspell
> > Could not load library .
> > Error was: Permission denied
>
> <aol>me too</aol>
>
> > 1 libc.a shr.o
> > 2 .
>
> > That's odd. libstdc++ includes '.'?
>
> > Has anyone seen this problem before on AIX?
>
> Yep. Every time I used gcc -shared to create a shared library that
> depended on another shared library.
>
> GCC would generate an import file starting with `#! .'. This would
> cause the generated library to depend on `.'. Ugh!
>
> This is fixed in the development sources. GCC 3.0 will be the first
> release of GCC to properly support the construction of shared
> libraries on AIX 4.1.
>
>
--
#include <sig.h>
------------------------------------------------------------------
Robert Nesius rnesius@ichips.intel.com 503.712.2181
DPG Engineering Computing SW Applications Team
prev parent reply other threads:[~2001-04-29 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 10:28 Robert A Nesius
2001-02-15 12:59 ` Alexandre Oliva
2001-02-15 14:47 ` Robert A Nesius
2001-02-16 10:02 ` Alexandre Oliva
2001-04-29 19:01 ` Robert A Nesius [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=Pine.LNX.4.30.0104291900400.13885-100000@plxw0032.pdx.intel.com \
--to=rnesius@ichips.intel.com \
--cc=aoliva@redhat.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).