From: 4ricci <4ricci@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] constraints disabled in openntpd after the switch to openssl
Date: Tue, 09 Mar 2021 13:20:14 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29347@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2567 bytes --]
New issue by 4ricci on void-packages repository
https://github.com/void-linux/void-packages/issues/29347
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
Void 5.10.20_1 x86_64 GenuineIntel uptodate rrFFFFFF
* package:
openntpd-6.2p3_8 and #27053
### Expected behavior
If constraints are enabled in `/etc/ntpd.conf`, then `ntpctl -s status` should print something like:
```
4/4 peers valid, constraint offset 0s, clock synced, stratum 3
```
`xbps-query -x openntpd` should print:
```
ca-certificates>=0
glibc>=2.32_1
libtls>=3.2.4_1
```
### Actual behavior
`ntpctl -s status` says nothing about constraints:
```
4/4 peers valid, clock synced, stratum 3
```
and the package does not depend on libtls at runtime.
I was able to link openntpd against libtls (and enable contraints support) by adding opennssl-devel to makedepends. I think that the configure script relies on some part of openssl/libressl that is not included in our standalone libtls to detect the latter, but I'm not sure about the correct way to fix that.
This is the build log with the actual template:
```
[...]
=> openntpd-6.2p3_8: installing target dependencies: libtls-devel-3.2.4_2 ...
[...]
checking for library containing tls_config_set_ca_mem... no
checking for tls_config_set_ca_mem... no
checking if tls_write takes 3 arguments... no
[...]
CC ntpd-constraint-disabled.o
[...]
=> openntpd-6.2p3_8: running pre-pkg hook: 04-generate-runtime-deps ...
SONAME: libm.so.6 <-> glibc>=2.32_1
SONAME: libc.so.6 <-> glibc>=2.32_1
[...]
=> openntpd-6.2p3_8: running pre-pkg hook: 999-collected-rdeps ...
ca-certificates>=0 glibc>=2.32_1
[...]
```
and this is with makedepends including openssl-devel:
```
[...]
=> openntpd-6.2p3_8: installing target dependencies: libtls-devel-3.2.4_2 openssl-devel-1.1.1j_2 ...
[...]
checking for library containing tls_config_set_ca_mem... -ltls
checking for tls_config_set_ca_mem... yes
checking if tls_write takes 3 arguments... yes
[...]
CC ntpd-constraint.o
[...]
=> openntpd-6.2p3_8: running pre-pkg hook: 04-generate-runtime-deps ...
SONAME: libm.so.6 <-> glibc>=2.32_1
SONAME: libtls.so.20 <-> libtls>=3.2.4_1
SONAME: libc.so.6 <-> glibc>=2.32_1
[...]
=> openntpd-6.2p3_8: running pre-pkg hook: 999-collected-rdeps ...
ca-certificates>=0 glibc>=2.32_1 libtls>=3.2.4_1
[...]
```
next reply other threads:[~2021-03-09 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 12:20 4ricci [this message]
2021-03-10 11:34 ` leahneukirchen
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29347@inbox.vuxu.org \
--to=4ricci@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).