From: Mika Linnanoja <mika.linnanoja@nokia.com>
To: padovan@profusion.mobi
Cc: linux-bluetooth <linux-bluetooth@vger.kernel.org>,
Ville Tervo <ville.tervo@nokia.com>
Subject: latest bluetooth-next doesn't compile
Date: Thu, 28 Apr 2011 14:25:38 +0300 [thread overview]
Message-ID: <4DB94EB2.5060204@nokia.com> (raw)
Hi!
I cloned today
git://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth-next-2.6.git
and seems it does not want to fully compile.
Steps were like this:
$ git clone <url>
$ cd <git_dir>
$ cp /boot/old_config_file .config
$ make oldconfig (default answers)
$ make
CHK include/linux/version.h
CHK include/generated/utsrelease.h
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
UPD include/generated/compile.h
CC init/version.o
LD init/built-in.o
VDSOSYM arch/x86/vdso/vdso32-int80-syms.lds
VDSOSYM arch/x86/vdso/vdso32-sysenter-syms.lds
VDSOSYM arch/x86/vdso/vdso32-syms.lds
LD arch/x86/vdso/built-in.o
LD arch/x86/built-in.o
CC [M] net/bluetooth/cmtp/core.o
net/bluetooth/cmtp/core.c: In function ‘cmtp_add_connection’:
net/bluetooth/cmtp/core.c:349: error: ‘struct l2cap_pinfo’ has no member named
‘omtu’
net/bluetooth/cmtp/core.c:349: error: ‘struct l2cap_pinfo’ has no member named
‘imtu’
make[3]: *** [net/bluetooth/cmtp/core.o] Error 1
make[2]: *** [net/bluetooth/cmtp] Error 2
make[1]: *** [net/bluetooth] Error 2
make: *** [net] Error 2
$
Is this a known issue? I have not tried to build this exact tree before.
BR,
Mika
next reply other threads:[~2011-04-28 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 11:25 Mika Linnanoja [this message]
2011-04-28 14:35 ` latest bluetooth-next doesn't compile Gustavo F. Padovan
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=4DB94EB2.5060204@nokia.com \
--to=mika.linnanoja@nokia.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=padovan@profusion.mobi \
--cc=ville.tervo@nokia.com \
/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;
as well as URLs for NNTP newsgroup(s).