public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: pramod gurav <pramod_gurav_etc@yahoo.co.in>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluetooth compilation version3.36 -regarding
Date: Mon, 14 Jul 2008 16:20:56 +0530 (IST)	[thread overview]
Message-ID: <20306.69710.qm@web8401.mail.in.yahoo.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 6400 bytes --]

Hi Umesh 
configure has failed.
Cross compile dbus first and its dependancies(libxml only)
provide path to it also. bluez depends in dbus thoroughly. and dbus on libxml.

please compile them and again try bluez.

 Thanks and Best regards


Pramod



----- Original Message ----
From: umeshyv <umeshyv@gmail.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Sent: Monday, 14 July, 2008 4:12:51 PM
Subject: [Bluez-users] bluetooth compilation version3.36 -regarding

Hi to all,
I started compiling bluetooth libs and utils version 3.36 ,I followed the earlier methods but following are the errors,please rectify me where I am going wrong and for version 3.32 I submitted the compilation errors and I am stuck up with it.

Compiling Bluetooth libraries

>Apply Buildroot or Toolchain Path
>./configure --host=mipsel-linux --prefix=/usr --enable-shared=no --enable-static=yes
>make
>make install DESTDIR=/home/newbuild/blue/bluez-libs-3.36/install

Compiling Bluetooth Utils

linux:/home/newbuild/blue/bluez-utils-3.36 # export BLUEZ_CFLAGS=-I /home/newbuild/blue/bluez-libs-3.32/install/usr/include
linux:/home/newbuild/blue/bluez-utils-3.36 # export BLUEZ_LIBS="-L/home/newbuild/blue/bluez-libs-3.32/install/usr/lib -lbluetooth"
linux:/home/newbuild/blue/bluez-utils-3.36 # ./configure --host=mipsel-linux --with-bluez=/home/newbuild/blue/bluez-libs-3.36/install/usr/ CPPFLAGS="-D__KERNEL__"
After configuration 
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 a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for mipsel-linux-strip... mipsel-linux-strip
checking whether to enable maintainer-specific portions of Makefiles... no
checking for mipsel-linux-gcc... mipsel-linux-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... yes
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether mipsel-linux-gcc accepts -g... yes
checking for mipsel-linux-gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of mipsel-linux-gcc... gcc3
checking whether mipsel-linux-gcc accepts -fPIE... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for bison... bison -y
checking for flex... flex
checking lex output file root... lex.yy
checking lex library... none needed
checking whether yytext is a pointer... no
checking build system type... i686-pc-linux-gnu
checking host system type... mipsel-unknown-linux-gnu
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ld used by mipsel-linux-gcc... /home/newbuild/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/bin/ld
checking if the linker (/home/newbuild/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/bin/ld) is GNU ld... yes
checking for /home/newbuild/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /home/newbuild/buildroot/build_mipsel/staging_dir/bin/mipsel-linux-nm -B
checking whether ln -s works... yes
checking how to recognize dependent libraries... pass_all
checking how to run the C preprocessor... mipsel-linux-gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking the maximum length of command line arguments... 98304
checking command to parse /home/newbuild/buildroot/build_mipsel/staging_dir/bin/mipsel-linux-nm -B output from mipsel-linux-gcc object... ok
checking for objdir... .libs
checking for mipsel-linux-ar... mipsel-linux-ar
checking for mipsel-linux-ranlib... mipsel-linux-ranlib
checking for mipsel-linux-strip... (cached) mipsel-linux-strip
checking if mipsel-linux-gcc supports -fno-rtti -fno-exceptions... no
checking for mipsel-linux-gcc option to produce PIC... -fPIC
checking if mipsel-linux-gcc PIC flag -fPIC works... yes
checking if mipsel-linux-gcc static flag -static works... yes
checking if mipsel-linux-gcc supports -c -o file.o... yes
checking whether the mipsel-linux-gcc linker (/home/newbuild/buildroot/build_mipsel/staging_dir/mipsel-linux-uclibc/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
checking for ppoll... yes
checking for mipsel-linux-pkg-config... no
checking for pkg-config... /usr/bin/pkg-config
configure: WARNING: In the future, Autoconf will not detect cross-tools
whose name does not start with the host triplet.  If you think this
configuration is useful to you, please write to autoconf@gnu.org.
checking pkg-config is at least version 0.9.0... yes
checking for BLUEZ... yes
checking for GLIB... no
checking for GMODULE... no
checking for dlopen in -ldl... yes
checking for DBUS... no
configure: error: D-Bus library is required

linux:/home/newbuild/blue/bluez-utils-3.32 # make

linux:/home/newbuild/blue/bluez-utils-3.36 # make
make: *** No targets specified and no makefile found.  Stop.

Waiting for valuable suggestions

Thanks & Regards
Umesh



      From Chandigarh to Chennai - find friends all over India. Go to http://in.promos.yahoo.com/groups/citygroups/

[-- Attachment #1.2: Type: text/html, Size: 7372 bytes --]

[-- Attachment #2: Type: text/plain, Size: 347 bytes --]

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2008-07-14 10:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 10:50 pramod gurav [this message]
2008-07-14 11:06 ` [Bluez-users] bluetooth compilation version3.36 -regarding umeshyv
  -- strict thread matches above, loose matches on Subject: below --
2008-07-14 11:40 pramod gurav
2008-07-14 12:00 ` umeshyv
2008-07-14 11:01 pramod gurav
2008-07-14 10:42 umeshyv

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=20306.69710.qm@web8401.mail.in.yahoo.com \
    --to=pramod_gurav_etc@yahoo.co.in \
    --cc=bluez-users@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