>>> Source configured. >>> Compiling source in /var/tmp/portage/dev-util/tup-0.7.8/work/tup-0.7.8 ... Package fuse was not found in the pkg-config search path. Perhaps you should add the directory containing `fuse.pc' to the PKG_CONFIG_PATH environment variable Package 'fuse', required by 'virtual:world', not found ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_systemd-20200107-091540 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.2.0 * llvm: 9.0.1 Available Python interpreters, in order of preference: [1] python3.7 [2] python3.6 [3] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Wed, 08 Jan 2020 02:05:59 +0000 emerge -qpvO dev-util/tup [ebuild N ] dev-util/tup-0.7.8
Created attachment 602788 [details] emerge-info.txt
Created attachment 602790 [details] dev-util:tup-0.7.8:20200108-023006.log
Created attachment 602792 [details] emerge-history.txt
Created attachment 602794 [details] environment
Created attachment 602796 [details] etc.portage.tbz2
Created attachment 602798 [details] temp.tbz2
Still a problem: * Checking for suitable kernel configuration options... [ ok ] Unable to unshare: EINVAL (for FEATURES="ipc-sandbox network-sandbox pid-sandbox") >>> Unpacking source... >>> Unpacking tup-0.7.8.tar.gz to /var/tmp/portage/dev-util/tup-0.7.8/work >>> Source unpacked in /var/tmp/portage/dev-util/tup-0.7.8/work Unable to unshare: EINVAL (for FEATURES="ipc-sandbox network-sandbox pid-sandbox") >>> Preparing source in /var/tmp/portage/dev-util/tup-0.7.8/work/tup-0.7.8 ... >>> Source prepared. Unable to unshare: EINVAL (for FEATURES="ipc-sandbox network-sandbox pid-sandbox") >>> Configuring source in /var/tmp/portage/dev-util/tup-0.7.8/work/tup-0.7.8 ... >>> Source configured. Unable to unshare: EINVAL (for FEATURES="ipc-sandbox network-sandbox pid-sandbox") >>> Compiling source in /var/tmp/portage/dev-util/tup-0.7.8/work/tup-0.7.8 ... Package fuse was not found in the pkg-config search path. Perhaps you should add the directory containing `fuse.pc' to the PKG_CONFIG_PATH environment variable No package 'fuse' found * ERROR: dev-util/tup-0.7.8::gentoo failed (compile phase): * (no error message) * * Call stack: * ebuild.sh, line 125: Called src_compile * environment, line 1685: Called die * The specific snippet of code: * ./bootstrap-nofuse.sh || die; * * If you need support, post the output of `emerge --info '=dev-util/tup-0.7.8::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-util/tup-0.7.8::gentoo'`. * The complete build log is located at '/var/tmp/portage/dev-util/tup-0.7.8/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-util/tup-0.7.8/temp/environment'. * Working directory: '/var/tmp/portage/dev-util/tup-0.7.8/work/tup-0.7.8' * S: '/var/tmp/portage/dev-util/tup-0.7.8/work/tup-0.7.8' >>> Failed to emerge dev-util/tup-0.7.8, Log file: >>> '/var/tmp/portage/dev-util/tup-0.7.8/temp/build.log' * Messages for package dev-util/tup-0.7.8: * ERROR: dev-util/tup-0.7.8::gentoo failed (compile phase): * (no error message) * * Call stack: * ebuild.sh, line 125: Called src_compile * environment, line 1685: Called die * The specific snippet of code: * ./bootstrap-nofuse.sh || die; * * If you need support, post the output of `emerge --info '=dev-util/tup-0.7.8::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-util/tup-0.7.8::gentoo'`. * The complete build log is located at '/var/tmp/portage/dev-util/tup-0.7.8/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-util/tup-0.7.8/temp/environment'. * Working directory: '/var/tmp/portage/dev-util/tup-0.7.8/work/tup-0.7.8' * S: '/var/tmp/portage/dev-util/tup-0.7.8/work/tup-0.7.8'
I think it can be fixed by adding "sed -i 's/pkg-config fuse/pkg-config fuse3/g'" on these files: - build.sh - Tupfile - Tuprule.tup - tup.1 By default it searches for `fuse.pc` but seems that libfuse provides only `fuse3.pc`. Trying to compile that caused another error though: In file included from /usr/include/fuse3/fuse.h:19:0, from ../src/tup/server/tup_fuse_fs.h:26, from ../src/tup/server/fuse_fs.c:29: /usr/include/fuse3/fuse_common.h:825:4: error: #error only API version 30 or greater is supported # error only API version 30 or greater is supported ^~~~~ ../src/tup/server/fuse_fs.c: In function ‘add_dir_entries’: ../src/tup/server/fuse_fs.c:577:7: error: too few arguments to function ‘filler’ if(filler(buf, de->d_name, &st, 0)) ^~~~~~ ../src/tup/server/fuse_fs.c: In function ‘tup_fs_readdir’: ../src/tup/server/fuse_fs.c:706:7: error: too few arguments to function ‘filler’ if(filler(buf, realname, &st, 0)) ^~~~~~ ../src/tup/server/fuse_fs.c:738:9: error: too few arguments to function ‘filler’ if (filler(buf, realname, &st, 0)) ^~~~~~ ../src/tup/server/fuse_fs.c: At top level: ../src/tup/server/fuse_fs.c:1400:13: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types] .getattr = tup_fs_getattr, ^~~~~~~~~~~~~~ ../src/tup/server/fuse_fs.c:1400:13: note: (near initialization for ‘tup_fs_oper.getattr’) ../src/tup/server/fuse_fs.c:1404:13: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types] .readdir = tup_fs_readdir, ^~~~~~~~~~~~~~ ../src/tup/server/fuse_fs.c:1404:13: note: (near initialization for ‘tup_fs_oper.readdir’) ../src/tup/server/fuse_fs.c:1410:12: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types] .rename = tup_fs_rename, ^~~~~~~~~~~~~ ../src/tup/server/fuse_fs.c:1410:12: note: (near initialization for ‘tup_fs_oper.rename’) ../src/tup/server/fuse_fs.c:1412:11: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types] .chmod = tup_fs_chmod, ^~~~~~~~~~~~ ../src/tup/server/fuse_fs.c:1412:11: note: (near initialization for ‘tup_fs_oper.chmod’) ../src/tup/server/fuse_fs.c:1413:11: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types] .chown = tup_fs_chown, ^~~~~~~~~~~~ ../src/tup/server/fuse_fs.c:1413:11: note: (near initialization for ‘tup_fs_oper.chown’) ../src/tup/server/fuse_fs.c:1414:14: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types] .truncate = tup_fs_truncate, ^~~~~~~~~~~~~~~ ../src/tup/server/fuse_fs.c:1414:14: note: (near initialization for ‘tup_fs_oper.truncate’) ../src/tup/server/fuse_fs.c:1415:13: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types] .utimens = tup_fs_utimens, ^~~~~~~~~~~~~~ ../src/tup/server/fuse_fs.c:1415:13: note: (near initialization for ‘tup_fs_oper.utimens’) ../src/tup/server/fuse_fs.c:1422:10: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types] .init = tup_fs_init, ^~~~~~~~~~~ ../src/tup/server/fuse_fs.c:1422:10: note: (near initialization for ‘tup_fs_oper.init’)
Created attachment 651746 [details, diff] Build fixes for fuse-3.x API I attached a patch (made it on top of the git though), that can be probably repurposed for the release as well.
I created a mainstream bug as well: https://github.com/gittup/tup/issues/402
Dear treecleaner@: I'm still able to reproduce this issue right now. Since it has not been fixed for a long time, I'd suggest to evaluate if it is the case to remove this package from the tree. Thanks
A new version was released since - https://github.com/gittup/tup/releases/tag/v0.7.10 It contains my fix for the FUSE 3.x: - Fixed several 'tup version' issues with bootstrapped or non-git tup - Fixed several issues with clang on Windows - Fixed an error in setting PGID for subprocesses (thanks Samuel!) - Fixed a few issues with generated files that become normal (user-created) files - Fixed an issue with ignored files and Visual Studio (thanks Aaron!) - Improvements to 'tup generate' build scripts (thanks Michael!) - Merged an old pull request for initial NetBSD support (thanks Kamil!), though more work is needed to get this working. - Better support for 32-bit Windows builds (thanks nmlgc!) - Now uses fuse3 by default on Linux, though fuse2 should still work. (Setting CONFIG_TUP_SERVER=fuse in tup.config will use fuse2 when building tup) Thus it should be fixed by version bump.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3a9f0f0469c034feec20c0dd1827f725895f9727 commit 3a9f0f0469c034feec20c0dd1827f725895f9727 Author: Pierre-Nicolas Clauss <pinicarus@protonmail.com> AuthorDate: 2021-07-11 10:29:39 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2021-07-20 10:25:18 +0000 dev-util/tup: upgrade to 0.7.10 Build of 0.7.8 fails since `fuse` pkgconfig is now called `fuse3`. - restrict fuse dependency slot - make sed replacements more resilient - move selection of system sqlite to the prepare phase - remove tests failing in sandbox Package-Manager: Portage-3.0.20, Repoman-3.0.2 Signed-off-by: Pierre-Nicolas Clauss <pinicarus@protonmail.com> Closes: https://bugs.gentoo.org/704990 Closes: https://github.com/gentoo/gentoo/pull/21623 Signed-off-by: Joonas Niilola <juippis@gentoo.org> dev-util/tup/Manifest | 1 + dev-util/tup/tup-0.7.10.ebuild | 102 +++++++++++++++++++++++++++++++++++++++++ 2 files changed, 103 insertions(+)
