| Summary: | net-libs/gnome-online-accounts-3.40.0: /usr/include/gcr-3/gcr/gcr.h:23:2: error: #error "This API has not yet reached stability." | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Frederik Pfautsch <bugs> |
| Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | jstein, sam |
| Priority: | Normal | Keywords: | PATCH |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/merge_requests/76 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 526268 | ||
| Attachments: |
emerge --info
build.log nonbash.patch |
||
Created attachment 759493 [details]
build.log
Please add the package category to the bug summary. checking for GCR... yes ./configure: 17053: test: yes: unexpected operator ./configure: 17060: test: yes: unexpected operator checking for krb5-config... (cached) /usr/bin/krb5-config checking for GCR... yes ./configure: 17451: test: yes: unexpected operator ./configure: 17458: test: yes: unexpected operator checking for timerfd support... yes checking for timerfd cancel-on-set support... yes Looks related to nonbash /bin/sh. Created attachment 759525 [details, diff]
nonbash.patch
You will need to modify the ebuild and set GNOME2_EAUTORECONF=yes at the top of the ebuild about inherit and apply this patch.
Oh, that makes sense. I wondered why the problem appeared now and not at the initial upgrade and didn't think to check the configure log. Thanks for the patch and the merge request! Both options (setting bash or using the patch) work for me. (In reply to Frederik Pfautsch from comment #5) > Oh, that makes sense. I wondered why the problem appeared now and not at the > initial upgrade and didn't think to check the configure log. > > Thanks for the patch and the merge request! Both options (setting bash or > using the patch) work for me. Excellent! Thanks for the quick feedback :) I think downstream we should just CONFIG_SHELL="${BASH}" meanwhile instead of incurring a eautoreconf
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=23749c7cadeb2e9b189fd70f3edb69459d548738 commit 23749c7cadeb2e9b189fd70f3edb69459d548738 Author: Sam James <sam@gentoo.org> AuthorDate: 2021-12-19 21:15:20 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-12-19 21:16:18 +0000 net-libs/gnome-online-accounts: use Bash for configure for now Fix compile using e.g. dash as /bin/sh (instead of bash as /bin/sh). Patch submitted upstream. Closes: https://bugs.gentoo.org/829494 Signed-off-by: Sam James <sam@gentoo.org> net-libs/gnome-online-accounts/gnome-online-accounts-3.40.0.ebuild | 5 ++++- net-libs/gnome-online-accounts/gnome-online-accounts-3.40.1.ebuild | 5 ++++- 2 files changed, 8 insertions(+), 2 deletions(-) |
Created attachment 759492 [details] emerge --info Gnome-online-accounts fails to build after complete rebuild of the system with the following error message from (included from app-crypt/gcr-3.40.0): In file included from goaidentityservice.c:29: /usr/include/gcr-3/gcr/gcr.h:23:2: error: #error "This API has not yet reached stability." 23 | #error "This API has not yet reached stability." | ^~~~~