From: James E Wilson <wilson@specifixinc.com>
To: "Arora, Sudhanshu" <sarora@informatica.com>
Cc: "Rathi, Dinesh" <drathi@informatica.com>, gcc@gcc.gnu.org
Subject: RE: Can code compiled with g++ 3.3.1 run with earlier versions of compiler runtime environment?
Date: Fri, 10 Sep 2004 21:25:00 -0000 [thread overview]
Message-ID: <1094843495.10265.24.camel@aretha.corp.specifixinc.com> (raw)
In-Reply-To: <38CAB093AB9394468FC8A817A855610A1522A4@in2kex01.informatica.com>
On Thu, 2004-09-09 at 23:53, Arora, Sudhanshu wrote:
> Thanks a lot for your reply. But I don't understand what do you mean by 'configure gcc --disable-shared'.
--disable-shared is a configure option. Add it to the command line you
use to configure gcc.
> I tried this option in my env and it doesn't work.
You didn't give an actual bug report, so I am not able to help.
"doesn't work" isn't enough info to go on.
> Is it equivalent to static option in gcc. i.e will it create static libs for me instead of dynamic libs?
Yes, it will build only static libraries. This is different than using
-static, because -static will link in a static libstdc++, but it will
also link in static system libraries like /lib/libc.so. If you
configure gcc with the --disable-shared option, then when you link you
will get a static libstdc++ and a dynamic /lib/libc.so which is better.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
next prev parent reply other threads:[~2004-09-10 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 8:14 Arora, Sudhanshu
2004-09-10 21:25 ` James E Wilson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-10 6:43 Rathi, Dinesh
2004-09-10 20:43 ` James E Wilson
2004-09-08 8:50 Rathi, Dinesh
2004-09-08 14:11 ` Nathan Sidwell
2004-09-09 21:56 ` James E Wilson
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=1094843495.10265.24.camel@aretha.corp.specifixinc.com \
--to=wilson@specifixinc.com \
--cc=drathi@informatica.com \
--cc=gcc@gcc.gnu.org \
--cc=sarora@informatica.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).