| Summary: | dev-libs/libgcrypt-1.9.4 : .../work/libgcrypt-1.8.5/random/jitterentropy-base.c:60:4: error: #error "The CPU Jitter random number generator must not be compiled with optimizations. See documentation. Use the compiler switch -O0 for compiling jitterentr... | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Xeha <Xeha> |
| Component: | Current packages | Assignee: | Mikle Kolyada (RETIRED) <zlogene> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | alexander, base-system, conikost, hjckr, jstein, lssndrbarbieri, me, sam, the_bishop, Xeha |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=793197 https://bugs.gentoo.org/show_bug.cgi?id=902765 |
||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 408963 | ||
| Attachments: |
build log
emerge --info |
||
|
Description
Xeha
2020-01-29 22:17:00 UTC
Created attachment 608568 [details]
build log
Created attachment 608570 [details]
emerge --info
i did just hit this on x86_64 with building 32abi of libgcrypt. How about 1.9.2? Same with 1.9.2 tinderbox has reproduced this issue with version 1.9.4 - Updating summary. same here, dev-libs/libgcrypt does not build. okay, so the build flag "o-flag-munging" does fix this problem. dev-libs/libgcrypt-1.10.1 has this problem too. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b4213c9598cf5ab09d9323dd254a9ea6b439dfcd commit b4213c9598cf5ab09d9323dd254a9ea6b439dfcd Author: Sam James <sam@gentoo.org> AuthorDate: 2022-04-15 00:51:33 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-04-15 00:51:33 +0000 dev-libs/libgcrypt: rename o-flag-munging -> custom-cflags More accurately represents what it does & requires a conscious action to turn _on_ the flag which may break the build. Closes: https://bugs.gentoo.org/707330 Signed-off-by: Sam James <sam@gentoo.org> dev-libs/libgcrypt/libgcrypt-1.10.1.ebuild | 4 ++-- dev-libs/libgcrypt/libgcrypt-1.9.4-r1.ebuild | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=eadc4f710b6783d509cb6d9b2b5b475069e16391 commit eadc4f710b6783d509cb6d9b2b5b475069e16391 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2022-04-16 19:32:25 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2022-04-16 19:34:26 +0000 dev-libs/libgcrypt: always enable O-flag-munging Exposing this as a USE flag is mostly pointless, and results in silly bug reports from users who disable it by accident. Users can disable it using EXTRA_ECONF if so desired. Bug: https://bugs.gentoo.org/629410 Bug: https://bugs.gentoo.org/707330 Closes: https://bugs.gentoo.org/838472 Signed-off-by: Mike Gilbert <floppym@gentoo.org> dev-libs/libgcrypt/libgcrypt-1.10.1.ebuild | 3 +-- dev-libs/libgcrypt/libgcrypt-1.8.8.ebuild | 5 ++--- dev-libs/libgcrypt/libgcrypt-1.8.9.ebuild | 3 +-- dev-libs/libgcrypt/libgcrypt-1.9.4-r1.ebuild | 3 +-- dev-libs/libgcrypt/metadata.xml | 1 - 5 files changed, 5 insertions(+), 10 deletions(-) Note, the flag munging does *not* account for -Oz which is supported with clang and gcc >= 12. given the comment by Steven Newbury above is this actually resolved? (In reply to Jeff Cliff from comment #13) > given the comment by Steven Newbury above is this actually resolved? It's a separate issue which would ideally have a new bug, as it's something we need to handle upstream. |
