All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: sparclinux@vger.kernel.org
Subject: cross-toolchain build script; problem with gas for sparc64
Date: Mon, 26 Apr 2004 03:49:07 +0000	[thread overview]
Message-ID: <408C86B3.8080800@kegel.com> (raw)
In-Reply-To: <20040426032713.GI3647@phunnypharm.org>

Hey folks,
I spent some time trying to get crosstool (my gcc/glibc cross toolchain
build script) to support the sparc64-linux target.  It might be of
interest for anyone who needs to build gcc and glibc but doesn't
have the target handy (or who wants to do a clean build from fully
pristine sources).  Its home page is http://kegel.com/crosstool

To build a gcc-3.4.0/glibc-2.3.2 toolchain targeting sparc64-linux
with the current version of my script, you'd do
   wget http://kegel.com/crosstool/crosstool-0.28-rc7.tar.gz
   tar -xzvf crosstool-0.28-rc7.tar.gz
   cd crosstool-0.28-rc7
   sh demo-sparc64.sh

Sadly, this fails at the moment with
   qp_qtoi.s:261: Error: Illegal operands: There are only 32 single precision f registers; [0-31]
while building glibc.
(See also http://sources.redhat.com/ml/binutils/2004-04/msg00686.html)
Anyone seen that kind of error before?  It's odd, since the assembler is
being passed the -Av9a -64 options, which really ought to tell it
there are 64 fp registers, I thought.

Thanks,
Dan


-- 
My technical stuff: http://kegel.com
My politics: see http://www.misleader.org for examples of why I'm for regime change

  reply	other threads:[~2004-04-26  3:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-26  3:27 cross-toolchain build script; problem with gas for sparc64 Ben Collins
2004-04-26  3:49 ` Dan Kegel [this message]
2004-04-26  5:12 ` Dan Kegel

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=408C86B3.8080800@kegel.com \
    --to=dank@kegel.com \
    --cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.