From: Vinu V Nair <vinu@sasi.com>
To: "Penias, Nissim" <Nissim.Penias@ca.com>
Cc: "'gcc-help@gcc.gnu.org'" <gcc-help@gcc.gnu.org>
Subject: Re: Getting an error message from gcc libstdc++.a on Solaris 2.5.1.
Date: Mon, 29 May 2000 01:35:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.10.10005291358310.25884-100000@sassun5.sasi.com> (raw)
In-Reply-To: <770292EEED98D311A2D7009027DE04A201CDBF29@ukslms01.cai.com>
For building shared libs, u have to give --enable-shared to the configure
program.
vinu
Vinu V. Nair
Software Engineer
Silicon Automation Systems Limited
5281461/5281229-2213
"The reasonable man adapts himself to the world; the unreasonable
man persists to adapt the world to himself. Therefore all progress
depends on the unreasonable." -- G. Bernard. Shaw.
next prev parent reply other threads:[~2000-05-29 1:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-28 23:57 Penias, Nissim
2000-05-29 1:35 ` Vinu V Nair [this message]
2000-05-29 1:43 ` Martin v. Loewis
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.GSO.4.10.10005291358310.25884-100000@sassun5.sasi.com \
--to=vinu@sasi.com \
--cc=Nissim.Penias@ca.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).