From: hong zhang <henryzhang62@yahoo.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] cross compile problem on bluez
Date: Mon, 6 Aug 2007 13:33:51 -0700 (PDT) [thread overview]
Message-ID: <547249.8186.qm@web58008.mail.re3.yahoo.com> (raw)
In-Reply-To: <mailman.151917.1186390010.21973.bluez-devel@lists.sourceforge.net>
List,
I apply bluez to embedded linux system. ARM processor
is used and arm compiler from montavista. Based on
README of bluez-libs-3.11. I run
configure
--host=/opt/montavista/mobilinux/devkit/arm/v6_vfp_le/bin/arm_v6_vfp_le-
--prefix=/root/Desktop/bluez-libs-3.11
returns error as following, any help would be
appreciated.
configure: WARNING: If you wanted to set the --build
type, don't use --host.
If a cross compiler is detected then cross compile
mode will be used.
checking for a BSD-compatible install...
/usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for
/opt/montavista/mobilinux/devkit/arm/v6_vfp_le/bin/arm_v6_vfp_le--strip...
no
checking for strip... strip
checking whether to enable maintainer-specific
portions of Makefiles... no
checking for
/opt/montavista/mobilinux/devkit/arm/v6_vfp_le/bin/arm_v6_vfp_le--gcc...
no
checking for gcc... gcc
checking for C compiler default output file name...
a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler...
yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none
needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for a BSD-compatible install...
/usr/bin/install -c
checking build system type... i686-redhat-linux-gnu
checking host system type... Invalid configuration
`/opt/montavista/mobilinux/devkit/arm/v6_vfp_le/bin/arm_v6_vfp_le-':
machine
`/opt/montavista/mobilinux/devkit/arm/v6_vfp_le/bin/arm_v6_vfp_le'
not recognized
configure: error: /bin/sh ./config.sub
/opt/montavista/mobilinux/devkit/arm/v6_vfp_le/bin/arm_v6_vfp_le-
failed
----henry
____________________________________________________________________________________
Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games.
http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-08-06 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.151917.1186390010.21973.bluez-devel@lists.sourceforge.net>
2007-08-06 16:40 ` [Bluez-devel] BlueZ version hong zhang
2007-08-08 17:04 ` tjoconno
2007-08-08 17:09 ` Marcel Holtmann
2007-08-06 20:33 ` hong zhang [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=547249.8186.qm@web58008.mail.re3.yahoo.com \
--to=henryzhang62@yahoo.com \
--cc=bluez-devel@lists.sourceforge.net \
/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