Bug 687434 – app-portage/portage-utils-0.80_pre20190530 configure: error: --enable-qmanifest was given, but test for blake2b failed

• Status: RESOLVED FIXED
• Product: Portage Development

[Description email200202 2019-06-05 12:02:16 UTC]

Created attachment 578844 [details]
build.log

checking blake2.h usability... yes
checking blake2.h presence... yes
checking for blake2.h... yes
checking for blake2b_update in -lb2... no
configure: error: in `/var/tmp/portage/app-portage/portage-utils-0.80_pre20190530/work/portage-utils-0.80_pre20190530':
configure: error: --enable-qmanifest was given, but test for blake2b failed
See `config.log' for more details

[Comment 1 email200202 2019-06-05 12:05:57 UTC]

Created attachment 578846 [details]
emerge -pqv '=app-portage/portage-utils-0.80_pre20190530::gentoo'

[Comment 2 email200202 2019-06-05 12:07:21 UTC]

Created attachment 578848 [details]
emerge --info '=app-portage/portage-utils-0.80_pre20190530::gentoo'

[Comment 3 Jeroen Roovers (RETIRED) 2019-06-05 15:23:44 UTC]

(In reply to email200202 from comment #0)
> See `config.log' for more details

Please attach that file.

[Comment 4 Fabian Groffen 2019-06-05 15:34:59 UTC]

long story short, you need to resync your tree and re-emerge libb2, if that doesn't fix, we need the config.log file

[Comment 5 email200202 2019-06-06 09:25:42 UTC]

When I did update yesterday, libb2 came as new dependency

[ebuild  N     ] app-crypt/libb2-0.98.1::gentoo  USE="openmp -native-cflags -static" 275 KiB
[ebuild     U  ] app-portage/portage-utils-0.80_pre20190530::gentoo [0.74-r1::gentoo] USE="nls openmp%* qmanifest%* -static" 1,717 KiB

I will try again today.

[Comment 6 email200202 2019-06-06 10:14:52 UTC]

After sync/update today, the same versions came up:

[ebuild  N     ] app-crypt/libb2-0.98.1::gentoo  USE="openmp -native-cflags -static" 275 KiB
[ebuild     U  ] app-portage/portage-utils-0.80_pre20190530::gentoo [0.74-r1::gentoo] USE="nls openmp%* qmanifest%* -static" 1,717 KiB

But this time, it passed the configuration stage with no problem:

checking blake2.h usability... yes
checking blake2.h presence... yes
checking for blake2.h... yes
checking for blake2b_update in -lb2... yes   <<<<<< was 'no' yesterday  

and the emerge was successful.

The versions are the same and the other packages in the sync/update seem to be not related to these packages! 

Anyway, the bug can be closed.

[Comment 7 Fabian Groffen 2019-06-06 10:51:34 UTC]

yes, there was a small window in which you synced, where a few commits where made

Thanks for the feedback!

[Comment 8 email200202 2019-06-06 11:22:59 UTC]

I did more research. I had a copy of yesterday portage.

When I compared libb2-0.98.1.ebuild between yesterday and today, I got this:

# diff libb2-0.98.1.ebuild /usr/portage/app-crypt/libb2/libb2-0.98.1.ebuild
37a38,39
>       # https://github.com/BLAKE2/libb2/pull/28
>       echo 'libb2_la_LDFLAGS = -no-undefined' >> src/Makefile.am || die
48c50
< src_compile() {
---
> do_make() {
50c52,61
<       emake $(use native-cflags && echo no)CFLAGS="${CFLAGS}"
---
>       local openmp=$(use openmp && echo -fopenmp)
>       emake $(use native-cflags && echo no)CFLAGS="${CFLAGS} ${openmp}" "$@"
> }
> 
> src_compile() {
>       do_make
> }
> 
> src_test() {
>       do_make check

The file changes without changing the version!