From: David Kirkby <david.kirkby@onetel.net>
To: JonathonS <thejunkjon@gmail.com>, gcc-help@gcc.gnu.org
Subject: Re: GCC on Solaris -- assertion failure
Date: Wed, 29 Aug 2012 16:44:00 -0000 [thread overview]
Message-ID: <CANX10hAa2_jYuF3pSq50EsrAXFdJ6NhNO4qaPajZiCoGeTnQTg@mail.gmail.com> (raw)
In-Reply-To: <CABw5CXcx=dkjYdAd_g6yHaAvJ0YzR2c9B57oykTxRvx1XevvxQ@mail.gmail.com>
On 28 August 2012 18:15, JonathonS <thejunkjon@gmail.com> wrote:
> Hi Dave,
Hi,
> uname -a
> --------------
> SunOS lab8sun210-07 5.10 Generic_139555-08 sun4u sparc SUNW,Sun-Fire-V210
A sun 4u processor is 64-bit, not 32-bit. You can still build 32-bit
code on a 64-bit processor. gcc will do this unless you add the -m64
option on Solaris.
I can't reallly help you on your problem, but hopefully have clarified
that any "64" messages are not necessarily a problem.
Dave
prev parent reply other threads:[~2012-08-28 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-28 11:08 JonathonS
2012-08-28 13:09 ` David Kirkby
[not found] ` <CABw5CXcx=dkjYdAd_g6yHaAvJ0YzR2c9B57oykTxRvx1XevvxQ@mail.gmail.com>
2012-08-29 16:44 ` David Kirkby [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=CANX10hAa2_jYuF3pSq50EsrAXFdJ6NhNO4qaPajZiCoGeTnQTg@mail.gmail.com \
--to=david.kirkby@onetel.net \
--cc=gcc-help@gcc.gnu.org \
--cc=thejunkjon@gmail.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).