Summary: | app-crypt/gcr - In file included from gck/gck-mock.c:22: /usr/include/glib-2.0/glib/gtypes.h: In function ‘_GLIB_CHECKED_ADD_U64’: /usr/include/glib-2.0/glib/gmacros.h:277:53: error: size of array ‘_GStaticAssertCompileTimeAssertion_0’ is negative | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | tt_1 <herrtimson> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
compressed build log
emerge --info from cross-emerge |
Created attachment 569390 [details]
emerge --info from cross-emerge
a suitable patch for gcr-3.28.1 can be cherry picked from: https://gitlab.gnome.org/GNOME/gcr/commit/1479bda8d36ed7b167a003e016b426ae615c6f33?merge_request_iid=20 need to run eautoconf in src_configure, obviously. fixed by bump to gcr-3.34.0 in: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8979a0fad85af59f8d1f9a3a405c05ff47b25707 |
Created attachment 569388 [details] compressed build log I think this happens because of using hosts pkg-config, which leads to pulling the hosts headers into the cross-compile. Is there a way to fix this within the build? cross-compiling without portage works, as long as export PKG_CONFIG=/usr/bin/armv7a-unknown-linux-gnueabihf-pkg-config is set before ./configure