X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7BB1B396BC0A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1628253395;
	bh=/WLu8JCzd7qSzYNSDHZz/wcN1QgtacdHUTmC1htfYQQ=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=gFx9tZcrfmiSFGmcozuK06bBPRMvdL9X5LKIi747ikklvqf8s2bn3cKqcxJ7Uyckh
	 BYBRmrEcmOJzLH1OPcAaXI1JwJc9g6vPbzyqw7df2OXwnW74Xc1qtBkv+5MhiAvQKG
	 dDu2kzetzUTCffXJBcbm+smUMdVV+bQwigMw//kc=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 8395C3847808
DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-05.nifty.com 176CZVtQ011053
X-Nifty-SrcIP: [110.4.221.123]
Date: Fri, 6 Aug 2021 21:35:30 +0900
To: cygwin AT cygwin DOT com
Subject: Re: SSHD causes 100% CPU load
Message-Id: <20210806213530.db859e77b415a7eed9e3ccbf@nifty.ne.jp>
In-Reply-To: <20210806203058.8d386cae9a7f085f007cab73@nifty.ne.jp>
References: <145999495 DOT 20210426124252 AT cfos DOT de>
 <1342428656 DOT 20210428072302 AT yandex DOT ru>
 <20210805191242 DOT b29a3904cbc4d082bdc3dd37 AT nifty DOT ne DOT jp>
 <YQv+rEqA8WiWdkVA AT calimero DOT vinschen DOT de>
 <20210806014331 DOT 899fb21f181e664663c328ae AT nifty DOT ne DOT jp>
 <20210806203058 DOT 8d386cae9a7f085f007cab73 AT nifty DOT ne DOT jp>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version: 1.0
X-Spam-Status: No, score=-5.0 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE,
 SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Takashi Yano via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

On Fri, 6 Aug 2021 20:30:58 +0900
Takashi Yano wrote:
> On Fri, 6 Aug 2021 01:43:31 +0900
> Takashi Yano wrote:
> > In order to look into this problem, I tried to build openssh-8.5p1-1
> > from source, however it cause the error in configure stage:
> > 
> > ...
> > checking for pkg-config... (cached) /usr/bin/pkg-config
> > checking if /usr/bin/pkg-config knows about libfido2... no
> > checking for fido_init in -lfido2... no
> > configure: error: no usable libfido2 found
> > *** ERROR: configure failed
> > 
> > despite libfido2-devel had been installed.
> 
> BTW, does anyone have suggestion for this error?

I found the solution by myself. Installing libcbor-devel package
fixes this error.

Thanks.

-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple