[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#42185: closed (An issue with bcrypt.h [MSYS2/MinGW64?])

From: GNU bug Tracking System
Subject: bug#42185: closed (An issue with bcrypt.h [MSYS2/MinGW64?])
Date: Thu, 13 Aug 2020 11:05:03 +0000

Your message dated Thu, 13 Aug 2020 04:04:29 -0700
with message-id 
and subject line Re: bug#42185: An issue with bcrypt.h [MSYS2/MinGW64?]
has caused the debbugs.gnu.org bug report #42185,
regarding An issue with bcrypt.h [MSYS2/MinGW64?]
to be marked as done.

(If you believe you have received this mail in error, please contact

42185: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=42185
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: An issue with bcrypt.h [MSYS2/MinGW64?] Date: Sat, 4 Jul 2020 11:09:24 +0200 (CEST)
This morning building the last master (32b3856f850e1) I get these warning while 

checking whether getloadavg is declared... no
checking bcrypt.h usability... no
checking bcrypt.h presence... yes
configure: WARNING: bcrypt.h: present but cannot be compiled
configure: WARNING: bcrypt.h:     check for missing prerequisite headers?
configure: WARNING: bcrypt.h: see the Autoconf documentation
configure: WARNING: bcrypt.h:     section "Present But Cannot Be Compiled"
configure: WARNING: bcrypt.h: proceeding with the compiler's result
configure: WARNING:     ## ------------------------------------ ##
configure: WARNING:     ## Report this to bug-gnu-emacs@gnu.org ##
configure: WARNING:     ## ------------------------------------ ##
checking for bcrypt.h... no
checking whether the bcrypt library is guaranteed to be present... (cached) no
checking whether gettimeofday clobbers localtime buffer... no
checking for gettimeofday with POSIX signature... yes

The above occurred with the Windows build (MSYS2/MinGW64).

--- End Message ---
--- Begin Message --- Subject: Re: bug#42185: An issue with bcrypt.h [MSYS2/MinGW64?] Date: Thu, 13 Aug 2020 04:04:29 -0700
Angelo Graziosi <angelo.g0@libero.it> writes:

> In the last build the warning is gone.. please close.

Great, I'm closing this bug report with this message.

Best regards,
Stefan Kangas

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]