From: Kai Ruottu <kai.ruottu@wippies.com>
To: Poor Yorick <org.gnu.gcc.help@pooryorick.com>
Cc: gcc-help@gnu.org
Subject: Re: build 64-bit gcc-4.2.2 on Solaris 9
Date: Mon, 14 Apr 2008 22:25:00 -0000 [thread overview]
Message-ID: <4803B659.7030404@wippies.com> (raw)
In-Reply-To: <48039C44.60002@tuliptree.org>
Jim Wilson wrote:
> Poor Yorick wrote:
>> I'm trying to build 64-bit gcc-4.2.2 on Solaris 9, but I keep getting
>> 32-bit files in the build. I've tried various values for --host,
>> --target, CFLAGS, and LDFLAGS, but no joy.
Telling what target names you have already tried would be quite
obligatory...
>> I've looked around the documentation, and back through a couple of years of the
>> mailing list without luck. Could someone please clue me in on how to
>> tell gcc to be 64-bit?
Looking around the obvious 'gcc/config.gcc' for the available target
names would be wise... If one cannot guess what the right target name
could be, here one sees what target name templates one could try...
> I don't have a sparc machine here, but I believe most sparc-solaris
> builds support both 32-bit and 64-bit code. You get 64-bit code with
> -m64 and 32-bit code with -m32. So yes, you will have 32-bit files in
> the build even when building a gcc that emits 64-bit code. This isn't a
> problem.
Traditionally using a 'sparc-solaris2.x' target name has resulted to
a 32-bit default, 64-bit optional (with '-m64') compiler.
> If you want 64-bit code only, you can configure for
> sparc64-sun-solaris2.10 (or whatever Solaris version you have) and also
> specify --disable-multilibs to turn off support for the 32-bit libraries.
Furhermore using a 'sparcv9-solaris2.x' target name has resulted to
a 64-bit default, 32-bit optional (with '-m32') compiler.
> You might need to be more specific about what you want here. You want a
> gcc compiled as 64-bit code or a gcc that emits 64-bit code or both?
And checking the 'gcc/config.gcc' before configuring would be highly
recommended! The 'sparc64-<something>' has been the '<cpu>-<something>'
template for Linux, *BSD etc. other opsyses when requiring a 64-bit
default toolchain... Maybe the earlier 'sparcv9' has now been changed
to 'sparc64' with '-solaris2.x' too...
prev parent reply other threads:[~2008-04-14 19:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 20:33 Poor Yorick
2008-04-14 19:49 ` Jim Wilson
2008-04-14 22:25 ` Kai Ruottu [this message]
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=4803B659.7030404@wippies.com \
--to=kai.ruottu@wippies.com \
--cc=gcc-help@gnu.org \
--cc=org.gnu.gcc.help@pooryorick.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).