From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] pskey gone, but bccmd won't build
Date: Sun, 15 Oct 2006 15:18:57 -0600 [thread overview]
Message-ID: <4532A5C1.4080504@xmission.com> (raw)
In-Reply-To: <1160943663.14340.10.camel@localhost>
Marcel
>> I noticed pskey disappear from utils/tools in cvs. Is bccmd preferred
>> for setting pskey values? bccmd won't build from the current utils.
>
> bccmd is the successor of pskey and you should use --enable-bccmd to
> build and install it correctly.
(I can't do a toplevel make: there is a dbus problem on ubuntu and
--disable-dbus doesn't really disable dbus)
shouldn't this work?
$ ./configure --enable-bccmd
...
$ make -C common/
...
$ make -C tools
...
$ make -C tools bccmd
make: Entering directory
`/media/usbdisk/goo/home/bmidgley/src/bluez/utils/tools'
/bin/sh ../libtool --mode=link gcc -I/usr/local/include
-I/usr/local/include -Wall -O2 -D_FORTIFY_SOURCE=2 -o bccmd
gcc -I/usr/local/include -I/usr/local/include -Wall -O2
-D_FORTIFY_SOURCE=2 -o bccmd
gcc: no input files
make: *** [bccmd] Error 1
make: Leaving directory
`/media/usbdisk/goo/home/bmidgley/src/bluez/utils/tools'
Brad
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-10-15 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-15 20:14 [Bluez-devel] pskey gone, but bccmd won't build Brad Midgley
2006-10-15 20:21 ` Marcel Holtmann
2006-10-15 21:18 ` Brad Midgley [this message]
2006-10-15 21:29 ` Marcel Holtmann
2006-10-15 23:00 ` Brad Midgley
2006-10-16 10:40 ` Peter Wippich
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=4532A5C1.4080504@xmission.com \
--to=bmidgley@xmission.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 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.