from /usr/include/stdlib.h:279, from malloc.c:15: /usr/include/bits/stdint-intn.h:27:19: error: conflicting types for 'int64_t' typedef __int64_t int64_t; ^~~~~~~ In file included from ../include/aal/libaal.h:17:0, ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-gnome-systemd_20171108-200002 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 (fallback) [3] python2.7 (fallback) [4] pypy3 (fallback) [5] pypy (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) * emerge -qpv sys-libs/libaal [ebuild N ] sys-libs/libaal-1.0.6 USE="-static-libs"
Created attachment 504314 [details] emerge-info.txt
Created attachment 504316 [details] emerge-history.txt
Created attachment 504318 [details] environment
Created attachment 504320 [details] etc.portage.tbz2
Created attachment 504322 [details] logs.tbz2
Created attachment 504324 [details] sys-libs:libaal-1.0.6:20171114-232019.log
Created attachment 504326 [details] temp.tbz2
this problem occurs in me
Created attachment 505868 [details] emerge info
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b79aa3db1cca97db331e6e058a1c751591f29759 commit b79aa3db1cca97db331e6e058a1c751591f29759 Author: Thomas Deutschmann <whissi@gentoo.org> AuthorDate: 2017-11-27 23:07:20 +0000 Commit: Thomas Deutschmann <whissi@gentoo.org> CommitDate: 2017-11-27 23:07:42 +0000 sys-libs/libaal: Fix build against glibc-2.6 Closes: https://bugs.gentoo.org/637610 Package-Manager: Portage-2.3.16, Repoman-2.3.6 sys-libs/libaal/Manifest | 2 +- sys-libs/libaal/files/libaal-1.0.6-glibc26.patch | 89 ++++++++++++++++++++++++ sys-libs/libaal/libaal-1.0.6.ebuild | 5 +- sys-libs/libaal/libaal-1.0.7-r1.ebuild | 42 +++++++++++ 4 files changed, 135 insertions(+), 3 deletions(-)
Well, the main issue is caused by glib-2.6 incompatibility is already fixed in libaal-1.0.7. However, stable reiser4progs ebuild limits libaal version for unknown reason (bug 102458), so I added a patch. Newer >=reiser4progs-1.2.0 will support >=libaal-1.0.6.
