public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Rupert Wood" <me@rupey.net>
To: "'Elliott Potter'" <epotter@eep.burdell.org>
Cc: <gcc-help@gcc.gnu.org>
Subject: RE: 64-bit gcc3.1 on Solaris?
Date: Mon, 01 Jul 2002 11:23:00 -0000	[thread overview]
Message-ID: <616BE6A276E3714788D2AC35C40CD18D5EC4CD@whale.softwire.co.uk> (raw)
In-Reply-To: <616BE6A276E3714788D2AC35C40CD18D6BFBC9@whale.softwire.co.uk>

Elliott Potter wrote:

> Has anyone tried to compile gcc 3.1 as 64 bit on Solaris 2.8 or 2.9?
> I got it compiled as 32 bit no problem (twice actually) and it does
> appear to compile working 64 bit programs, but just for the heck of
> it I thought I'd try to compile the compiler with the -m64 option.

I don't have 2.9 to play with but the following works for me on 2.8:

    CC="gcc -m64" ~/cvs/gcc31/configure --enable-threads=posix \
        --disable-checking --disable-nls --with-cpu=ultrasparc \
        sparcv9-sun-solaris2.8 \
        && gmake -j4 bootstrap CC="gcc -m64"

using Sun's as and ld and CVS GCC3.1.1 sources from the middle of last
week (release 3.1 ought to work too). gmake is GNU make - haven't tried
Sun's make. This build didn't include Ada; I've got Sun ld vs Ada symbol
problems and GNU ld 64-bit vs patched libdl.so problems but I haven't
yet found time to work out what bugs I need to report to whom.

For day to day use, though, I'd stick to the default 32-bit version and
-m64.

Rup.

       reply	other threads:[~2002-07-01 18:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <616BE6A276E3714788D2AC35C40CD18D6BFBC9@whale.softwire.co.uk>
2002-07-01 11:23 ` Rupert Wood [this message]
2002-07-01 12:46   ` Elliott Potter
2002-07-19  9:43 Anil Shinde
  -- strict thread matches above, loose matches on Subject: below --
2002-06-29 22:52 Elliott Potter

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=616BE6A276E3714788D2AC35C40CD18D5EC4CD@whale.softwire.co.uk \
    --to=me@rupey.net \
    --cc=epotter@eep.burdell.org \
    --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).