Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: James E Wilson <wilson@specifix.com>
To: kernel coder <lhrkernelcoder@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: gcc-4.1.0 cross-compile for MIPS
Date: Fri, 23 Jun 2006 12:01:21 -0700	[thread overview]
Message-ID: <1151089281.25695.11.camel@aretha.corp.specifix.com> (raw)
In-Reply-To: <f69849430606182340t72ed5a68l95a724ea933faf12@mail.gmail.com>

On Sun, 2006-06-18 at 23:40, kernel coder wrote:
> ../glibc-2.3.6/configure --host=mipsel-linux --prefix="/usr"
> --enable-add-ons --with-headers=/home/shahzad/install/mipsel/include
> "misc/sys/uio.h"'; } |                 \ gcc -mabi=32 -E -dM -MD -MP
> cc1: error: unrecognized command line option "-mabi=32"

It failed, because it tries to give mips compiler options to the native
(x86?) compiler, which obviously won't work.  And you got this failure
because you configured glibc wrong.

As always, the answer to this problem can be found in Dan Kegel's
crosstools package, which knows how to correctly configure glibc.  Since
you apparently haven't taken my previous hints, instead of giving you
the answer, I'm just going to point you at the crosstools package, and
ask you to look it up yourself.
-- 
Jim Wilson, GNU Tools Support, http://www.specifix.com

      parent reply	other threads:[~2006-06-23 19:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-16 12:22 gcc-4.1.0 cross-compile for MIPS kernel coder
2006-06-16 12:38 ` Ralf Roesch
2006-06-16 14:22   ` kernel coder
2006-06-16 15:41 ` Jonathan Day
2006-06-16 22:33 ` James E Wilson
2006-06-19  6:40   ` kernel coder
2006-06-19  7:19     ` Matej Kupljen
2006-06-23 19:01     ` James E Wilson [this message]

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=1151089281.25695.11.camel@aretha.corp.specifix.com \
    --to=wilson@specifix.com \
    --cc=lhrkernelcoder@gmail.com \
    --cc=linux-mips@linux-mips.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