From: Max Kellermann <max@duempel.org>
To: netfilter-devel@lists.netfilter.org
Subject: nfsim on amd64: va_list incompatible type error
Date: Fri, 7 Jan 2005 00:57:48 +0100 [thread overview]
Message-ID: <20050106235748.GA23714@roonstrasse.net> (raw)
Hi,
I'm trying to get nfsim running on my Athlon 64.. (nfsim is definitely
cool stuff! I'll use it to test my H.323 ct helper module)
The easiest thing first: the README should mention that you need the
libreadline headers to compile (libreadline4-dev on Debian).
I applied Patrick's 4 patches to my svn/trunk working copy, they fixed
a lot of error messages concerning 64 bit portability. Plus, I had to
add 24 dummy bytes to pad cmdline_option (also Patrick's idea).
gcc -Wmissing-prototypes -Wstrict-prototypes -Wunused -Wall -g -Wa,-W
-I. -I/home/max/svn/nfsim/core -I/home/max/svn/nfsim/kernelenv/include
-I/home/max/svn/nfsim/netfilter/include -c -o core/talloc.o
core/talloc.c
core/talloc.c: In function `talloc_vasprintf':
core/talloc.c:862: error: incompatible types in assignment
core/talloc.c:868: error: incompatible types in assignment
core/talloc.c: In function `talloc_vasprintf_append':
core/talloc.c:906: error: incompatible types in assignment
core/talloc.c:918: error: incompatible types in assignment
both gcc 1:3.3.5-5 and 3.4.3-6 (Debian) are affected. I found several
references to this behaviour on the net, one is a gcc bug report:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8262
.. but I fail to understand how to go around this limitation. When I
defined HAVE_VA_COPY as a workaround, the error went away. Where is
HAVE_VA_COPY meant to be defined?
nfsim works now, although most tests from nfsim-testsuite fail, is
that correct? (on my P4 @work, nfsim segfaults, I'll analyze that
tomorrow).
Max
next reply other threads:[~2005-01-06 23:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 23:57 Max Kellermann [this message]
2005-01-07 0:30 ` nfsim on amd64: va_list incompatible type error Patrick McHardy
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=20050106235748.GA23714@roonstrasse.net \
--to=max@duempel.org \
--cc=netfilter-devel@lists.netfilter.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.