From: aoliva@redhat.com
To: ravi kol <kolli27@yahoo.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: linking problems with gcc3.0 on solaris8
Date: Wed, 01 Aug 2001 19:23:00 -0000 [thread overview]
Message-ID: <orlml3nqt7.fsf@feijoada.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20010801220402.20541.qmail@web4605.mail.yahoo.com>
On Aug 1, 2001, ravi kol <kolli27@yahoo.com> wrote:
> ld: fatal: relocations remain against allocatable but
> non-writable sections collect2: ld returned 1 exit
> status
> I have recently shifted from gcc-2.95.2 .when i tried
> using the -fPIC option ,it compiles ...ok...but the
> resultant shared object is a wrong one.
It must be a different problem. -fPIC is the correct solution for the
problem you're running into. A work-around (that would cause the
generation of a less efficient shared library) is to link using
-mimpure-text.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
prev parent reply other threads:[~2001-08-01 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 15:04 ravi kol
2001-08-01 19:23 ` aoliva [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=orlml3nqt7.fsf@feijoada.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=kolli27@yahoo.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).