public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Benjamin Krueger <benjamin@seattleFenix.net>
To: gcc-help@gcc.gnu.org
Subject: 64bit Executable Support on Solaris 9
Date: Sat, 07 Sep 2002 01:31:00 -0000	[thread overview]
Message-ID: <20020907012927.A88923@mail.seattleFenix.net> (raw)


I've recently installed the Sunfreeware gcc 3.2 package on a
SPARCengine AXi (UltraSPARC-IIi 270MHz) running Solaris 9 Generic 64-bit. I'd
like to be able to compile 64-bit executables, however compiling even the
following simple code fails to work. Google references to this error and
similar errors vary wildly and as far as I can tell from my limited
programming knowledge, aren't applicable to this problem.

#include <stdio.h>
int main()
{
	printf("Hello, World.\n");
	return -1;
}

# gcc -m32 -o test32 test.c
# ./test32
Hello, World.
# gcc -m64 -o test64 test.c
ld: fatal: file /usr/lib/sparcv9/values-Xa.o: wrong ELF class: ELFCLASS32
ld: fatal: File processing errors. No output written to test64
collect2: ld returned 1 exit status
# locate values-Xa.o
/usr/ccs/lib/sparcv9/values-Xa.o
/usr/ccs/lib/values-Xa.o
/usr/lib/sparcv9/values-Xa.o
/usr/lib/values-Xa.o

All of the above files are ELF 32-bit MSB relocatable SPARC Version 1

Is there anything special I should be doing here to create a 64bit executable?
Am I missing something?

Please CC me in replies as I am not subscribed to this list.

Regards,

-- 
Benjamin Krueger

"Everyone has wings, some folks just don't know what they're for"
- B. Banzai
----------------------------------------------------------------
Send mail w/ subject 'send public key' or query for (0x251A4B18)
Fingerprint = A642 F299 C1C1 C828 F186  A851 CFF0 7711 251A 4B18

             reply	other threads:[~2002-09-07  8:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-07  1:31 Benjamin Krueger [this message]
     [not found] <616BE6A276E3714788D2AC35C40CD18D7D2E0A@whale.softwire.co.uk>
2002-09-09  1:00 ` Rupert Wood

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=20020907012927.A88923@mail.seattleFenix.net \
    --to=benjamin@seattlefenix.net \
    --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).