From: Adam Stein <adam@scan.mc.xerox.com>
To: gcc-help@gcc.gnu.org
Subject: Building gcc 3.1 with 64 bit support on Solaris 2.6?
Date: Tue, 18 Jun 2002 08:36:00 -0000 [thread overview]
Message-ID: <200206181535.g5IFZZT26002@chroma> (raw)
I can build a version of gcc 3.1 with 64 bit support if I'm compiling on Solaris
8 (and running a 64 bit kernel).
What I would like to do is compile gcc 3.1 on a Solaris 2.6 running a 32 bit
kernel (it is an ultrasparc machine if that matters). In this way, gcc would be
able to compile normally using 32 bit code which would run on Solaris 2.6 and
up, but have the "-m64" option work when compiling on Solaris 8 systems without
having two versions of gcc 3.1.
Is there any way to do this? I've tried various combinations of configurations
options, but it seems that gcc compiled on Solaris 2.6 won't have the "-m64"
support when being run on Solaris 8 systems.
Any help is appreciated, even if you can tell me that you definitely can NOT do
this.
Otherwise, I will have to have two versions of gcc, one for Solaris 2.6 and one
for Solaris 8.
Adam
--
Adam Stein @ Xerox Corporation Email: adam@scan.mc.xerox.com
Disclaimer: All views expressed
here have been proved to be my own. [http://www.csh.rit.edu/~adam/]
reply other threads:[~2002-06-18 15:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200206181535.g5IFZZT26002@chroma \
--to=adam@scan.mc.xerox.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).