public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "darren at mambo dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/25740] Bus Error compiling gcc/config/sparc/sol2-c1.asm
Date: Thu, 12 Jan 2006 15:30:00 -0000	[thread overview]
Message-ID: <20060112153012.13789.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25740-12001@http.gcc.gnu.org/bugzilla/>



------- Comment #10 from darren at mambo dot net  2006-01-12 15:30 -------
Well, after about ten tries, I got it to all compile.

The magic required was:

1. Ensure bintools was in path before /usr/ccs/bin
2. Remove gnu ld from system
3. CFLAGS='-m64' configure --disable-multilib --enable-languages=c,c++
sparcv9-sun-solaris2.10
4. gmake

I disabled multilib because otherwise it tried to compile sparcv7 with 'xgcc
... -m32 -m64', requiring too many manual changes of config.status and
resulting Makefile's

I guess my final point is that if configure sees that it's on Solaris 2.10 with
a v9 processor, shouldn't it at least guess 'sparcv9-sun-solaris2.10' as the
triplet instead of the generic 'sparc-sun-solaris', especially since I hadn't
specified --host, --target or --build?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25740


  parent reply	other threads:[~2006-01-12 15:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-10 15:37 [Bug bootstrap/25740] New: " darren at mambo dot net
2006-01-10 16:05 ` [Bug bootstrap/25740] " ebotcazou at gcc dot gnu dot org
2006-01-10 16:12 ` darren at mambo dot net
2006-01-10 16:58 ` ebotcazou at gcc dot gnu dot org
2006-01-10 17:52 ` darren at mambo dot net
2006-01-10 18:09 ` ebotcazou at gcc dot gnu dot org
2006-01-10 21:32 ` darren at mambo dot net
2006-01-10 21:38 ` ebotcazou at gcc dot gnu dot org
2006-01-10 22:13 ` ebotcazou at gcc dot gnu dot org
2006-01-10 22:50 ` ebotcazou at gcc dot gnu dot org
2006-01-12 15:30 ` darren at mambo dot net [this message]
2006-01-12 15:47 ` ebotcazou at gcc dot gnu dot org

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=20060112153012.13789.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).