From: Lopsch <lopsch@lopsch.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Shared object not being built by patch-o-matic-ng
Date: Thu, 18 Nov 2004 15:56:56 +0000 [thread overview]
Message-ID: <419CC648.6090002@lopsch.com> (raw)
In-Reply-To: <1100769962.23414.18.camel@tux.it-akademiet.no>
Stian B. Barmen schrieb:
> I try to use patch-o-matic-ng for installation. Kernel patching works
> nicely but the libipt_ipp2p.so shared object does not get built. I find
> the .c file in the patch-o-matic tree under ipp2p but I don't know how
> to manually compile it.
> My lsmod includes the sucsessfully made ipt_ipp2p module and I also
> recompiled iptables for good measure.
> Help anyone?
>
> Best regards
> Stian B. Barmen
>
Just copy the iptables files from pom-ng to iptables dir in the correct
location, change permissions if necessary and just build the iptables again.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-11-18 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 9:26 [LARTC] Shared object not being built by patch-o-matic-ng Stian B. Barmen
2004-11-18 15:56 ` Lopsch [this message]
2004-11-19 8:50 ` Stian B. Barmen
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=419CC648.6090002@lopsch.com \
--to=lopsch@lopsch.com \
--cc=lartc@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.