From: Patrick McHardy <kaber@trash.net>
To: wolf@sarchasm.us
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Possible 32/64-bit issue building/using iptables 1.3.7 with UML ("ERROR: 0 not a valid target)")
Date: Mon, 25 Jun 2007 12:26:30 +0200 [thread overview]
Message-ID: <467F9856.8030409@trash.net> (raw)
In-Reply-To: <20070624181050.520b2179@megumi.wolf.fhi>
Adam Snodgrass wrote:
> On Sat, 23 Jun 2007 16:08:06 +0200
> Patrick McHardy <kaber@trash.net> wrote:
>
>
>>>guest# ./iptables -V
>>>iptables v1.3.7
>>>guest# ./iptables -nL
>>>ERROR: 0 not a valid target)
>>
>>Thats really strange. Could you try again with current -rc? I fixed
>>the default table initialization so you might get a better error
>>message.
>>
>
>
> I pulled down a fresh copy of svn (I presume this is what you meant,
> as I didn't see any newer releases than 1.3.7), and built a new set of
> binaries, and ran into the same problem. I had a sneaking suspicion
> about the kernel tree I was building against, however, and decided to
> swap it with a fresh one. Another compile later, and I now have
> working binaries for my i386 umls. The only difference between my
> kernel trees is that the former was originally used to build my amd64
> uml kernels. This is strange to me, as I thought that iptables only
> needed access to the headers?
Its possible that some alignment constant or a data type depends
on a correctly setup include/asm symlink. Doesn't seem to be a
bug at least ..
prev parent reply other threads:[~2007-06-25 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 5:36 Possible 32/64-bit issue building/using iptables 1.3.7 with UML ("ERROR: 0 not a valid target)") Adam Snodgrass
2007-06-23 14:08 ` Patrick McHardy
2007-06-24 22:10 ` Adam Snodgrass
2007-06-25 10:26 ` Patrick McHardy [this message]
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=467F9856.8030409@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=wolf@sarchasm.us \
/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.