From: chloris-pale-green <chloris-pale-green@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: opendkim-2.10.3_12: missing dependency `perl`
Date: Wed, 13 Jul 2022 18:36:15 +0200 [thread overview]
Message-ID: <20220713163615.UTEJJ8Nc8d2rm0BfU2ZRJlFmtih2L_9w7zrb9mzGFeA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38036@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
New comment by chloris-pale-green on void-packages repository
https://github.com/void-linux/void-packages/issues/38036#issuecomment-1183440386
Comment:
> configure can't find strlcat/strlcpy and fails (with or without perl)
@tranzystorek-io I can confirm that. I get these errors in build stage `=> opendkim-2.10.3_12: running do_configure ...` (some additional OK lines included):
```
checking bsd/string.h usability... yes
checking bsd/string.h presence... yes
checking for bsd/string.h... yes
checking for strlcat... no
checking for library containing strlcat... no
checking for library containing strlcpy... no
checking for strlcpy... no
checking for library containing strlcat... (cached) no
checking for library containing strlcpy... (cached) no
configure: error: no strlcpy/strlcat found
=> ERROR: opendkim-2.10.3_12: do_configure: '${configure_script} ${configure_args}' exited with 1
=> ERROR: in do_configure() at common/build-style/gnu-configure.sh:8
```
I added `depends="perl"` to the template, but I don't think it actually matters considering that error.
next prev parent reply other threads:[~2022-07-13 16:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 9:19 [ISSUE] " chloris-pale-green
2022-07-13 11:36 ` wael444
2022-07-13 15:14 ` tranzystorek-io
2022-07-13 16:35 ` chloris-pale-green
2022-07-13 16:36 ` chloris-pale-green [this message]
2022-07-13 20:29 ` tranzystorek-io
2022-07-14 2:45 ` sgn
2022-07-14 5:36 ` chloris-pale-green
2022-07-14 14:00 ` [ISSUE] [CLOSED] " sgn
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=20220713163615.UTEJJ8Nc8d2rm0BfU2ZRJlFmtih2L_9w7zrb9mzGFeA@z \
--to=chloris-pale-green@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).