All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: xtables-addons link error
Date: Sat, 14 Apr 2012 15:42:08 +0100	[thread overview]
Message-ID: <4F898CC0.6080806@googlemail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1204141007590.1110@frira.zrqbmnf.qr>


> As a temporary mitigation, please set build_ECHO=n in the mconfig file.
>   
Will do, thanks. That will exclude the ECHO module from the final build 
I take it, right?

On a side note - since I am building/testing kernels for various 
purposes more often than compiling/building xta kernel modules (I am 
also pretty fed up with having to build/reinstall my buildsys packages 
every time I move to another kernel!), I decided to incorporate the xta 
kernel modules as a kernel patch instead of building them separately 
each time I build a kernel for testing.

I remember getting the above errors, but since it was the first time I 
have attempted to include the xta modules as a patch, I thought that I 
must be doing something wrong. In addition to the above errors I also 
got a separate error, which stemmed from one of the xta kernel modules 
(I think it was DNETMAP) using/depending on a separate .o/.so kernel 
file being built prior to it, hence a few other unresolved symbols 
during linking. It was the reason I abandoned this effort pretty quickly.

Has this been attempted before - to include the xta modules as part of 
the kernel? If there is an interest, I could dig in again to see what 
other linking errors was I getting - just let me know.

  reply	other threads:[~2012-04-14 14:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04  2:34 xtables-addons compile error Mr Dash Four
2012-04-05  5:24 ` Jan Engelhardt
2012-04-05 11:01   ` Mr Dash Four
2012-04-14  2:58     ` xtables-addons link error Mr Dash Four
2012-04-14  8:28       ` Jan Engelhardt
2012-04-14 14:42         ` Mr Dash Four [this message]
2012-04-14 14:59           ` Mr Dash Four

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=4F898CC0.6080806@googlemail.com \
    --to=mr.dash.four@googlemail.com \
    --cc=jengelh@medozas.de \
    --cc=netfilter-devel@vger.kernel.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.