From: Ismael Valladolid Torres <ivalladt@punkass.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Error trying to build bluez-utils
Date: Thu, 05 Jul 2007 13:26:39 +0200 [thread overview]
Message-ID: <20070705112639.GB3575@punkass.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 845 bytes --]
test -f lexer.c || /bin/sh ../ylwrap lexer.l .c lexer.c -- /bin/sh /usr/src/bluez/utils/missing --run flex
/usr/src/bluez/utils/hcid/ylwrap20111
make[3]: *** [lexer.c] Error 1
make[3]: Leaving directory `/usr/src/bluez/utils/hcid'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/usr/src/bluez/utils/hcid'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/bluez/utils'
make: *** [all] Error 2
On my Debian sid I've instaled these packages apart from
build-essential which was already installed: automake, libtool,
libdbus-1-dev, bison and flex.
Any ideas welcome.
Cordially, Ismael
--
Ismael Valladolid Torres GnuPG key: DE721AF4
Jabber: ivalladt@gmail.com
http://linuxav.blogspot.com Skype: ivalladt
http://lamediahostia.blogspot.com/
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 286 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
[-- 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:[~2007-07-05 11:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070705112639.GB3575@punkass.com \
--to=ivalladt@punkass.com \
--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