From: MK <mailing.m1@kkk-web.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] BATMAN 2018.1 fails to compile
Date: Tue, 31 Jul 2018 21:24:54 +0200 [thread overview]
Message-ID: <bb8d1046-af37-dab3-12ce-46455acedbbf@kkk-web.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1255 bytes --]
Hi!
Since 2018.1 release the batman module fails to compile on my machine:
:~/Server-config/batman-adv-2018.1# make
/root/server-config/batman-adv-2018.1/gen-compat-autoconf.sh
/root/server-config/batman-adv-2018.1/compat-autoconf.h
mkdir -p /root/server-config/batman-adv-2018.1/build/net/batman-adv/
compat-patches/replacements.sh
touch
/root/server-config/batman-adv-2018.1/build/net/batman-adv/.compat-prepared
make -C /lib/modules/4.9.0-7-amd64/build
M=/root/server-config/batman-adv-2018.1/build
PWD=/root/server-config/batman-adv-2018.1/build REVISION=
CONFIG_BATMAN_ADV=m CONFIG_BATMAN_ADV_DEBUG=n
CONFIG_BATMAN_ADV_DEBUGFS=y CONFIG_BATMAN_ADV_BLA=y
CONFIG_BATMAN_ADV_DAT=y CONFIG_BATMAN_ADV_NC=n CONFIG_BATMAN_ADV_MCAST=y
CONFIG_BATMAN_ADV_BATMAN_V=n INSTALL_MOD_DIR=updates/ modules
make[1]: Verzeichnis „/lib/modules/4.9.0-7-amd64/build“ wird betreten
make[1]: *** Keine Regel, um „modules“ zu erstellen. Schluss.
make[1]: Verzeichnis „/lib/modules/4.9.0-7-amd64/build“ wird verlassen
Makefile:90: die Regel für Ziel „all“ scheiterte
make: *** [all] Fehler 2
This is a debian stretch installation. Someone out there with the same
problem? Make clean did not help.
A bit lost :)
Martin
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2018-07-31 19:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 19:24 MK [this message]
2018-07-31 19:58 ` [B.A.T.M.A.N.] BATMAN 2018.1 fails to compile Sven Eckelmann
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=bb8d1046-af37-dab3-12ce-46455acedbbf@kkk-web.de \
--to=mailing.m1@kkk-web.de \
--cc=b.a.t.m.a.n@lists.open-mesh.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 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.