From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: Guenter Feldmann <fld@informatik.uni-bremen.de>
Cc: gcc@gcc.gnu.org, fld@tzi.de
Subject: Re: gcc -m64 for Solaris10 x86
Date: Mon, 13 Dec 2004 17:16:00 -0000 [thread overview]
Message-ID: <ydd3byauniw.fsf@xayide.TechFak.Uni-Bielefeld.DE> (raw)
In-Reply-To: Guenter Feldmann's message of "Mon, 13 Dec 2004 13:55:20 +0100"
Guenter Feldmann <fld@informatik.uni-bremen.de> writes:
> could any one explain what is needed to enable the 64-bit mode in
> gcc for Solaris10 x86?
>
> I tried
> configure ... amd64-pc-solaris2.10
> and
> configure ... x86_64-pc-solaris2.10
>
> in both cases
> make bootstrap
> ended up in:
>
> > [ ... ]
> > checking for .preinit_array/.init_array/.fini_array support... no
> > checking if mkdir takes one argument... no
> > *** Configuration x86_64-pc-solaris2.10 not supported
Nothing: just bootstrap on Solaris 10/x86 without specifying a specific
configuration triplet. The resulting compiler will automatically support
amd64 code generation when specifying the -m64 option. Note however that
you need to use a recent version of GNU as (from CVS binutils) for the
bootstrap to succeed. You'll probably have to restrict yourself to C at
the moment: the 64-bit libstdc++ didn't build (at least as of a week ago).
Besides, there may be code generation bugs on mainline: building a 64-bit
lsof some time ago seems to have produced wrong code (though I haven't
investigate this in detail yet).
You may be better off with a modified version of GCC 3.4.3 from the
csl-sol210-3_4-branch branch documented in
http://gcc.gnu.org/cvs.html
at the moment. This compiler will be included in Solaris 10 build 73
(probably the next release of Solaris Express), btw.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University
next prev parent reply other threads:[~2004-12-13 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 12:55 Guenter Feldmann
2004-12-13 16:11 ` Daniel Jacobowitz
2004-12-13 17:16 ` Rainer Orth [this message]
2004-12-13 22:08 ` Albert Chin
2004-12-14 12:34 ` Rainer Orth
2004-12-14 18:26 ` Mark Mitchell
2004-12-15 18:44 ` Rainer Orth
2004-12-15 19:00 ` Mark Mitchell
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=ydd3byauniw.fsf@xayide.TechFak.Uni-Bielefeld.DE \
--to=ro@techfak.uni-bielefeld.de \
--cc=fld@informatik.uni-bremen.de \
--cc=fld@tzi.de \
--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).