View previous topic :: View next topic |
Author |
Message |
RobinEggBlue n00b
Joined: 03 Aug 2021 Posts: 8 Location: Chicago
|
Posted: Tue Aug 03, 2021 7:10 pm Post subject: [SOLVED]sys-fs/fuse-2.9.9_rc1 failing to compile |
|
|
Gurus,
I'm having a little bit of trouble installing flatpak, as sys-fs/fuse-2.9.9_rc1 is a dependency that refuses to compile.
I had been running Steam on a multilib ~amd64 configuration, but recently switched profiles to #12 amd64/17.1/no-multilib. As a result, I have no choice but to chroot (boo) or run flatpak(oh well).
If it makes any difference, I had briefly flirted with running the 9999 releases of the gcc toolchain, only to find that I was running into all kinds of issues. I've dialed back what I could, but gblic won't take a single step backwards.I admire the boldness but it leads me to suspect that it is tripping up my fuse emerge. The rest of the toolchain has compiled itself a couple of times over since. Fuse is installed as a module and in the boot runlevel.
I have my make.conf configured such that I comment out CFLAGS that interfere with compilation rather than run the LTO-Overlay.
Quote: | CFLAGS = "-march=znver2 -O3 -pipe"
CFLAGS = "${CFLAGS} -fgraphite-identity -floop-nest-optimize -floop-parallelize-all"
CFLAGS = "${CFLAGS} -flto-compression-level=19 -flto=auto -fuse-linker-plugin"
# Graphite flags
CFLAGS="${CFLAGS} -fgraphite-identity -floop-interchange -ftree-loop-distribution -floop-strip-mine -floop-block"
# CXX flags
CXXFLAGS = "${CFLAGS}"
# parallel compiling
MAKEOPTS = "--jobs=12 --load-average=12"
NINJAFLAGS = "-j12 -l12"
PARALLELMFLAGS = "-j12 -l12" |
Even after I comment out everything but Quote: | march=znver2 -O3 -pipe | and run a single job I have no luck.
I hope the information above was relevant, if there's anything else I can provide please let me know.
Thank you in advance.
Below are the emerge logs for:
[ebuild N ] sys-fs/fuse-2.9.9-r1 USE="-examples -static-libs"
Quote: | Portage 3.0.20 (python 3.9.6-final-0, default/linux/amd64/17.1/no-multilib, gcc-11.2.0, glibc-9999, 5.13.7-gentooono x86_64)
=================================================================
System Settings
=================================================================
System uname: Linux-5.13.7-gentooono-x86_64-AMD_Ryzen_5_3600_6-Core_Processor-with-glibc2.34.9000
KiB Mem: 16328928 total, 5377896 free
KiB Swap: 15625212 total, 15322620 free
Timestamp of repository gentoo: Tue, 03 Aug 2021 18:21:54 +0000
Head commit of repository gentoo: 7a13eb83be88b0c9abf377abda4bea8de87c49aa
Timestamp of repository SarahMiaOverlay: Sun, 18 Jul 2021 12:52:33 +0000
Head commit of repository SarahMiaOverlay: 2bb4cbc27c93b179aeb92e7cd9e8441b5ee117cc
Timestamp of repository jorgicio: Fri, 23 Jul 2021 05:52:31 +0000
Head commit of repository jorgicio: 858b97a63cffd8ada337fd2df47814b6f8f4dcaa
sh bash 5.1_p8
ld GNU ld (Gentoo 2.36.1 p5) 2.36.1
ccache version 4.3 [enabled]
app-shells/bash: 5.1_p8::gentoo
dev-lang/perl: 5.34.0-r1::gentoo
dev-lang/python: 3.9.6-r1::lto-overlay, 3.10.0_rc1::gentoo
dev-lang/rust: 1.53.0::gentoo
dev-util/ccache: 4.3-r3::gentoo
dev-util/cmake: 3.21.1::gentoo
dev-util/pkgconfig: 0.29.2::gentoo
sys-apps/baselayout: 2.7-r3::gentoo
sys-apps/openrc: 0.43.3::gentoo
sys-apps/sandbox: 2.24::gentoo
sys-devel/autoconf: 2.13-r1::gentoo, 2.71-r1::gentoo
sys-devel/automake: 1.16.4::gentoo
sys-devel/binutils: 2.36.1-r2::gentoo
sys-devel/gcc: 11.2.0::gentoo
sys-devel/gcc-config: 2.4::gentoo
sys-devel/libtool: 2.4.6-r6::gentoo
sys-devel/make: 4.3::gentoo
sys-kernel/linux-headers: 5.13::gentoo (virtual/os-headers)
sys-libs/glibc: 9999::gentoo
Repositories:
gentoo
location: /var/db/repos/gentoo
sync-type: git
sync-uri: https://github.com/gentoo-mirror/gentoo.git
priority: -1000
SarahMiaOverlay
location: /var/db/repos/SarahMiaOverlay
sync-type: git
sync-uri: https://github.com/gentoo-mirror/SarahMiaOverlay.git
masters: gentoo
jorgicio
location: /var/db/repos/jorgicio
sync-type: git
sync-uri: https://github.com/gentoo-mirror/jorgicio.git
masters: gentoo
ACCEPT_KEYWORDS="amd64 ~amd64"
ACCEPT_LICENSE="*"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=znver2 -O3 -pipe -fgraphite-identity -floop-nest-optimize -floop-parallelize-all -flto-compression-level=19 -flto=auto -fuse-linker-plugin -fgraphite-identity -floop-interchange -ftree-loop-distribution -floop-strip-mine -floop-block"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-march=znver2 -O3 -pipe -fgraphite-identity -floop-nest-optimize -floop-parallelize-all -flto-compression-level=19 -flto=auto -fuse-linker-plugin -fgraphite-identity -floop-interchange -ftree-loop-distribution -floop-strip-mine -floop-block"
DISTDIR="/var/cache/distfiles"
ENV_UNSET="CARGO_HOME DBUS_SESSION_BUS_ADDRESS DISPLAY GOBIN GOPATH PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs ccache config-protect-if-modified distlocks ebuild-locks fixlafiles ipc-sandbox merge-sync multilib-strict network-sandbox news parallel-fetch pid-sandbox preserve-libs protect-owned qa-unresolved-soname-deps sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="http://distfiles.gentoo.org"
LANG="C.UTF8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j12"
PKGDIR="/var/cache/binpkgs"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git"
PORTAGE_TMPDIR="/var/tmp"
USE="GRUB_PLATFORMS=efi-64 X acl alsa amd64 bluetooth branding bzip2 cli crypt dbus default-compiler-rt default-libunwind dri elogind experimental gdbm gif gnome graphite gtk iconv icu jpeg jumbo-build lcms libglvnd libmpv libtirpc lm-sensors lto lz4 lzma mp3 nptl opengl openmp pam pcre pgo png pulseaudio readline seccomp spell split-usr ssl svg tcpd tiff truetype udev unicode vala vorbis vorbisx264 x264 x265 xattr xml xvid zlib zstd" ABI_X86="64" ADA_TARGET="gnat_2018" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="karbon sheets words" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt rdrand sha sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock greis isync itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 timing tsip tripmate tnt ublox ubx" INPUT_DEVICES="libinput" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" LLVM_TARGETS="NVPTX X86" LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php7-3 php7-4" POSTGRES_TARGETS="postgres12 postgres13" PYTHON_SINGLE_TARGET="python3_9" PYTHON_TARGETS="python3_9 python3_10" RUBY_TARGETS="ruby27 ruby30" USERLAND="GNU" VIDEO_CARDS="nvidia" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq proto steal rawnat logmark ipmark dhcpmac delude chaos account"
Unset: CC, CPPFLAGS, CTARGET, CXX, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, LINGUAS, PORTAGE_BINHOST, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, RUSTFLAGS |
And this is how things look when the merge goes pear-shaped:
Quote: | libtool: link: x86_64-pc-linux-gnu-gcc -march=znver2 -O3 -pipe -fgraphite-identity -floop-nest-optimize -floop-parallelize-all -fuse-linker-plugin -fgraphite-identity -floop-interchange -ftree-loop-distribution -floop-strip-mine -floop-block -Wl,-O1 -o fusermount fusermount-fusermount.o fusermount-mount_util.o -Wl,--as-needed
ulockmgr_server.c:127:12: error: conflicting types for 'closefrom'; have 'int(int)'
127 | static int closefrom(int minfd)
| ^~~~~~~~~
In file included from ulockmgr_server.c:14:
/usr/include/unistd.h:363:13: note: previous declaration of 'closefrom' with type 'void(int)'
363 | extern void closefrom (int __lowfd) __THROW;
| ^~~~~~~~~
ulockmgr_server.c: In function 'main':
ulockmgr_server.c:371:16: warning: ignoring return value of 'chdir' declared with attribute 'warn_unused_result' [-Wunused-result]
371 | (void) chdir("/");
| ^~~~~~~~~~
make[2]: *** [Makefile:504: ulockmgr_server-ulockmgr_server.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/var/tmp/portage/sys-fs/fuse-2.9.9-r1/work/fuse-2.9.9/util'
make[1]: *** [Makefile:335: all] Error 2
make[1]: Leaving directory '/var/tmp/portage/sys-fs/fuse-2.9.9-r1/work/fuse-2.9.9/util'
make: *** [Makefile:450: all-recursive] Error 1
* ERROR: sys-fs/fuse-2.9.9-r1::gentoo failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=sys-fs/fuse-2.9.9-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-fs/fuse-2.9.9-r1::gentoo'`.
* The complete build log is located at '/var/tmp/portage/sys-fs/fuse-2.9.9-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-fs/fuse-2.9.9-r1/temp/environment'.
* Working directory: '/var/tmp/portage/sys-fs/fuse-2.9.9-r1/work/fuse-2.9.9'
* S: '/var/tmp/portage/sys-fs/fuse-2.9.9-r1/work/fuse-2.9.9'
>>> Failed to emerge sys-fs/fuse-2.9.9-r1, Log file:
>>> '/var/tmp/portage/sys-fs/fuse-2.9.9-r1/temp/build.log'
* Messages for package sys-fs/fuse-2.9.9-r1:
* ERROR: sys-fs/fuse-2.9.9-r1::gentoo failed (compile phase):
* emake failed |
Last edited by RobinEggBlue on Tue Aug 03, 2021 11:00 pm; edited 1 time in total |
|
Back to top |
|
|
fedeliallalinea Administrator
Joined: 08 Mar 2003 Posts: 30894 Location: here
|
Posted: Tue Aug 03, 2021 7:37 pm Post subject: |
|
|
Welcome to gentoo forum!
See bug #803923 _________________ Questions are guaranteed in life; Answers aren't. |
|
Back to top |
|
|
sam_ Developer
Joined: 14 Aug 2020 Posts: 1678
|
Posted: Tue Aug 03, 2021 8:55 pm Post subject: Re: sys-fs/fuse-2.9.9_rc1 failing to compile |
|
|
RobinEggBlue wrote: | Gurus,
I'm having a little bit of trouble installing flatpak, as sys-fs/fuse-2.9.9_rc1 is a dependency that refuses to compile.
I had been running Steam on a multilib ~amd64 configuration, but recently switched profiles to #12 amd64/17.1/no-multilib. As a result, I have no choice but to chroot (boo) or run flatpak(oh well).
If it makes any difference, I had briefly flirted with running the 9999 releases of the gcc toolchain, only to find that I was running into all kinds of issues. I've dialed back what I could, but gblic won't take a single step backwards.I admire the boldness but it leads me to suspect that it is tripping up my fuse emerge. The rest of the toolchain has compiled itself a couple of times over since. Fuse is installed as a module and in the boot runlevel.
I have my make.conf configured such that I comment out CFLAGS that interfere with compilation rather than run the LTO-Overlay.
|
1. It's not _rc1, it's -r1
2. This line:
RobinEggBlue wrote: |
sys-libs/glibc: 9999::gentoo
|
... is extremely scary. You SHOULD be able to at least step back to glibc-2.34, but you may need to set a scary variable temporarily. Please show us the output when you try to emerge glibc-2.34. Please remove any package.accept_keywords entry involving 9999/**.
You'll need something like (ONLY for your case, nobody else reading this should do it) this in /etc/portage/package.accept_keywords:
Code: |
<sys-libs/glibc-2.35 **
|
fedeliallalinea wrote: | Welcome to gentoo forum!
See bug #803923 |
Yep, I'll backport the patch soon. Thank you! |
|
Back to top |
|
|
RobinEggBlue n00b
Joined: 03 Aug 2021 Posts: 8 Location: Chicago
|
Posted: Tue Aug 03, 2021 9:05 pm Post subject: |
|
|
fedeliallalinea,
Thank you for your prompt reply and warm welcome.
I've never applied a patch before, pretty certain the format I'm using is incorrect but I can't google my way to a solution. (Doesn't "diff" turn up a coupla times?...)
Following the guide at https://wiki.gentoo.org/wiki//etc/portage/patches as best I could, I created two files by copying the content at https://github.com/libfuse/libfuse/pull/619/files
into /etc/portage/patches/sys-fs/fuse:
grateful.patch:
Quote: | @@ -55,6 +55,7 @@ fi
AC_CHECK_FUNCS([fork setxattr fdatasync splice vmsplice utimensat])
AC_CHECK_FUNCS([posix_fallocate])
AC_CHECK_FUNCS([closefrom])
AC_CHECK_MEMBERS([struct stat.st_atim])
AC_CHECK_MEMBERS([struct stat.st_atimespec])
|
thankful.patch:
Quote: |
@@ -22,6 +22,10 @@
#include <sys/socket.h>
#include <sys/wait.h>
#ifdef HAVE_CONFIG_H
#include "config.h"
#endif
struct message {
unsigned intr : 1;
unsigned nofd : 1;
@@ -124,6 +128,7 @@ static int receive_message(int sock, void *buf, size_t buflen, int *fdp,
return res;
}
#if !defined(HAVE_CLOSEFROM)
static int closefrom(int minfd)
{
DIR *dir = opendir("/proc/self/fd");
@@ -141,6 +146,7 @@ static int closefrom(int minfd)
}
return 0;
}
#endif
static void send_reply(int cfd, struct message *msg)
{
|
However, the output of ebuild fuse-2.9.9-r1.ebuild clean prepare:
Quote: |
>>> Preparing source in /var/tmp/portage/sys-fs/fuse-2.9.9-r1/work/fuse-2.9.9 ...
* Running elibtoolize in: fuse-2.9.9/
* Applying portage/1.2.0 patch ...
* Applying sed/1.5.6 patch ...
* Applying as-needed/2.4.3 patch ...
* Applying ppc64le/2.4.4 patch ...
* Applying fuse-2.9.3-kernel-types.patch ... [ ok ]
>>> Source prepared.
|
User patches are not pulled in, as you can see. Can you tell me what's wrong with my setup?
Thank you! |
|
Back to top |
|
|
sam_ Developer
Joined: 14 Aug 2020 Posts: 1678
|
Posted: Tue Aug 03, 2021 9:19 pm Post subject: |
|
|
RobinEggBlue wrote: | fedeliallalinea,
Thank you for your prompt reply and warm welcome.
I've never applied a patch before, pretty certain the format I'm using is incorrect but I can't google my way to a solution. (Doesn't "diff" turn up a coupla times?...)
|
You can actually get the full patch by pending ".patch" to the URL, but unfortunately, we need to make an ebuild change (eautoreconf) to make it apply, and then I need to rebase my patch a bit. If you wait a little bit, I can try get to this tonight?
So, all you need to do, is follow the glibc downgrade instructions I mentioned and also be patient. I'll update this post and the bug when I've fixed it, then emerge --sync, and try again? |
|
Back to top |
|
|
RobinEggBlue n00b
Joined: 03 Aug 2021 Posts: 8 Location: Chicago
|
Posted: Tue Aug 03, 2021 9:22 pm Post subject: Re: sys-fs/fuse-2.9.9_rc1 failing to compile |
|
|
sam,
sam_ wrote: |
2. This line: ... is extremely scary.......... nobody else reading this should do it
|
I have already removed all 9999 related package.accept_keywords entries, and inserted your recommended fix.
Emerging glibc-2.34 still produces the dreaded
Quote: | Checking general environment sanity.
* Sanity check to keep you from breaking your system:
* Downgrading glibc is not supported and a sure way to destruction.
* ERROR: sys-libs/glibc-2.34::gentoo failed (pretend phase):
* Aborting to save your system.
*
* Call stack:
* ebuild.sh, line 127: Called pkg_pretend
* glibc-2.34.ebuild, line 726: Called sanity_prechecks
* glibc-2.34.ebuild, line 627: Called die
* The specific snippet of code:
* [[ ${I_ALLOW_TO_BREAK_MY_SYSTEM} = yes ]] || die "Aborting to save your system." |
At this point, is it better to pull a I_KNOW_WHAT_I_AM_DOING(when obviously I do not), or just wear a mask until glibc naturally evolves beyond 2.35?
Thanks for your input and backporting! |
|
Back to top |
|
|
sam_ Developer
Joined: 14 Aug 2020 Posts: 1678
|
Posted: Tue Aug 03, 2021 9:24 pm Post subject: Re: sys-fs/fuse-2.9.9_rc1 failing to compile |
|
|
RobinEggBlue wrote: | sam,
sam_ wrote: |
2. This line: ... is extremely scary.......... nobody else reading this should do it
|
|
That's how I felt reading it!
It's OK, we'll sort you out.
RobinEggBlue wrote: |
I have already removed all 9999 related package.accept entries, and inserted your recommended fix.
Emerging glibc-2.34 still produces the dreaded
Quote: | Checking general environment sanity.
* Sanity check to keep you from breaking your system:
* Downgrading glibc is not supported and a sure way to destruction.
* ERROR: sys-libs/glibc-2.34::gentoo failed (pretend phase):
* Aborting to save your system.
*
* Call stack:
* ebuild.sh, line 127: Called pkg_pretend
* glibc-2.34.ebuild, line 726: Called sanity_prechecks
* glibc-2.34.ebuild, line 627: Called die
* The specific snippet of code:
* [[ ${I_ALLOW_TO_BREAK_MY_SYSTEM} = yes ]] || die "Aborting to save your system." |
At this point, is it better to pull a I_KNOW_WHAT_I_AM_DOING(when obviously I do not), or just wear a mask until glibc naturally evolves beyond 2.35?
Thanks for your input and backporting! |
Hey!
No problem. I'm glad my patch is useful
As a one off, could you do:
Code: |
I_KNOW_WHAT_I_AM_DOING=1 emerge -pv1 glibc
|
If it shows it'll downgrade to 2.34, let it run (drop -p). If anything looks wrong or you want to double check, just come back here and show me first and I'll get back to you ASAP! |
|
Back to top |
|
|
Ionen Developer
Joined: 06 Dec 2018 Posts: 2717
|
Posted: Tue Aug 03, 2021 9:28 pm Post subject: Re: sys-fs/fuse-2.9.9_rc1 failing to compile |
|
|
RobinEggBlue wrote: | At this point, is it better to pull a I_KNOW_WHAT_I_AM_DOING(when obviously I do not), or just wear a mask until glibc naturally evolves beyond 2.35? | Do /only/ use that now for the downgrade (like above). Just to be clear, do not go back to 2.33, this is not safe, has to be 2.34.
2.34 was just released so it's close to what -9999 is giving you making this (relatively) safe (so, a chance to break free of glibc-9999).
If in doubt, make a `quickpkg sys-libs/glibc` of your current glibc which could potentially be restored from a chroot if anything went wrong.
glibc-2.34 is very new (may run into other issues like fuse here, currently undergoing testing) but it won't be worse than -9999.
Last edited by Ionen on Tue Aug 03, 2021 9:33 pm; edited 1 time in total |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54220 Location: 56N 3W
|
Posted: Tue Aug 03, 2021 9:33 pm Post subject: |
|
|
RobinEggBlue,
The patch Code: | @@ -55,6 +55,7 @@ fi
AC_CHECK_FUNCS([fork setxattr fdatasync splice vmsplice utimensat])
AC_CHECK_FUNCS([posix_fallocate])
AC_CHECK_FUNCS([closefrom])
AC_CHECK_MEMBERS([struct stat.st_atim])
AC_CHECK_MEMBERS([struct stat.st_atimespec]) |
Should read Code: | @@ -55,6 +55,7 @@ fi
AC_CHECK_FUNCS([fork setxattr fdatasync splice vmsplice utimensat])
AC_CHECK_FUNCS([posix_fallocate])
+AC_CHECK_FUNCS([closefrom])
AC_CHECK_MEMBERS([struct stat.st_atim])
AC_CHECK_MEMBERS([struct stat.st_atimespec])
|
The + tells patch to add the line.
The format @@ -55,6 +55,7 @@ says before the patch the 6 lines starting at line 55 become 7 lines. Blank lines matter
The patch provides three lines of context before the change and three lines after the change.
Likewise the + add line and - remove line directives are missing from the second patch.
The headers are missing that tell patch which file to patch. e.g.
Code: | diff --git a/work/vboxnetflt/linux/VBoxNetFlt-linux.c b/work/vboxnetflt/linux/VBoxNetFlt-linux.c
index f824654..b61d82c 100644
--- work/vboxnetflt/linux/VBoxNetFlt-linux.c
+++ work/vboxnetflt/linux/VBoxNetFlt-linux.c
@@ -126,6 +126,10 @@ typedef struct VBOXNETFLTNOTIFIER *PVBOXNETFLTNOTIFIER;
# endif
#endif
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 14, 0)
+#define SKB_GSO_UDP 0
+#endif
+
#if LINUX_VERSION_CODE >= KERNEL_VERSION(3, 20, 0)
# define VBOX_HAVE_SKB_VLAN
#else
| is a properly formatted patch. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
RobinEggBlue n00b
Joined: 03 Aug 2021 Posts: 8 Location: Chicago
|
Posted: Tue Aug 03, 2021 10:01 pm Post subject: Re: sys-fs/fuse-2.9.9_rc1 failing to compile |
|
|
Ionen wrote: | make a `quickpkg sys-libs/glibc` of your current glibc |
Sound advice, I've made a binary pack. Alas, it matters not as I remain unable to further harm myself in confusion... glibc still won't downgrade.
Passing Code: | I_KNOW_WHAT_I_AM_DOING=1 emerge -v1 glibc | still triggers a sanity check during the sys-libs/glibc-2.34 emerge.
NeddySeagoon,
Thank you for stepping in to help me rectify my patches. Once I have glibc sorted I'll fix the formatting per your advice, even if sam_ beats me
to the punch.
Now that such auspicious names as Ionen and Neddy have chimed in, I'd like to thank the Gentoo forum community as a whole.
Your efforts to save not only a poor fool such as myself, but in general for providing a deep pool of supportive and essentially snark-free
content.
Over the last couple of years I've been running this distro and lurking about here I've been blown away by the untold
hours of effort some have you have put into the project. |
|
Back to top |
|
|
sam_ Developer
Joined: 14 Aug 2020 Posts: 1678
|
Posted: Tue Aug 03, 2021 10:04 pm Post subject: Re: sys-fs/fuse-2.9.9_rc1 failing to compile |
|
|
RobinEggBlue wrote: | Ionen wrote: | make a `quickpkg sys-libs/glibc` of your current glibc |
Sound advice, I've made a binary pack. Alas, it matters not as I remain unable to further harm myself in confusion... glibc still won't downgrade.
Passing Code: | I_KNOW_WHAT_I_AM_DOING=1 emerge -v1 glibc | still triggers a sanity check during the sys-libs/glibc-2.34 emerge.
|
Could you upload the build.log here to the forum or to a pastebin? (Guess: if you're using sudo, it needs to be 'sudo I_KNOW_...', not 'I_KNOW_...' sudo').
(just a quick note about the patch: you'll still need to inherit autotools + add eautoreconf in the ebuild in src_prepare, but I think the patch may not cleanly apply to the version in Gentoo. Should be easy though.) |
|
Back to top |
|
|
RobinEggBlue n00b
Joined: 03 Aug 2021 Posts: 8 Location: Chicago
|
Posted: Tue Aug 03, 2021 10:22 pm Post subject: Re: sys-fs/fuse-2.9.9_rc1 failing to compile |
|
|
sam_ wrote: | RobinEggBlue wrote: |
Passing Code: | I_KNOW_WHAT_I_AM_DOING=1 emerge -v1 glibc | still triggers a sanity check during the sys-libs/glibc-2.34 emerge.
|
Could you upload the build.log here to the forum or to a pastebin? (Guess: if you're using sudo, it needs to be 'sudo I_KNOW_...', not 'I_KNOW_...' sudo').
(just a quick note about the patch: you'll still need to inherit autotools + add eautoreconf in the ebuild in src_prepare, but I think the patch may not cleanly apply to the version in Gentoo. Should be easy though.) |
Sure,
Code: |
* Package: sys-libs/glibc-2.34
* Repository: gentoo
* Maintainer: toolchain@gentoo.org
* USE: abi_x86_64 amd64 elibc_glibc kernel_linux ssp static-libs userland_GNU
* FEATURES: ccache network-sandbox preserve-libs sandbox userpriv usersandbox
* Checking general environment sanity.
* Sanity check to keep you from breaking your system:
* Downgrading glibc is not supported and a sure way to destruction.
* ERROR: sys-libs/glibc-2.34::gentoo failed (pretend phase):
* Aborting to save your system.
*
* Call stack:
* ebuild.sh, line 127: Called pkg_pretend
* glibc-2.34.ebuild, line 726: Called sanity_prechecks
* glibc-2.34.ebuild, line 627: Called die
* The specific snippet of code:
* [[ ${I_ALLOW_TO_BREAK_MY_SYSTEM} = yes ]] || die "Aborting to save your system."
*
* If you need support, post the output of `emerge --info '=sys-libs/glibc-2.34::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.34::gentoo'`.
* The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.34/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.34/temp/die.env'.
* Working directory: '/var/tmp/portage/sys-libs/glibc-2.34/empty'
* S: '/var/tmp/portage/sys-libs/glibc-2.34/work/glibc-2.34' |
|
|
Back to top |
|
|
sam_ Developer
Joined: 14 Aug 2020 Posts: 1678
|
Posted: Tue Aug 03, 2021 10:22 pm Post subject: Re: sys-fs/fuse-2.9.9_rc1 failing to compile |
|
|
RobinEggBlue wrote: | sam_ wrote: | RobinEggBlue wrote: |
Passing Code: | I_KNOW_WHAT_I_AM_DOING=1 emerge -v1 glibc | still triggers a sanity check during the sys-libs/glibc-2.34 emerge.
|
Could you upload the build.log here to the forum or to a pastebin? (Guess: if you're using sudo, it needs to be 'sudo I_KNOW_...', not 'I_KNOW_...' sudo').
(just a quick note about the patch: you'll still need to inherit autotools + add eautoreconf in the ebuild in src_prepare, but I think the patch may not cleanly apply to the version in Gentoo. Should be easy though.) |
Sure,
Code: |
* Package: sys-libs/glibc-2.34
* Repository: gentoo
* Maintainer: toolchain@gentoo.org
* USE: abi_x86_64 amd64 elibc_glibc kernel_linux ssp static-libs userland_GNU
* FEATURES: ccache network-sandbox preserve-libs sandbox userpriv usersandbox
* Checking general environment sanity.
* Sanity check to keep you from breaking your system:
* Downgrading glibc is not supported and a sure way to destruction.
* ERROR: sys-libs/glibc-2.34::gentoo failed (pretend phase):
* Aborting to save your system.
*
* Call stack:
* ebuild.sh, line 127: Called pkg_pretend
* glibc-2.34.ebuild, line 726: Called sanity_prechecks
* glibc-2.34.ebuild, line 627: Called die
* The specific snippet of code:
* [[ ${I_ALLOW_TO_BREAK_MY_SYSTEM} = yes ]] || die "Aborting to save your system."
*
* If you need support, post the output of `emerge --info '=sys-libs/glibc-2.34::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.34::gentoo'`.
* The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.34/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.34/temp/die.env'.
* Working directory: '/var/tmp/portage/sys-libs/glibc-2.34/empty'
* S: '/var/tmp/portage/sys-libs/glibc-2.34/work/glibc-2.34' |
|
Aha, do this instead: I_ALLOW_TO_BREAK_MY_SYSTEM=1 emerge -vp1 ...
Keep in mind what ionen said again, ofc. |
|
Back to top |
|
|
sam_ Developer
Joined: 14 Aug 2020 Posts: 1678
|
Posted: Tue Aug 03, 2021 10:24 pm Post subject: |
|
|
sam_ wrote: | RobinEggBlue wrote: | fedeliallalinea,
Thank you for your prompt reply and warm welcome.
I've never applied a patch before, pretty certain the format I'm using is incorrect but I can't google my way to a solution. (Doesn't "diff" turn up a coupla times?...)
|
You can actually get the full patch by pending ".patch" to the URL, but unfortunately, we need to make an ebuild change (eautoreconf) to make it apply, and then I need to rebase my patch a bit. If you wait a little bit, I can try get to this tonight?
[...]
|
Done, see the bug and commit. You'll need to emerge --sync in a little bit first. |
|
Back to top |
|
|
RobinEggBlue n00b
Joined: 03 Aug 2021 Posts: 8 Location: Chicago
|
Posted: Tue Aug 03, 2021 10:26 pm Post subject: Re: sys-fs/fuse-2.9.9_rc1 failing to compile |
|
|
sam_ wrote: |
Aha, do this instead: I_ALLOW_TO_BREAK_MY_SYSTEM=1 emerge -vp1 ...
Keep in mind what ionen said again, ofc. |
Ding ding ding, we have a winner!
Now, while that's emerging, let's see about these patches that brought me here in the first place.
Will report back after I have them squared away or if I become hopelessly lost once more. |
|
Back to top |
|
|
RobinEggBlue n00b
Joined: 03 Aug 2021 Posts: 8 Location: Chicago
|
Posted: Tue Aug 03, 2021 10:29 pm Post subject: |
|
|
sam_ wrote: | sam_ wrote: | RobinEggBlue wrote: | fedeliallalinea,
Thank you for your prompt reply and warm welcome.
I've never applied a patch before, pretty certain the format I'm using is incorrect but I can't google my way to a solution. (Doesn't "diff" turn up a coupla times?...)
|
You can actually get the full patch by pending ".patch" to the URL, but unfortunately, we need to make an ebuild change (eautoreconf) to make it apply, and then I need to rebase my patch a bit. If you wait a little bit, I can try get to this tonight?
[...]
|
Done, see the bug and commit. You'll need to emerge --sync in a little bit first. |
Wow, that was fast...
Well, how long will that take to propagate through the sync servers?
EDIT: Fifteen minutes later and we have fuse-2*, Flatpak, and a whole new (old) glibc.
Thank you sam_, Ionen, and NeddySeagoon. |
|
Back to top |
|
|
sam_ Developer
Joined: 14 Aug 2020 Posts: 1678
|
Posted: Tue Aug 03, 2021 11:00 pm Post subject: |
|
|
RobinEggBlue wrote: | sam_ wrote: | sam_ wrote: | RobinEggBlue wrote: | fedeliallalinea,
Thank you for your prompt reply and warm welcome.
I've never applied a patch before, pretty certain the format I'm using is incorrect but I can't google my way to a solution. (Doesn't "diff" turn up a coupla times?...)
|
You can actually get the full patch by pending ".patch" to the URL, but unfortunately, we need to make an ebuild change (eautoreconf) to make it apply, and then I need to rebase my patch a bit. If you wait a little bit, I can try get to this tonight?
[...]
|
Done, see the bug and commit. You'll need to emerge --sync in a little bit first. |
Wow, that was fast...
Well, how long will that take to propagate through the sync servers?
EDIT: Fifteen minutes later and we have fuse-2*, Flatpak, and a whole new (old) glibc.
Thank you sam_, Ionen, and NeddySeagoon. |
Hah, I was just about to come say "it should be there now if you're using git at least". Great news! Really pleased things are ok now.
Now, don't mess with toolchain stuff again, or you'll get coal at Christmas! |
|
Back to top |
|
|
RobinEggBlue n00b
Joined: 03 Aug 2021 Posts: 8 Location: Chicago
|
Posted: Thu Aug 05, 2021 3:19 am Post subject: |
|
|
sherinemuasher wrote: | Es scheint ein Fehler im System zu sein. Haben Sie versucht, das System zu überprüfen? Vielleicht ändert sich dadurch etwas. Sie können es auch auf anderen Geräten versuchen. Es könnte auch daran liegen, dass es auf Ihr Gerät nicht anwendbar ist. |
Falscher thread, mein Freund. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|