From: Alan Mackenzie <acm@muc.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Please help me understand this emerge error message.
Date: Sat, 12 Aug 2023 10:14:04 +0000 [thread overview]
Message-ID: <ZNdbbKr3MZCqeBib@ACM> (raw)
In-Reply-To: <4c4a3007-04df-9a23-0634-330cdbc99836@gmail.com>
On Fri, Aug 11, 2023 at 13:52:25 -0500, Dale wrote:
> Alan Mackenzie wrote:
> > Hello, Gentoo.
> > For the past couple of days, after $ emerge --sync, I've tried
> > $ emerge -auND @world
> > .. It has come back very quickly with the error message:
> > #########################################################################
> > !!! The ebuild selected to satisfy ">=net-misc/curl-7.21.5[ssl]" has unmet requirements.
> > - net-misc/curl-8.1.2::gentoo USE="adns ftp gnutls http2 imap pop3 progress-meter smtp ssl tftp -alt-svc -brotli -gopher -hsts -idn -kerberos -ldap -mbedtls (-nghttp3) -nss -openssl -rtmp (-rustls) -samba -ssh (-sslv3) -static-libs -telnet
> > -test -verify-sig -websockets -zstd" ABI_X86="(64) -32 (-x32)" CURL_SSL="openssl -gnutls -mbedtls -nss (-rustls)"
> > The following REQUIRED_USE flag constraints are unsatisfied:
> > curl_ssl_openssl? ( openssl )
> > The above constraints are a subset of the following complete expression:
> > ssl? ( exactly-one-of ( curl_ssl_gnutls curl_ssl_mbedtls curl_ssl_nss curl_ssl_openssl curl_ssl_rustls ) ) curl_ssl_gnutls? ( gnutls ) curl_ssl_mbedtls? ( mbedtls ) curl_ssl_nss? ( nss ) curl_ssl_openssl? ( openssl ) curl_ssl_rustls? (
> > rustls )
> > #########################################################################
> > .. I don't understand what is meant by "curl_ssl_openssl? ( openssl )" in
> > the above message. I assume it's talking about some USE flag, but which?
> > openssl? curl_ssl_openssl? As a matter of interest, I have
> > =dev-libs/openssl-3.0.9-r2 installed.
> > Please help me understand what's happening.
> > Thanks for the help!
> I think I got that a while back. This is what I have for my USE flags
> for that package.
[ .... ]
> I think it wants you to enable openssl or one of the other USE flag
> options. Since I seem to recall having openssl installed already, I
> just picked it. I'd try enabling that and see if the error goes away.
That was the problem. Although I had openssl installed, I hadn't set the
USE flag openssl for curl. When I did that, the problem went away. :-)
> Hope that helps.
It did. Thanks!
> Dale
> :-) :-)
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2023-08-12 10:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 18:46 [gentoo-user] Please help me understand this emerge error message Alan Mackenzie
2023-08-11 18:52 ` Dale
2023-08-11 18:55 ` David Rosenbaum
2023-08-12 10:14 ` Alan Mackenzie [this message]
2023-08-11 19:45 ` Arsen Arsenović
2023-08-11 19:57 ` Kusoneko
2023-08-11 20:24 ` Dale
2023-08-12 10:19 ` Alan Mackenzie
2023-08-12 11:49 ` [gentoo-user] " Nuno Silva
2023-08-12 1:15 ` [gentoo-user] " Paul Colquhoun
2023-08-12 10:22 ` Alan Mackenzie
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=ZNdbbKr3MZCqeBib@ACM \
--to=acm@muc.de \
--cc=gentoo-user@lists.gentoo.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