From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] new problem with new crossdev
Date: Fri, 1 Sep 2006 01:07:14 -0400 [thread overview]
Message-ID: <200609010107.14364.vapier@gentoo.org> (raw)
In-Reply-To: <200609010008.36687.ladmanj@volny.cz>
[-- Attachment #1: Type: text/plain, Size: 319 bytes --]
On Thursday 31 August 2006 18:08, Jakub Ladman wrote:
> cc1: error: command line option ‘-m4-nofpu’ is not supported by this
> configuratn
guess you're targetting sh4 with gcc-4.1.1 huh
there's a bug open atm about enabling multilib support in such a
configuration, but gcc-3.4.6 should work fine
-mike
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2006-09-01 5:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 22:08 [gentoo-embedded] new problem with new crossdev Jakub Ladman
2006-09-01 4:10 ` KIMURA Masaru / hiyuh
2006-09-01 7:23 ` Jakub Ladman
2006-09-01 18:58 ` KIMURA Masaru / hiyuh
2006-09-01 5:07 ` Mike Frysinger [this message]
2006-09-01 7:32 ` Jakub Ladman
2006-09-01 7:45 ` Mike Frysinger
2006-09-01 7:52 ` Jakub Ladman
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=200609010107.14364.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-embedded@lists.gentoo.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