public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@iki.fi>
To: linux-omap@vger.kernel.org
Subject: Re: mainline: misc.o uses VFP instructions error
Date: Sat, 4 Jul 2009 19:19:27 +0300	[thread overview]
Message-ID: <da94abde0907040919o7ebc00a5v5a4f935b4f01c682@mail.gmail.com> (raw)
In-Reply-To: <87zlbkqy7s.fsf@litku.valot.fi>

On Sat, Jul 4, 2009 at 6:12 PM, Kalle Valo<kalle.valo@iki.fi> wrote:
> I'm trying to compile omap_generic_2420_defconfig in mainline and I get
> this error:
>
>  Kernel: arch/arm/boot/Image is ready
>  LD      arch/arm/boot/compressed/vmlinux
> arm-linux-ld: ERROR: arch/arm/boot/compressed/misc.o uses VFP
>  instructions, whereas arch/arm/boot/compressed/vmlinux does not
> arm-linux-ld: failed to merge target specific data of file
>  arch/arm/boot/compressed/misc.o

I tried omap3_beagle_defconfig and it compiled without errors. I found
discussion about the error here:

http://www.spinics.net/lists/arm-kernel/msg59073.html

And reverting this commit fixed the issue with omap_generic_2420_defconfig:

commit 80cec14a83ad0ad109d822b3f3482a379bc481ba
Author: Russell King <rmk@dyn-67.arm.linux.org.uk>
Date:   Tue Sep 9 13:56:45 2008 +0100

    [ARM] Add -march=all to assembly file build in arch/arm/boot/compressed

    This allows assembly files to be crafted to cover all ARM CPU types
    rather than erroring out on instructions only in later CPUs.  We
    are careful in these files to only execute CPU specific code when
    the CPU ID says we can.

    Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-07-04 16:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-04 15:12 mainline: misc.o uses VFP instructions error Kalle Valo
2009-07-04 16:19 ` Kalle Valo [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=da94abde0907040919o7ebc00a5v5a4f935b4f01c682@mail.gmail.com \
    --to=kalle.valo@iki.fi \
    --cc=linux-omap@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox