public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: "John P. Hartmann" <jphartmann@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: -m31 rejected when building libgcc for cross compiler for s390 (31 bit) gcc 4.6.0
Date: Sat, 21 May 2011 17:04:00 -0000	[thread overview]
Message-ID: <mcrtyco134h.fsf@coign.corp.google.com> (raw)
In-Reply-To: <BANLkTinApiihuy4su+jyWwSQD+k-9Zf0MA@mail.gmail.com> (John	P. Hartmann's message of "Sat, 21 May 2011 10:24:49 +0100")

"John P. Hartmann" <jphartmann@gmail.com> writes:

> Building a cross compiler from i686 (the platform of my linux) to s390
> I get the following when the bootstrap process is configuring in
> s390-ibm-linux/libgcc:
>
> configure:3268: /usr/ports/gcc390/build460/./gcc/xgcc
> -B/usr/ports/gcc390/build460/./gcc/
> -B/usr/ports/gcc390/inst/s390-ibm-linux/bin/
> -B/usr/ports/gcc390/inst/s390-ibm-linux/lib/ -isystem
> /usr/ports/gcc390/inst/s390-ibm-linux/include -isystem
> /usr/ports/gcc390/inst/s390-ibm-linux/sys-include    -c -g -O2
> conftest.c >&5
> exec: 89: -m31: not found

This looks like you don't have a cross-assembler.  You need to make and
install the GNU binutils first with the same --host, --target, and
--prefix options.  Then start again with gcc in a brand new empty build
directory.

Ian

  reply	other threads:[~2011-05-21 15:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-21 12:22 John P. Hartmann
2011-05-21 17:04 ` Ian Lance Taylor [this message]
2011-05-22  2:00   ` John P. Hartmann
2011-05-22  8:58     ` Ian Lance Taylor
2011-05-22  9:34       ` Ian Lance Taylor
2011-05-22  9:44       ` Ian Lance Taylor
2011-05-22 12:14       ` John P. Hartmann
2011-05-22 13:12         ` Jeffrey Walton

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=mcrtyco134h.fsf@coign.corp.google.com \
    --to=iant@google.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jphartmann@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).