From: "Rakshit Karnavat , Gurgaon" <rakshit@ggn.hcltech.com>
To: gcc@gcc.gnu.org
Subject: GCC Build Status for SCO OS 5.0.5
Date: Tue, 20 Nov 2001 13:36:00 -0000 [thread overview]
Message-ID: <5F0021EEA434D511BE7300D0B7B6AB530187C66E@MAIL2> (raw)
I was unable to make gcc 3.0.1 using the --enable-shared option in
the i386 environment. Without that option, everything runs fine. But
then,
I am unable to make shared libraries using gcc. I make shared libraries
using the native cc.
But it is not serving the purpose. Any help on this front??
Is it possible to make shared libraries with gcc on SCO OS 5.*
Rakshit.
WARNING: multiple messages have this Message-ID
From: "Rakshit Karnavat, Gurgaon" <rakshit@ggn.hcltech.com>
To: gcc@gcc.gnu.org
Subject: GCC Build Status for SCO OS 5.0.5
Date: Tue, 27 Nov 2001 23:58:00 -0000 [thread overview]
Message-ID: <5F0021EEA434D511BE7300D0B7B6AB530187C66E@MAIL2> (raw)
Message-ID: <20011127235800.oACThKaTQXdnqD3OFtA2D7xtlafFvqSFR8GudGhEQlc@z> (raw)
I was unable to make gcc 3.0.1 using the --enable-shared option in
the i386 environment. Without that option, everything runs fine. But
then,
I am unable to make shared libraries using gcc. I make shared libraries
using the native cc.
But it is not serving the purpose. Any help on this front??
Is it possible to make shared libraries with gcc on SCO OS 5.*
Rakshit.
next reply other threads:[~2001-11-28 7:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 13:36 Rakshit Karnavat , Gurgaon [this message]
2001-11-20 16:46 ` Robert Lipe
2001-11-28 6:28 ` Robert Lipe
2001-11-27 23:58 ` Rakshit Karnavat, Gurgaon
2001-11-20 17:17 Rakshit Karnavat , Gurgaon
2001-11-20 19:38 ` Phil Edwards
2001-11-28 11:20 ` Phil Edwards
2001-11-28 7:39 ` Rakshit Karnavat, Gurgaon
2001-11-21 13:12 Rakshit Karnavat , Gurgaon
2001-11-21 15:33 ` Phil Edwards
2001-11-29 8:49 ` Phil Edwards
2001-11-28 22:07 ` Rakshit Karnavat, Gurgaon
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=5F0021EEA434D511BE7300D0B7B6AB530187C66E@MAIL2 \
--to=rakshit@ggn.hcltech.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).