x86_64-pc-linux-gnu-gcc -O2 -pipe -march=native -Wall -Wall -Wextra -I. -Iinclude/ -Wimplicit -D_GNU_SOURCE -D__linux__ -std=gnu11 -Wdeclaration-after-statement -Wformat=2 -Winit-self -Wnested-externs -Wpacked -Wshadow -Wswitch-enum -Wundef -Wwrite-strings -Wno-format-nonliteral -Wstrict-prototypes -Wmissing-prototypes -Wlogical-op -Wstrict-aliasing=3 -Wno-maybe-uninitialized -o ioctls/autofs.o -c ioctls/autofs.c In file included from ioctls/autofs.c:4:0: ioctls/autofs.c:241:8: error: ‘AUTOFS_IOC_EXPIRE_INDIRECT’ undeclared here (not in a function); did you mean ‘AUTOFS_IOC_EXPIRE_CMD’? IOCTL(AUTOFS_IOC_EXPIRE_INDIRECT), ^ include/ioctls.h:53:15: note: in definition of macro ‘IOCTL’ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_libressl_20171229-190412 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.2.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) [3] jython2.7 (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.6.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv dev-util/trinity [ebuild N ] dev-util/trinity-1.7 USE="-examples"
Created attachment 512390 [details] emerge-info.txt
Created attachment 512392 [details] dev-util:trinity-1.7:20171231-200609.log
Created attachment 512394 [details] emerge-history.txt
Created attachment 512396 [details] environment
Created attachment 512398 [details] etc.portage.tbz2
Created attachment 512400 [details] temp.tbz2
1.8 should fix this (and it works in my setup)
got at the unstable amd64 chroot image 17.0-no-multilib-hardened_libressl_20171227-170709 this : ioctls/autofs.c:241:8: error: AUTOFS_IOC_EXPIRE_INDIRECT undeclared here (not in a function)
Created attachment 513306 [details] emerge-info.txt
Created attachment 513308 [details] dev-util:trinity-1.8:20180104-141418.log
Created attachment 513310 [details] emerge-history.txt
Created attachment 513312 [details] environment
Created attachment 513314 [details] etc.portage.tbz2
Created attachment 513316 [details] temp.tbz2
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=13fb235948d859e2c248f68bc92644412a7f8a1b commit 13fb235948d859e2c248f68bc92644412a7f8a1b Author: Pacho Ramos <pacho@gentoo.org> AuthorDate: 2018-10-20 11:57:59 +0000 Commit: Pacho Ramos <pacho@gentoo.org> CommitDate: 2018-10-20 12:16:49 +0000 dev-util/trinity: Apply Fedora/Debian fixes Closes: https://bugs.gentoo.org/642936 Closes: https://bugs.gentoo.org/648962 Signed-off-by: Pacho Ramos <pacho@gentoo.org> Package-Manager: Portage-2.3.51, Repoman-2.3.11 dev-util/trinity/files/trinity-autofs.patch | 53 +++++++++++++++ dev-util/trinity/files/trinity-irda.patch | 47 +++++++++++++ dev-util/trinity/files/trinity-memfd.patch | 79 ++++++++++++++++++++++ dev-util/trinity/files/trinity-net-protocols.patch | 11 +++ dev-util/trinity/trinity-1.8.ebuild | 15 +++- 5 files changed, 202 insertions(+), 3 deletions(-)
