Linux bluetooth development
 help / color / mirror / Atom feed
From: Andrew Kirch <trelane@trelane.net>
To: "Morné Liebenberg" <dtsnamibia@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Bluetooth Help Needed Please
Date: Mon, 24 Jan 2011 22:08:52 -0500	[thread overview]
Message-ID: <4D3E3EC4.3010304@trelane.net> (raw)
In-Reply-To: <AANLkTim-w9rFa-W4HTGW7RBMoMyFUT9-cZ4NnFj0LsaV@mail.gmail.com>

install dbus-dev dbus-devel libdbus, etc

Andrew

On 1/24/2011 9:05 PM, Morné Liebenberg wrote:
> To whom it may concern;
>
> Hi may name is Morne and I'm trying to update my Bluez software but
> get the following errors:
>
> gmg@GMG:~/Downloads/bluez-4.86$ ./configure --prefix=/usr
> --mandir=/usr/share/man \
>> --sysconfdir=/etc --localstatedir=/var --libexecdir=/lib
> 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... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> 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 ISO C89... none needed
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking whether gcc and cc understand -c and -o together... yes
> checking whether gcc accepts -fPIE... yes
> checking for a BSD-compatible install... /usr/bin/install -c
> checking for bison... no
> checking for byacc... no
> checking for flex... no
> checking for lex... no
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> checking for a sed that does not truncate output... /bin/sed
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for fgrep... /bin/grep -F
> checking for ld used by gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
> checking the name lister (/usr/bin/nm -B) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 1572864
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking for /usr/bin/ld option to reload object files... -r
> checking for objdump... objdump
> checking how to recognize dependent libraries... pass_all
> checking for ar... ar
> checking for strip... strip
> checking for ranlib... ranlib
> checking command to parse /usr/bin/nm -B output from gcc object... ok
> checking how to run the C preprocessor... 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 for dlfcn.h... yes
> checking for objdir... .libs
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC -DPIC
> checking if gcc PIC flag -fPIC -DPIC works... yes
> checking if gcc static flag -static works... yes
> checking if gcc supports -c -o file.o... yes
> checking if gcc supports -c -o file.o... (cached) yes
> checking whether the gcc linker (/usr/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
> checking for ppoll... yes
> checking for dlopen in -ldl... yes
> checking for DBUS... no
> configure: error: D-Bus library is required
> gmg@GMG:~/Downloads/bluez-4.86$
>
> Could you perhaps help me with this update issue...
>
> The other issue I am having is receiving calls to my cellphone and
> playing the person who is calling via my computer speakers using a
> blue-tooth dongle.
> Otherwise if it's not possible then I could just might as well buy a
> blue-tooth earpiece, disconnect it's small speaker and connect it to
> my amp but will only have mono sound
>
> Anyways please help me on this issue...i would be gratefull if any
> good news came back
>
> Thank you
> Morne
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" 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:[~2011-01-25  3:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25  2:05 Bluetooth Help Needed Please Morné Liebenberg
2011-01-25  3:08 ` Andrew Kirch [this message]
2011-01-25  4:55   ` Arun K. Singh

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=4D3E3EC4.3010304@trelane.net \
    --to=trelane@trelane.net \
    --cc=dtsnamibia@gmail.com \
    --cc=linux-bluetooth@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