public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: Manfred Hollstein <manfred@ks.sel.alcatel.de>
Cc: egcs@cygnus.com
Subject: Re: egcs-970929: SunOS and --enable-shared - HOW?
Date: Thu, 09 Oct 1997 02:08:00 -0000	[thread overview]
Message-ID: <or90w39won.fsf@sunsite.dcc.unicamp.br> (raw)
In-Reply-To: <9710080752.AA23586@lts.sel.alcatel.de>

Manfred Hollstein writes:

> Can anybody who believes  to  have built a  shared libstdc++  on SunOS
> successfully shed some light on this?

I build egcs with shared libraries regularly on SunOS 4.1.3

The only non-trivial trick I use is to create a soft-link
egcs-<date>/gcc/real-ld -> GNU ld.  I also create such links in the
several stage subdirectories.

-- 
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil

  reply	other threads:[~1997-10-09  2:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-08  1:51 Manfred Hollstein
1997-10-09  2:08 ` Alexandre Oliva [this message]
1997-10-10  8:51   ` Manfred Hollstein
1997-10-10  8:51   ` Manfred Hollstein

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=or90w39won.fsf@sunsite.dcc.unicamp.br \
    --to=oliva@dcc.unicamp.br \
    --cc=egcs@cygnus.com \
    --cc=manfred@ks.sel.alcatel.de \
    /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).