Re:[SOLVED] [gentoo-user] ERROR: app-office/gnucash-4.4::gentoo failed (compile phase)
On 4/2/21 5:53 PM, konsolebox wrote: > This might be related to this: https://bugs.gentoo.org/762661 Yes, that was it. Someone suggested uninstalling gnucash-4.2 and installing 4.4 and it worked!
Re: [gentoo-user] ERROR: app-office/gnucash-4.4::gentoo failed (compile phase)
This might be related to this: https://bugs.gentoo.org/762661 -- konsolebox
[gentoo-user] ERROR: app-office/gnucash-4.4::gentoo failed (compile phase)
I just got this error:
ERROR: compile
ERROR: app-office/gnucash-4.4::gentoo failed (compile phase):
ninja -v -j8 -l8 failed
Call stack:
ebuild.sh, line 125: Called src_compile
environment, line 3290: Called cmake_src_compile
environment, line 1181: Called cmake_build
environment, line 1150: Called eninja
environment, line 1602: Called die
The specific snippet of code:
"$@" || die "${nonfatal_args[@]}" "${*} failed"
I didn't try try to emerge again as system is still updating.
emerge --info '=app-office/gnucash-4.4::gentoo'
Portage 3.0.17 (python 3.8.8-final-0, default/linux/amd64/17.1/desktop,
gcc-9.3.0, glibc-2.32-r7, 5.4.80-gentoo-r1 x86_64)
=
System Settings
=
System uname:
Linux-5.4.80-gentoo-r1-x86_64-AMD_Ryzen_5_1400_Quad-Core_Processor-with-glibc2.2.5
KiB Mem:16392964 total, 5699260 free
KiB Swap: 524284 total,523516 free
Timestamp of repository gentoo: Fri, 02 Apr 2021 19:30:01 +
Head commit of repository gentoo: d71fade8c2afdbf154e2bf3916befa7f576d4a4a
sh bash 5.0_p18
ld GNU ld (Gentoo 2.34 p6) 2.34.0
app-shells/bash: 5.0_p18::gentoo
dev-java/java-config: 2.3.1::gentoo
dev-lang/perl:5.30.3::gentoo
dev-lang/python: 3.8.8::gentoo, 3.9.2::gentoo
dev-util/cmake: 3.18.5::gentoo
sys-apps/baselayout: 2.7::gentoo
sys-apps/openrc: 0.42.1-r1::gentoo
sys-apps/sandbox: 2.20::gentoo
sys-devel/autoconf: 2.13-r1::gentoo, 2.69-r5::gentoo
sys-devel/automake: 1.16.2-r1::gentoo
sys-devel/binutils: 2.34-r2::gentoo, 2.35.1-r1::gentoo
sys-devel/gcc:9.3.0-r2::gentoo, 10.2.0-r5::gentoo
sys-devel/gcc-config: 2.3.3::gentoo
sys-devel/libtool:2.4.6-r6::gentoo
sys-devel/make: 4.3::gentoo
sys-kernel/linux-headers: 5.10::gentoo (virtual/os-headers)
sys-libs/glibc: 2.32-r7::gentoo
Repositories:
gentoo
location: /var/db/repos/gentoo
sync-type: rsync
sync-uri: rsync://rsync.gentoo.org/gentoo-portage
priority: -1000
sync-rsync-verify-max-age: 24
sync-rsync-extra-opts:
sync-rsync-verify-jobs: 1
sync-rsync-verify-metamanifest: yes
brother-overlay
location: /var/lib/layman/brother-overlay
masters: gentoo
priority: 50
Local
location: /usr/local/portage
masters: gentoo
priority:
ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="* -@EULA @FREE"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=native -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/lib64/fax /usr/share/easy-rsa
/usr/share/gnupg/qualified.txt /var/spool/fax/etc
/var/www/localhost/htdocs/phpmyadmin"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d
/etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release
/etc/php/apache2-php7.4/ext-active/ /etc/php/cgi-php7.4/ext-active/
/etc/php/cli-php7.4/ext-active/ /etc/revdep-rebuild /etc/sandbox.d
/etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d
/etc/texmf/updmap.d /etc/texmf/web2c /var/spool/fax/etc/xferfaxlog"
CXXFLAGS="-march=native -O2 -pipe"
DISTDIR="/var/cache/distfiles"
EMERGE_DEFAULT_OPTS="--autounmask-write=y --keep-going --with-bdeps=y"
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="-march=native -O2 -pipe"
FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs
collision-protect 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="-march=native -O2 -pipe"
GENTOO_MIRRORS="http://mirror.csclub.uwaterloo.ca/gentoo-distfiles/
http://gentoo.osuosl.org/ ftp://mirror.csclub.uwaterloo.ca/gentoo-distfiles/
http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/
ftp://linux.rz.ruhr-uni-bochum.de/gentoo-mirror/
ftp://ftp.spline.inf.fu-berlin.de/mirrors/gentoo/
http://ftp.spline.inf.fu-berlin.de/mirrors/gentoo/;
LANG="en_US.utf8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j8 -l8"
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="X a52 aac acpi alsa amd64 apache2 bluetooth branding bzip2 cairo cdda cdr
cgi cleartype cli corefonts crypt cups dbus dri dts dvd dvdr elogind emboss
encode exif fam flac foomaticdb fortran gdbm gif gimp gimpprint gpm gtk gui
iconv icu
Re: [gentoo-user] Sandbox violation when emerging gentoo-kernel-5.4.105
Thank you. Disabling ccache fixed it.
[gentoo-user] Sandbox violation when emerging gentoo-kernel-5.4.105
Hello Gentoo, I've recently started with Gentoo in the last few months, still interested in learning about the build system and to start trying to slim down my install. This morning I ran into the following issue, I'll try to provide as much detail as I can: THE ISSUE: I am failing to emerge sys-kernel/gentoo-kernel-5.4.105 with a sandbox violation. The violation summary is inserted below: * --- ACCESS VIOLATION SUMMARY --- * LOG FILE: "/var/tmp/portage/sys-kernel/gentoo-kernel-5.4.105/temp/sandbox.log" * VERSION 1.0 FORMAT: F - Function called FORMAT: S - Access Status FORMAT: P - Path as passed to function FORMAT: A - Absolute Path (not canonical) FORMAT: R - Canonical Path FORMAT: C - Command Line F: unlink S: deny P: /dev/null.dwo A: /dev/null.dwo R: /dev/null.dwo C: x86_64-pc-linux-gnu-gcc -Werror -gsplit-dwarf -S -x c /dev/null -o /dev/null * The relevant section of the log is: x86_64-pc-linux-gnu-gcc -Wl,-O1 -Wl,--as-needed -o scripts/kconfig/conf scripts/kconfig/conf.o scripts/kconfig/confdata.o scripts/kconfig/expr.o scripts/kconfig/lexer.lex.o scripts/kconfig/parser.tab.o scripts/kconfig/preprocess.o scripts/kconfig/symbol.o scripts/kconfig/conf --olddefconfig Kconfig * ACCESS DENIED: unlink: /dev/null.dwo # # configuration written to .config # make[1]: Leaving directory '/var/tmp/portage/sys-kernel/gentoo-kernel-5.4.105/work/modprep' I am trying to use a custom config file and am building gentoo-kernel with the "savedconfig" USE flag. I also recently updated to Portage 3.0.17. TROUBLESHOOTING STEPS: To try to troubleshoot, I have ran "eclean distfiles" and have removed the "/var/tmp/portage/sys-kernel/gentoo-kernel-5.4.105" directory. I then ran a sync and deep update, but the issue remains. I have attached the log generated by portage. Let me know if there is any other info that would be helpful. Any help would be greatly appreciated, Grant[32;01m * [39;49;00mPackage:sys-kernel/gentoo-kernel-5.4.105 [32;01m * [39;49;00mRepository: gentoo [32;01m * [39;49;00mMaintainer: dist-ker...@gentoo.org [32;01m * [39;49;00mUSE:abi_x86_64 amd64 elibc_glibc initramfs kernel_linux savedconfig userland_GNU [32;01m * [39;49;00mFEATURES: ccache network-sandbox preserve-libs sandbox userpriv usersandbox [32;01m*[0m Using python3.8 to build >>> Unpacking source... >>> Unpacking linux-5.4.tar.xz to /var/tmp/portage/sys-kernel/gentoo-kernel-5.4.105/work >>> Unpacking genpatches-5.4-108.base.tar.xz to /var/tmp/portage/sys-kernel/gentoo-kernel-5.4.105/work >>> Unpacking genpatches-5.4-108.extras.tar.xz to /var/tmp/portage/sys-kernel/gentoo-kernel-5.4.105/work >>> Unpacking gentoo-kernel-config-5.4.89.tar.gz to /var/tmp/portage/sys-kernel/gentoo-kernel-5.4.105/work >>> Unpacking kernel-x86_64.config.5.4.21 to /var/tmp/portage/sys-kernel/gentoo-kernel-5.4.105/work unpack kernel-x86_64.config.5.4.21: file format not recognized. Ignoring. >>> Source unpacked in /var/tmp/portage/sys-kernel/gentoo-kernel-5.4.105/work >>> Preparing source in /var/tmp/portage/sys-kernel/gentoo-kernel-5.4.105/work/linux-5.4 ... [32;01m*[0m Applying 1000_linux-5.4.1.patch ... [A[231C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying 1001_linux-5.4.2.patch ... [A[231C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying 1002_linux-5.4.3.patch ... [A[231C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying 1003_linux-5.4.4.patch ... [A[231C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying 1004_linux-5.4.5.patch ... [A[231C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying 1005_linux-5.4.6.patch ... [A[231C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying 1006_linux-5.4.7.patch ... [A[231C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying 1007_linux-5.4.8.patch ... [A[231C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying 1008_linux-5.4.9.patch ... [A[231C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying 1009_linux-5.4.10.patch ... [A[231C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying 1010_linux-5.4.11.patch ... [A[231C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying 1011_linux-5.4.12.patch ... [A[231C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying 1012_linux-5.4.13.patch ... [A[231C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying 1013_linux-5.4.14.patch ... [A[231C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying 1014_linux-5.4.15.patch ... [A[231C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying 1015_linux-5.4.16.patch ... [A[231C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying 1016_linux-5.4.17.patch ... [A[231C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying 1017_linux-5.4.18.patch ... [A[231C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying
Re: [gentoo-user] Console scrollback
Hello, Karl. Thanks for the reply. On Fri, Apr 02, 2021 at 21:32:04 +0200, k...@aspodata.se wrote: > Alan Mackenzie: > ... > > I've now cobbled together a working console scroll on Linux > > 5.4.80-gentoo-r1. In the end, I reused much of the old machinery which > > was still present in 4.19.97. Once I've tidied it up, I hope that the > > resulting patch file will apply cleanly also to later versions than > > 5.4.80-r1. > ... > Nice, where is the patch so I can try ? I've attached a patch to this post. To apply it, the following seems to work from the top directory of a kernel source tree, e.g. 5.4.80-r1: $ patch -p0 < diff.20210402.diff .. Then you'll need to run make menuconfig (or whatever), going down to Device Drivers/Graphic support/Console display driver support and there accepting the defaults for the new config variables. (This is assuming you've got FRAMEBUFFER support enabled in a neighbouring page.) Then build the kernel as normal, and put the new version into whatever boot loader you use. It should (??) run, with a scrollback buffer on each virtual terminal. Just a word about the current state of the source - it is rough, with things unfinished. The "word" STOUGH (pronounced "stuff") is just a word I use which appears nowhere else and enables me to find changes quickly and unambiguously. As I said, I'm not finished with the changes, and swapping from and back to a scrolled tty isn't completely satisfactory. Nevertheless, I hope it works for you and you have fun with it. > > (i) The scrolling doesn't work on /dev/tty1 aka the console. > > (ii) When, e.g., /dev/tty6 has been scrolled upwards a bit, and then > >pressed to go to /dev/tty2, on returning to /dev/tty6, the > > scrolling has been cancelled and the cursor is no longer visible. > > However, the scrollback buffer is still present. > > > > I think I'm fairly likely to be able to solve (ii). However, (i), the > > problem with /dev/tty1, has me baffled. I don't know where to start > > looking for the problem. If anybody with some kernel knowledge could > > make any suggestions, I'd be very grateful. > What happens if you set /dev/console to be /dev/ttyS0, i.e. make sure > that tty1 is the only one using the first virtual console. I will try than. Thanks! > Regards, > /Karl Hammar -- Alan Mackenzie (Nuremberg, Germany). --- drivers/video/console/Kconfig.orig 2021-03-31 19:14:48.186140856 + +++ drivers/video/console/Kconfig 2021-03-31 12:39:08.090301096 + @@ -79,6 +79,52 @@ help Low-level framebuffer-based console driver. +config FRAMEBUFFER_CONSOLE_SOFT_SCROLLBACK + bool "Enable Scrollback Buffer in System RAM" + depends on FB=y && FRAMEBUFFER_CONSOLE + default y + help + This option creates scrollback buffers for each framebuffer console, + or one buffer for them all. These buffers are allocated dynamically + during initialisation. + +If you want this feature, say 'Y' here and enter the amount of +RAM to allocate for this buffer. If unsure, say 'N'. + +config FRAMEBUFFER_CONSOLE_SOFT_SCROLLBACK_SIZE + int "Scrollback Buffer Size (in KB)" + depends on FRAMEBUFFER_CONSOLE_SOFT_SCROLLBACK + range 1 1024 + default "128" + help + Enter the amount of System RAM to allocate for scrollback buffers of + framebuffer consoles. Each character position on the video takes 2 + bytes of storage. 128k will give you approximately 4 240x67 + screenfuls of scrollback buffer. + +config FRAMEBUFFER_CONSOLE_SOFT_SCROLLBACK_PERSISTENT_ENABLE_BY_DEFAULT + bool "Persistent Scrollback History for each framebuffer console by default" + depends on FB=y && FRAMEBUFFER_CONSOLE && FRAMEBUFFER_CONSOLE_SOFT_SCROLLBACK + default y + help + + Say Y here if the scrollback history should persist by default when + switching between consoles. Otherwise, the scrollback history will + be flushed the first time a scroll-up operation occurs on the new + console after the console is switched. STOUGH!!! FIXME!!! This + feature can also be enabled using the boot command line parameter + 'vgacon.scrollback_persistent=1'. + + This feature might break your tool of choice to flush the scrollback + buffer, e.g. clear(1) will work fine but Debian's clear_console(1) + will be broken, which might cause security issues. + You can use the escape sequence \e[3J instead if this feature is + activated. + + Note that a buffer of VGACON_SOFT_SCROLLBACK_SIZE is taken for each + created tty device. + So if you use a RAM-constrained system, say
Re: [gentoo-user] Console scrollback
Alex Mackenzie: ... > I've now cobbled together a working console scroll on Linux > 5.4.80-gentoo-r1. In the end, I reused much of the old machinery which > was still present in 4.19.97. Once I've tidied it up, I hope that the > resulting patch file will apply cleanly also to later versions than > 5.4.80-r1. ... Nice, where is the patch so I can try ? > (i) The scrolling doesn't work on /dev/tty1 aka the console. > (ii) When, e.g., /dev/tty6 has been scrolled upwards a bit, and then >pressed to go to /dev/tty2, on returning to /dev/tty6, the > scrolling has been cancelled and the cursor is no longer visible. > However, the scrollback buffer is still present. > > I think I'm fairly likely to be able to solve (ii). However, (i), the > problem with /dev/tty1, has me baffled. I don't know where to start > looking for the problem. If anybody with some kernel knowledge could > make any suggestions, I'd be very grateful. What happens if you set /dev/console to be /dev/ttyS0, i.e. make sure that tty1 is the only one using the first virtual console. Regards, /Karl Hammar
Re: [gentoo-user] Console scrollback
Hello, Gentoo. On Wed, Jan 20, 2021 at 19:59:09 +, Alan Mackenzie wrote: [Context: Scrolling on the Linux text console using the keys and has been removed from the kernel. This is not a Good Thing.] > What I have in mind now is writing a Linux driver, a small piece of code > which would piggy-back on the existing virtual terminal drivers, and > simply pass everything through to and from the main driver, filtering out > things relevant to scrolling, and processing these in my new driver. > I've spent the last few evenings reading up on drivers, and reading the > relevant source code from 4.19.97. I can understand the kernel > maintainers not being enthusiastic about the existing code. But that > dates from, I believe, the 1990s, when RAM was measured in megabytes, and > processor speeds in megahertz. Optimisation for speed and store usage > just isn't important any more. I finally got around to looking into this seriously in the last couple of weeks. The above plan turned out not to be the right thing. I've now cobbled together a working console scroll on Linux 5.4.80-gentoo-r1. In the end, I reused much of the old machinery which was still present in 4.19.97. Once I've tidied it up, I hope that the resulting patch file will apply cleanly also to later versions than 5.4.80-r1. As a matter of interest, the kernel code for the console is not the easiest in the world to deal with, having too many abstractions and too few comments. ;-( I've enhanced the mechanism so that each tty has its own scrollback buffer, rather than one buffer being shared between all tty's. The default size of these buffers is now 128kB, but can be set in make menuconfig. I'm intending to make sharing a buffer between all tty's be an option, but haven't implemented that yet. The code, as yet, is a bit scruffy (in fact, very scruffy), and I have several technical problems: (i) The scrolling doesn't work on /dev/tty1 aka the console. (ii) When, e.g., /dev/tty6 has been scrolled upwards a bit, and then pressed to go to /dev/tty2, on returning to /dev/tty6, the scrolling has been cancelled and the cursor is no longer visible. However, the scrollback buffer is still present. I think I'm fairly likely to be able to solve (ii). However, (i), the problem with /dev/tty1, has me baffled. I don't know where to start looking for the problem. If anybody with some kernel knowledge could make any suggestions, I'd be very grateful. -- Alan Mackenzie (Nuremberg, Germany).
Re: [gentoo-user] Sandbox violation when emerging gentoo-kernel-5.4.105
On Fri, Apr 02, 2021 at 04:58:56PM +, itsgrant wrote: > THE ISSUE: > I am failing to emerge sys-kernel/gentoo-kernel-5.4.105 with a sandbox > violation. The violation summary is inserted below: > [...] > R: /dev/null.dwo > C: x86_64-pc-linux-gnu-gcc -Werror -gsplit-dwarf -S -x c /dev/null -o > /dev/null This is https://bugs.gentoo.org/770931 Happens when using FEATURES=ccache, so can turn it off to workaround. -- ionen signature.asc Description: PGP signature
Re: [gentoo-user] Sandbox violation when emerging gentoo-kernel-5.4.105
Hey, Quoting itsgrant (2021-04-02 18:58:56) >* ACCESS DENIED: unlink: /dev/null.dwo I had the same issue, I found a bug report about it, it was due to ccache: https://bugs.gentoo.org/770931 Guillaume
Re: [gentoo-user] Cannot find LILO
On Fri, Apr 2, 2021 at 9:37 PM Peter Humphrey wrote: > > Hello list, > > Today's update brought in sys-kernel/gentoo-sources-5.10.27, but it comes with > a problem: when I 'make install' I get 'Cannot find LILO'. Of course it can't, > but why is it wanted? > > $ uname -a > Linux peak 5.4.97-gentoo #1 SMP Sun Feb 21 22:53:16 GMT 2021 x86_64 > Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz GenuineIntel GNU/Linux > > Another x86_64 box Just Works, so I suppose I must have something wrong on > this one. > > Clues, anyone? Your ARCH is set to i386 most likely. Maybe it's a CHOST configuration issue. -- konsolebox
[gentoo-user] Cannot find LILO
Hello list, Today's update brought in sys-kernel/gentoo-sources-5.10.27, but it comes with a problem: when I 'make install' I get 'Cannot find LILO'. Of course it can't, but why is it wanted? $ uname -a Linux peak 5.4.97-gentoo #1 SMP Sun Feb 21 22:53:16 GMT 2021 x86_64 Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz GenuineIntel GNU/Linux Another x86_64 box Just Works, so I suppose I must have something wrong on this one. Clues, anyone? -- Regards, Peter.
