From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] A bunch of configure args passed to bind are wrong/useless
Date: Sun, 31 Jan 2021 04:21:49 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28351@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
New issue by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/28351
Description:
### Expected behavior
Running configure for `bind` doesn't show unrecognized options.
### Actual behavior
Running configure for `bind` gets me:
```
Unrecognized options:
--enable-threads, --enable-atomic, --enable-ipv6, --with-randomdev, --with-ecdsa, --with-eddsa, --without-gost, --enable-openssl-hash, --enable-fetchlimit, --enable-sit, --enable-seccomp, --with-geoip
```
I have removed seccomp, because it lead to a misleading build option in package metadata, but haven't touched the others.
### Steps to reproduce the behavior
`./xbps-src configure bind`
next reply other threads:[~2021-01-31 3:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 3:21 ericonr [this message]
2021-03-04 6:12 ` heliocat
2021-03-08 4:08 ` [ISSUE] [CLOSED] " 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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28351@inbox.vuxu.org \
--to=ericonr@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).