netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Neal P. Murphy" <neal.p.murphy@alum.wpi.edu>
To: nhhabsburglothringen <nhhabsburglothringen@gmail.com>
Cc: "netfilter-devel@vger.kernel.org"
	<netfilter-devel@vger.kernel.org>,
	"netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: iptables: undefined symbol: xtables_find_target_revision
Date: Sat, 13 Apr 2019 18:32:29 +0000	[thread overview]
Message-ID: <20190413143226.1f9412e2@playground> (raw)
In-Reply-To: <2b4c9c9a-7524-8d72-26f4-34bf2eb95182@gmail.com>

Actually, because it's 'xtlibDIR', I believe the option should be
    --with-xtlibdir=/lib


On Sat, 13 Apr 2019 11:24:46 +0200
nhhabsburglothringen <nhhabsburglothringen@gmail.com> wrote:

> More interesting suggestion, very very thank.
> 
> Today I will try to compiling with the modifications suggested and I
> will send the result.
> 
> Actualy, in my sistem (debian 9):
> 
> in /lib I have the libxtables.so.12.2.0 and the directory xtables with
> all other
> library;
> 
> I have not the /usr/lib64;
> 
> in /lib64 I have only one symbolic link to ld-linux-x86-64.so.2 that
> point to /lib/x86_64-linux-gnu/ld-2.24.so.
> 
> I will try with and without the directive --libdir=/lib/x86_64-linux-gnu
> (that may is the correct pat for my 64bit library).
> 
> After done, I will report the result
> 
> Emy
> 
> 
> 
> Il 13/04/2019 02:42, Duncan Roe ha scritto:
> > On Sat, Apr 13, 2019 at 01:07:36AM +0200, nhhabsburglothringen wrote:  
> >>
> >>
> >> -------- Messaggio Inoltrato --------
> >> Oggetto: 	Re: iptables: undefined symbol: xtables_find_target_revision
> >> Data: 	Sat, 13 Apr 2019 00:56:20 +0200
> >> Mittente: 	nhhabsburglothringen <nhhabsburglothringen@gmail.com>
> >> A: 	Duncan Roe <duncan_roe@optusnet.com.au>
> >>
> >>
> >>
> >> Hi, thank you.
> >>
> >> I have test the 1.8.2 and the 1.8.0 with the same result.
> >>
> >> The older 1.6.2, working fine (I have completed the check).
> >>
> >> May be there are a bug ?
> >>
> >> Emy
> >>
> >> Il 10/04/2019 13:11, Duncan Roe ha scritto:  
> >>> On Wed, Apr 10, 2019 at 11:09:25AM +0200, nhhabsburglothringen wrote:  
> >>>> Seems to be a problem of version 1.8 because compiling the 1.6.2 whitout
> >>>> any modify, all working fine (I reserve further checks but it seems to
> >>>> be so).
> >>>>
> >>>> Can be a problem linked to the new name *legacy (maybe some library
> >>>> don't recognize it).
> >>>>
> >>>> Any idea ?
> >>>>
> >>>> Emy
> >>>>
> >>>> Il 09/04/2019 21:14, nhhabsburglothringen ha scritto:  
> >>>>> Hi to all.
> >>>>>
> >>>>> I have compiled from source iptables v1.8.2 on debian 9 with a kernel
> >>>>> 4.9.144-rt93 64bit also recompiled for enable use of imq as module and
> >>>>> other stuff.
> >>>>>
> >>>>> no error configurig (./configure CFLAGS="-ggdb3 -O0 -DDEBUG"
> >>>>> --prefix=/usr --sbindir=/sbin --enable-libipq --enable-bpf-compiler
> >>>>> --with-xtlibdir=/lib/xtables) nor during compiling with make, but
> >>>>> running when I try to write a rule (for example: iptables -I FORWARD -j
> >>>>> port-filter (after iptables -N port-filter) if I type iptables -L I get
> >>>>> this error:
> >>>>>
> >>>>> Chain INPUT (policy ACCEPT)
> >>>>> target     prot opt source               destination
> >>>>>
> >>>>> Chain FORWARD (policy ACCEPT)
> >>>>> target     prot opt source               destination
> >>>>>
> >>>>> iptables: symbol lookup error: iptables: undefined symbol:
> >>>>> xtables_find_target_revision
> >>>>>
> >>>>> There are some person that can help me ?
> >>>>>
> >>>>> Thank in advance,
> >>>>>
> >>>>> Emilio  
> >>> --
> >>>  Please avoid sending me Word or PowerPoint attachments.
> >>>  See http://www.gnu.org/philosophy/no-word-attachments.html
> >>>
> >>> 1.8.1 is latest.
> >>>
> >>> xtables_find_target_revision is supplied by libxtables.so.12.1.0
> >>>
> >>> Hope that's some help,
> >>>
> >>> Cheers ... Duncan.  
> > Hi Emy,
> >
> > Your ./config directive --with-xtlibdir=/lib/xtables looks wrong to me - I think
> > it should be --with-xtlibdir=/lib/libxtables
> >                                   ~~~
> >
> > Why do you think you need it anyway? I would miss it out.
> >
> > When building for 64-bit, I always include --libdir=/usr/lib64. Maybe some
> > Makefiles look after that but it's in the SlackBuild template so I always use
> > it.
> >
> > Cheers ... Duncan.  
> 


           reply	other threads:[~2019-04-13 18:32 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <2b4c9c9a-7524-8d72-26f4-34bf2eb95182@gmail.com>]

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=20190413143226.1f9412e2@playground \
    --to=neal.p.murphy@alum.wpi.edu \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=netfilter@vger.kernel.org \
    --cc=nhhabsburglothringen@gmail.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).