From: Dimitry Andric <dimitry@andric.com>
To: Guylhem Aznar <bluez-devel@externe.net>
Cc: bluez-devel@lists.sourceforge.net, steve.crane@rococosoft.com
Subject: Re: [Bluez-devel] cross compiling bluez 2.16 for arm (Zaurus)
Date: Fri, 6 May 2005 10:30:36 +0200 [thread overview]
Message-ID: <35666156.20050506103036@andric.com> (raw)
In-Reply-To: <20050505182213.GA22967@externe.net>
[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]
On 2005-05-05 at 20:22:13 Guylhem Aznar wrote:
> arm-linux-gcc -DHAVE_CONFIG_H -I. -I. -I..
> -I/home/guylhem/bluez-libs-2.16//include -I/usr/include -Wall -O2
> -c `test -f 'sdptool.c' || echo './'`sdptool.c
> /tmp/ccsosFZV.s: Assembler messages:
> /tmp/ccsosFZV.s:1094: Error: bad instruction `rorw $8,r4'
> /tmp/ccsosFZV.s:1094: Error: bad instruction `rorl $16,r4'
> /tmp/ccsosFZV.s:1094: Error: bad instruction `rorw $8,r4'
> /tmp/ccsosFZV.s:1096: Error: bad instruction `rorw $8,r3'
> /tmp/ccsosFZV.s:1099: Error: bad instruction `rorw $8,r2'
> /tmp/ccsosFZV.s:1102: Error: bad instruction `rorw $8,r3'
> /tmp/ccsosFZV.s:1105: Error: bad instruction `rorw $8,r2'
> /tmp/ccsosFZV.s:1105: Error: bad instruction `rorl $16,r2'
> /tmp/ccsosFZV.s:1105: Error: bad instruction `rorw $8,r2'
> /tmp/ccsosFZV.s:1108: Error: bad instruction `rorw $8,r3'
This usually means there's something wrong with your toolchain.
Please run exactly the same command line, but then with the "-v"
option to arm-linux-gcc, and mail us the output.
[-- Attachment #2: Type: application/pgp-signature, Size: 183 bytes --]
next prev parent reply other threads:[~2005-05-06 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 18:22 [Bluez-devel] cross compiling bluez 2.16 for arm (Zaurus) Guylhem Aznar
2005-05-06 8:30 ` Dimitry Andric [this message]
2005-05-06 22:06 ` Guylhem Aznar
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=35666156.20050506103036@andric.com \
--to=dimitry@andric.com \
--cc=bluez-devel@externe.net \
--cc=bluez-devel@lists.sourceforge.net \
--cc=steve.crane@rococosoft.com \
/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