From: butters <butters@station51.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: angstrom-gnome-image compilation error
Date: Sat, 29 May 2010 20:24:26 +0200 [thread overview]
Message-ID: <4C015BDA.2090506@station51.net> (raw)
In-Reply-To: <htr2a9$f76$1@dough.gmane.org>
Well I had wondered if it was something with Ubuntu screwing it up. I
had planned on trying Debian with it, but i haven't had the energy to do
it yet. I was hoping someone else had experienced the same problem. I
hope someone has a solution for it.
On 5/29/2010 2:46 PM, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 29-05-10 13:01, butters wrote:
>
>> Hello,
>>
>> I'm having trouble getting angstrom-gnome-image.bb to completely
>> compile. It stops at firefox_3.6.3.bb with this error..
>>
>> ./nanojit/NativeARM.cpp:949: warning unused variable 'was'
>> {standard input} Assembler messages:
>> {standard input}: 824: Error: selected processor does not support clz r1,r1
>> jsbuiltins.cpp
>>
>> I'm compiling for armv4t, for the mini2440 machine. Is this a known
>> issue? Because I've been able to compile this in the past.
>>
> Looks like nanojit is forcing armv5te instructions even for armv4t,
> which the compiler and binutils have every reason to complain about.
>
> Does anyone familiar with the mozilla buildsystem know if we can disable
> things like CLZ for armv4t and below?
>
> regards,
>
> Koen
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD8DBQFMAQyJMkyGM64RGpERAiM+AKCKUkS9EmkuzA8ow//U+tu5jfkcqACeK6n5
> ZlKdnPlkE8axIRTN8APRKq0=
> =xuT6
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
prev parent reply other threads:[~2010-05-29 18:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 11:01 angstrom-gnome-image compilation error butters
2010-05-29 12:46 ` Koen Kooi
2010-05-29 18:24 ` butters [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=4C015BDA.2090506@station51.net \
--to=butters@station51.net \
--cc=openembedded-devel@lists.openembedded.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.