public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "David Eisner" <deisner@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Building gcc-4.2.4 on Solaris 9
Date: Tue, 29 Jul 2008 15:04:00 -0000	[thread overview]
Message-ID: <5ef8ba410807290643s6358c576tf28e80a4b1a985fa@mail.gmail.com> (raw)

I'm trying to build gcc-4.2.4 on a 64-bit Solaris 9 SPARC system,
using the Sun Studio compiler (Sun C 5.8).

I'm attempting to build 64-bit binaries (bad idea?).  I've built
64-bit versions of libmpfr and libgmp, and I have CC="cc
-xarch=generic64".  I'm running into a problem when building the stage
2 or stage 3 compiler:

/export/data/software/cradle/build/gcc/objdir/./prev-gcc/xgcc
-B/export/data/software/cradle/build/gcc/objdir/./prev-gcc/
-B/data/software/devtools/gcc-4.2.4-sparc-sun-solaris2.9/sparc-sun-solaris2.9/bin/
  -g -O2 -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros
-Wno-overlength-strings -Wold-style-definition
-Wmissing-format-attribute    -DHAVE_CONFIG_H  -o f951 \
        fortran/arith.o fortran/array.o fortran/bbt.o fortran/check.o
fortran/data.o fortran/decl.o fortran/dump-parse-tree.o
fortran/error.o fortran/expr.o fortran/interface.o fortran/intrinsic.o
fortran/io.o fortran/iresolve.o fortran/match.o fortran/matchexp.o
fortran/misc.o fortran/module.o fortran/openmp.o fortran/options.o
fortran/parse.o fortran/primary.o fortran/resolve.o fortran/scanner.o
fortran/simplify.o fortran/st.o fortran/symbol.o fortran/convert.o
fortran/dependency.o fortran/f95-lang.o fortran/trans.o
fortran/trans-array.o fortran/trans-common.o fortran/trans-const.o
fortran/trans-decl.o fortran/trans-expr.o fortran/trans-intrinsic.o
fortran/trans-io.o fortran/trans-openmp.o fortran/trans-stmt.o
fortran/trans-types.o main.o  libbackend.a ../libcpp/libcpp.a
../libdecnumber/libdecnumber.a
-L/data/software/devtools/gmp-4.2.1-sparc-sun-solaris2.9/lib
-L/data/software/devtools/mpfr-2.3.0-sparc-sun-solaris2.9/lib -lmpfr
-lgmp ../libcpp/libcpp.a ./../intl/libintl.a  ../libiberty/libiberty.a
../libdecnumber/libdecnumber.a
ld: fatal: file
/data/software/devtools/mpfr-2.3.0-sparc-sun-solaris2.9/lib/libmpfr.so:
wrong ELF class: ELFCLASS64
ld: fatal: file
/data/software/devtools/gmp-4.2.1-sparc-sun-solaris2.9/lib/libgmp.so:
wrong ELF class: ELFCLASS64
ld: fatal: File processing errors. No output written to f951
collect2: ld returned 1 exit status
make[3]: *** [f951] Error 1


The problem is that fortran .o files are 32-bit, not 64-bit:

cannes [objdir]$ file gcc/fortran/arith.o
gcc/fortran/arith.o:    ELF 32-bit MSB relocatable SPARC32PLUS Version
1, V8+ Required

What's the proper way to tell the later stage compilers to produce
64-bit binaries?

Thanks.

-David

-- 
David Eisner http://cradle.brokenglass.com

             reply	other threads:[~2008-07-29 13:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29 15:04 David Eisner [this message]
     [not found] <1217413077.17216.ezmlm@gcc.gnu.org>
2008-07-30 14:15 ` Jay
2008-07-30 16:45   ` David Eisner
     [not found] <1217501358.30475.ezmlm@gcc.gnu.org>
2008-07-31 17:03 ` Jay

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=5ef8ba410807290643s6358c576tf28e80a4b1a985fa@mail.gmail.com \
    --to=deisner@gmail.com \
    --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).