From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Kernel patch - ERROR KCFG= FAIL
Date: Tue, 19 Feb 2019 11:25:44 +0000 [thread overview]
Message-ID: <2528C607-55C3-4AC3-A712-B18A3020A79E@ipfire.org> (raw)
In-Reply-To: <34687f7a87d1ea578a58ce3ef2136c56af691a62.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1513 bytes --]
Hi,
The error message is probably quite a bit before the end of the log.
What is this patch for?
-Michael
> On 19 Feb 2019, at 11:22, ummeegge <ummeegge(a)ipfire.org> wrote:
>
> Hi all,
> am trying currently to patch the kernel for nDPI-netfilter and am
> getting an error which i can´t solve. The patch is from here -->
> https://github.com/vel21ripn/nDPI/blob/netfilter-2.2/ndpi-netfilter/kernel-patch/v4.14.0.diff
> and it does apply but the kernel quits after sometime with
>
> CC [M] drivers/net/wireless/ti/wlcore/sdio.o
> LD [M] drivers/net/wireless/ti/wlcore/wlcore_sdio.o
> LD [M] drivers/net/wireless/ti/wlcore/wlcore.o
> AR drivers/net/wireless/ti/built-in.o
> AR drivers/net/wireless/built-in.o
> AR drivers/net/built-in.o
> AR drivers/built-in.o
> make[1]: Leaving directory '/usr/src/linux-4.14.97'
> make: *** [linux:149: /usr/src/log/linux-4.14.97-ipfire] Error
>
> ERROR: Building linux KCFG= [ FAIL ]
> Check /var/dev-ipfire_20190118_1813/ipfire-2.x/log/_build.ipfire.log for errors if applicable
>
>
> so may there is a simple solution for the "KCFG= ERROR". Since i do not
> really have much experience in kernel development i decided to ask the
> list for potential help...
>
> Might be great if someone do have a hint for me ?
>
> Best,
>
> Erik
>
next prev parent reply other threads:[~2019-02-19 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 11:22 ummeegge
2019-02-19 11:25 ` Michael Tremer [this message]
2019-02-19 15:07 ` ummeegge
2019-02-19 16:20 ` Michael Tremer
2019-02-19 17:21 ` ummeegge
2019-02-25 13:32 ` ummeegge
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=2528C607-55C3-4AC3-A712-B18A3020A79E@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox