From: Robert Woodworth <rwoodworth@securics.com>
To: Josh Boyer <jwboyer@jdub.homelinux.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Xilinx Virtex4 FX PPC
Date: Mon, 20 Aug 2007 11:26:57 -0600 [thread overview]
Message-ID: <1187630817.6336.34.camel@PisteOff> (raw)
In-Reply-To: <20070820113549.7cc3ac45@weaponx.rchland.ibm.com>
On Mon, 2007-08-20 at 11:35 -0500, Josh Boyer wrote:
> On Mon, 20 Aug 2007 10:00:54 -0600
> Robert Woodworth <rwoodworth@securics.com> wrote:
>
> > Problem 2: Build my own rootfs.
> > If I try to build my own programs (busybox and bash at this point) with
> > shared libc using the same glibc from my toolchain, I get an "Illegal
> > instruction" error. Is my glibc not compatible with my Xilinx PPC 405??
> >
> >
> > If I try to build a rootfs with debian ppc packages I have the same
> > "Illegal instruction" error.
> >
> >
> >
> > Question 1:
> > Do I need a special glibc for the Xilinx PPC 405????
> > Does a normal PPC glibc have more "advanced" instructions compiled in
> > that will not work on a Xilinx PPC 405??
>
> Make sure you're building glibc with soft-fp, or make sure you have
> CONFIG_MATH_EMULATION enabled in your kernel. The PPC 405 doesn't have
> an FPU.
>
> josh
CONFIG_MATH_EMULATION fixed it!!
What are the opinions out there?
Kernel fp or glibc soft-fp??
I don't have a need for floating point in my final application anyway.
next prev parent reply other threads:[~2007-08-20 17:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 16:00 Xilinx Virtex4 FX PPC Robert Woodworth
2007-08-20 16:35 ` Josh Boyer
2007-08-20 17:26 ` Robert Woodworth [this message]
2007-08-20 17:42 ` Grant Likely
2007-08-20 17:50 ` Stephen Neuendorffer
2007-08-21 22:14 ` Clemens Koller
2007-08-20 17:50 ` Grant Likely
2007-08-21 8:52 ` Stelios Koroneos
2007-08-21 12:57 ` Josh Boyer
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=1187630817.6336.34.camel@PisteOff \
--to=rwoodworth@securics.com \
--cc=jwboyer@jdub.homelinux.org \
--cc=linuxppc-embedded@ozlabs.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.