From: Alexandre Oliva <aoliva@redhat.com>
To: "Sangwan, Vikas (CORP, GEITC)" <Vikas.Sangwan@geind.ge.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Clarification
Date: Wed, 14 Feb 2001 17:09:00 -0000 [thread overview]
Message-ID: <oritmc4urj.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: <4DE51758E7CDD411A78700508B6FEB1E0120A54B@ban03xbindge.geind.ge.com>
On Feb 13, 2001, "Sangwan, Vikas (CORP, GEITC)" <Vikas.Sangwan@geind.ge.com> wrote:
> I am trying to build a shared library from a set of '.o's.
Compile with -fPIC, otherwise Sun's linker will complain unless you
run gcc with -mimpure-text. The latter will result in dynamic
libraries, but not shared libraries (in the sense that their memory
pages won't be shareable across multiple processes, because they'd
need relocations).
--
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
next prev parent reply other threads:[~2001-02-14 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 13:43 Clarification Sangwan, Vikas (CORP, GEITC)
2001-02-14 17:09 ` Alexandre Oliva [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-06 3:58 Clarification Damian Minihan
2000-07-06 4:03 ` Clarification Alexandre Oliva
2000-07-06 4:32 ` Clarification Neelakanth
2000-07-06 12:31 ` Clarification Martin v. Loewis
2000-07-06 6:42 ` Clarification Philipp Thomas
1999-02-21 15:34 Clarification Jeffrey A Law
1999-02-28 22:53 ` Clarification Jeffrey A Law
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=oritmc4urj.fsf@guarana.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=Vikas.Sangwan@geind.ge.com \
--cc=gcc@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).