Github messages for voidlinux
 help / color / mirror / Atom feed
From: ailiop-git <ailiop-git@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ulogd: enable pcap output as a build option
Date: Thu, 10 Jun 2021 11:40:49 +0200	[thread overview]
Message-ID: <20210610094049.AuKMec_IQCVzicHtuOgHDx2bKwCMa7_YiK0SsMvgyY0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31331@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 2219 bytes --]

New comment by ailiop-git on void-packages repository

https://github.com/void-linux/void-packages/pull/31331#issuecomment-858473922

Comment:
> It doesn't seem to have created any additional dependency in the binary package, I assume because it dlopens things?

Good catch. Yes, ulogd dlopens all the plugins, but that's not all. Wouldn't 04-generate-runtime-deps.sh scan all the shared objects anyway and pick up the deps?

I think the issue is that the particular plugin doesn't actually depend on libpcap at runtime:
```
$ ldd ulogd_output_PCAP.so                                                                                                                                                      
        linux-vdso.so.1 (0x00007ffd0b919000)                                                                                                                                                                                     
        libc.so.6 => /usr/lib/libc.so.6 (0x00007f68d00bc000)                                                                                                                                                                     
        /usr/lib64/ld-linux-x86-64.so.2 (0x00007f68d028e000) 
```
despite the plugin being compiled with the intention of linking against libpcap:

`libtool: link: cc -shared -Wl,--as-needed  -fPIC -DPIC  .libs/ulogd_output_PCAP.o   -lpcap  -mtune=generic -O2 -g -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed   -Wl,-soname -Wl,ulogd_output_PCAP.so -o .libs/ulogd_output_PCAP.so                                                                                                                                                                                                                             `

That's because from what is seems there's really no actual code dependency to libpcap (the ulog plugin output doesn't use any functionality), so it only needs pcap.h during compilation for some structs.

So we really don't need the build option (not for the pcap output plugin at least), so I'll push again making it unconditional.

I suppose also a patch is needed for upstream to remove linking against pcap since this is not really needed.

  parent reply	other threads:[~2021-06-10  9:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-06 23:15 [PR PATCH] " ailiop-git
2021-06-07 13:58 ` ahesford
2021-06-07 14:04 ` ailiop-git
2021-06-10  0:57 ` ericonr
2021-06-10  9:40 ` ailiop-git [this message]
2021-06-10  9:44 ` [PR PATCH] [Updated] " ailiop-git
2021-06-10 14:45 ` [PR PATCH] [Merged]: " ericonr
2021-06-10 14:45 ` ericonr

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=20210610094049.AuKMec_IQCVzicHtuOgHDx2bKwCMa7_YiK0SsMvgyY0@z \
    --to=ailiop-git@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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 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).