From: DVornheder@t-online.de (Dirk Vornheder)
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Compile bluez-bluefw-1.0 fails
Date: Sun, 18 Apr 2004 23:21:55 +0200 [thread overview]
Message-ID: <200404182321.55431.dvornheder@t-online.de> (raw)
Hi !
Compile bluez-bluefw-1.0 fails:
make[1]: Leaving directory `/privat/bluetooth/bluez-bluefw-1.0/hotplug'
make[1]: Entering directory `/privat/bluetooth/bluez-bluefw-1.0'
source='bluefw.c' object='bluefw.o' libtool=no \
depfile='.deps/bluefw.Po' tmpdepfile='.deps/bluefw.TPo' \
depmode=gcc3 /bin/sh ./depcomp \
gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\"
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"bluez-bluefw\"
-DVERSION=\"1.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DBT3C_SUPPORT=1 -I.
-I. -I/usr/src/linux/include -Wall -g -O2 -c `test -f 'bluefw.c' || echo
'./'`bluefw.c
In file included from usblib.h:30,
from bluefw.c:39:
/usr/src/linux/include/linux/usbdevice_fs.h:49: error: variable or field
`__user' declared void
/usr/src/linux/include/linux/usbdevice_fs.h:49: warning: no semicolon at end
of struct or union
/usr/src/linux/include/linux/usbdevice_fs.h:49: error: parse error before '*'
token
/usr/src/linux/include/linux/usbdevice_fs.h:56: error: variable or field
`__user' declared void
/usr/src/linux/include/linux/usbdevice_fs.h:56: warning: no semicolon at end
of struct or union
/usr/src/linux/include/linux/usbdevice_fs.h:56: error: parse error before '*'
token
/usr/src/linux/include/linux/usbdevice_fs.h:100: error: variable or field
`__user' declared void
/usr/src/linux/include/linux/usbdevice_fs.h:100: warning: no semicolon at end
of struct or union
/usr/src/linux/include/linux/usbdevice_fs.h:100: error: parse error before '*'
token
/usr/src/linux/include/linux/usbdevice_fs.h:109: error: parse error before '}'
token
/usr/src/linux/include/linux/usbdevice_fs.h:116: error: variable or field
`__user' declared void
/usr/src/linux/include/linux/usbdevice_fs.h:116: warning: no semicolon at end
of struct or union
/usr/src/linux/include/linux/usbdevice_fs.h:116: error: parse error before '*'
token
make[1]: *** [bluefw.o] Error 1
I use kernel 2.6.6-rc1-bk2 !
Dirk
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2004-04-18 21:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-18 21:21 Dirk Vornheder [this message]
2004-04-18 21:55 ` [Bluez-users] Compile bluez-bluefw-1.0 fails Marcel Holtmann
2004-04-19 8:35 ` Alex Holland
2004-04-19 10:23 ` Marcel Holtmann
2004-04-19 13:19 ` Alex Holland
2004-04-19 13:30 ` Marcel Holtmann
2004-04-19 13:41 ` Alex Holland
2004-04-19 13:54 ` Marcel Holtmann
2004-04-19 15:39 ` Alex Holland
2004-04-19 16:12 ` Marcel Holtmann
2004-04-19 17:22 ` Alex Holland
2004-04-19 17:52 ` Simone Gotti
2004-04-19 20:21 ` Alex Holland
2004-04-20 9:28 ` Alex Holland
2004-04-20 11:56 ` Marcel Holtmann
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=200404182321.55431.dvornheder@t-online.de \
--to=dvornheder@t-online.de \
--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