From: Duncan Roe <duncan_roe@optusnet.com.au>
To: "G.W. Haywood" <ged@jubileegroup.co.uk>
Cc: Netfilter Development <netfilter-devel@vger.kernel.org>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Subject: Re: Documentation oddity.
Date: Tue, 11 Mar 2025 11:00:32 +1100 [thread overview]
Message-ID: <Z899IF0jLhUMQLE4@slk15.local.net> (raw)
In-Reply-To: <4991be2e-3839-526f-505e-f8dd2c2fc3f3@jubileegroup.co.uk>
Hi Ged,
On Mon, Mar 10, 2025 at 06:00:40PM +0000, G.W. Haywood wrote:
> Hi there,
>
> Another one for you.
>
> In the docs at
>
> https://www.netfilter.org/projects/libnetfilter_queue/doxygen/html/
>
> there is given a command to compile the sample code in nf-queue.c.
>
> The command given is
>
> gcc -g3 -ggdb -Wall -lmnl -lnetfilter_queue -o nf-queue nf-queue.c
>
> Here, and I suspect almost everywhere else, that doesn't work.
Works here with gcc versions 11.2.0 and 14.2.0.
>
> Should the command not be something more like the one below?
>
> gcc -o nf-queue nf-queue.c -g3 -ggdb -Wall -lmnl -lnetfilter_queue
gcc doesn't care, but the conventional order for command arguments is option
args first, as in the docs.
>
The -ggdb argument is obsolete and may be slated for removal. Can you please try
this:
gcc -g3 -gdwarf-4 -Wall -lmnl -lnetfilter_queue -o nf-queue nf-queue.c
If it still fails for you, please let me know at least 2 things:
1. What is the error message
2. The first line output bu the command "gcc --version"
Cheers ... Duncan.
next prev parent reply other threads:[~2025-03-11 0:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 15:20 Documentation oddity G.W. Haywood
2024-12-19 9:22 ` Jozsef Kadlecsik
2025-03-10 18:00 ` G.W. Haywood
2025-03-11 0:00 ` Duncan Roe [this message]
2025-03-11 10:00 ` G.W. Haywood
2025-03-12 6:21 ` Duncan Roe
2025-03-12 9:48 ` G.W. Haywood
2025-03-13 10:04 ` Duncan Roe
2025-03-28 13:55 ` G.W. Haywood
2025-04-02 9:36 ` Duncan Roe
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=Z899IF0jLhUMQLE4@slk15.local.net \
--to=duncan_roe@optusnet.com.au \
--cc=ged@jubileegroup.co.uk \
--cc=kadlec@blackhole.kfki.hu \
--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.