Re: [gentoo-user] Systemd-boot not compiling
On Monday, April 8, 2019 4:44:58 PM CEST Peter Humphrey wrote: > On Monday, 8 April 2019 15:29:47 BST J. Roeleveld wrote: > > On April 8, 2019 1:14:38 PM UTC, Peter Humphrey > > wrote: > > >Hello list, > > > > > >Is anyone else having trouble emerging systemd-boot-241? This machine > > >has a small rescue system as an alternative boot, and I get a mysterious > > >error when I emerge the package. The end of the log shows this: > > > > > >[248/248] x86_64-pc-linux-gnu-gcc -o bootctl 'bootctl@exe/ > > >src_boot_bootctl.c.o' -Wl,--no-undefined -Wl,--as-needed -Wl,-z,relro > > >-Wl,- z,now -Wl,--gc-sections -O2 -march=haswell -pipe -Wl,-O1 > > >-Wl,--as-needed -Wl,--start-group src/shared/libsystemd-shared-241.a src/ > > >libsystemd/libsystemd_static.a src/basic/libbasic.a > > >/usr/lib64/libblkid.so > > >-lrt/usr/lib64/libcap.so /usr/lib64/libmount.so -lrt -lm -Wl,--end-group > > >-pthread > > >'-Wl,-rpath,$ORIGIN/src/shared:$ORIGIN/src/libsystemd:$ORIGIN/src/ > > >basic'-Wl,-rpath-link,/var/tmp/portage/sys-boot/systemd-boot-241/work/ > > >systemd-boot-241- build/src/shared:/var/tmp/portage/sys-boot/systemd > > >-boot-241/work/systemd-boot-241-build/src/libsystemd:/var/tmp/portage/sys > > >- > > >boot/systemd-boot-241/work/ systemd-boot-241-build/src/basic > > >stat: No such file or directory > > > > > > * ERROR: sys-boot/systemd-boot-241::gentoo failed (compile phase): > > > * (no error message) > > > > > >But it compiles just fine on the main system. > > > > > >Perhaps something is missing from the rescue system and hasn't been > > >caught by the ebuild, but I can't think of what. If 'stat' had said what > > >file or directory wasn't present, I'd be able to dig a bit deeper to find > > >the problem. > > > > > >I see the same behaviour on another machine. Both are 64-bit, but only > > >this one is ~amd64; the other one has a KEYWORD to enable systemd-boot. > > > > Have you tried compiling with "MAKEOPTS="-j 1"? (Eg, no parallel build? > > I knew I'd missed something out - yes, that's the first thing I tried. if you search for "stat" in the build-log and/or makefile(s), does it show which file(s) it is checking? -- Joost
Re: [gentoo-user] syslog-ng not outputting to tty12
On Sat, Apr 06, 2019 at 10:40:22AM +0100, Mick wrote > Right, as Joost points out if there is no tty12 specified you won't have one > to display syslog-ng. Check your /etc/rc.conf for this entry: > > # on Linux and Hurd, this is the number of ttys allocated for logins > # It is used in the consolefont, keymaps, numlock and termencoding > # service scripts. > rc_tty_number=12 I have that. I do have one non-standard item in /etc/inittab that I've been using for years without trouble... # TERMINALS #x1:12345:respawn:/sbin/agetty 38400 console linux c1:12345:respawn:/sbin/agetty 38400 tty1 linux c2:2345:respawn:/sbin/agetty 38400 tty2 linux c3:2345:respawn:/sbin/agetty 38400 tty3 linux c4:2345:respawn:/sbin/agetty 38400 tty4 linux c5:2345:respawn:/sbin/agetty 38400 tty5 linux c6:2345:respawn:/sbin/agetty 38400 tty6 linux c7:2345:respawn:/sbin/agetty 38400 tty7 linux c8:2345:respawn:/sbin/agetty 38400 tty8 linux c9:2345:respawn:/sbin/agetty 38400 tty9 linux This puts X on tty10. Back before xrandr was up to its current feature set, I'd bring up a second X at a different reolution on tty11, to get something resembling "fullscreen" on video streams that were 640x480 or 512x384. Logging to tty12 has always worked fine. -- Walter Dnes I don't run "desktop environments"; I run useful applications
Re: [gentoo-user] Systemd-boot not compiling
On Monday, 8 April 2019 15:29:47 BST J. Roeleveld wrote: > On April 8, 2019 1:14:38 PM UTC, Peter Humphrey wrote: > >Hello list, > > > >Is anyone else having trouble emerging systemd-boot-241? This machine > >has a small rescue system as an alternative boot, and I get a mysterious > >error when I emerge the package. The end of the log shows this: > > > >[248/248] x86_64-pc-linux-gnu-gcc -o bootctl 'bootctl@exe/ > >src_boot_bootctl.c.o' -Wl,--no-undefined -Wl,--as-needed -Wl,-z,relro > >-Wl,- z,now -Wl,--gc-sections -O2 -march=haswell -pipe -Wl,-O1 > >-Wl,--as-needed -Wl,--start-group src/shared/libsystemd-shared-241.a src/ > >libsystemd/libsystemd_static.a src/basic/libbasic.a /usr/lib64/libblkid.so > >-lrt/usr/lib64/libcap.so /usr/lib64/libmount.so -lrt -lm -Wl,--end-group > >-pthread '-Wl,-rpath,$ORIGIN/src/shared:$ORIGIN/src/libsystemd:$ORIGIN/src/ > >basic'-Wl,-rpath-link,/var/tmp/portage/sys-boot/systemd-boot-241/work/ > >systemd-boot-241- build/src/shared:/var/tmp/portage/sys-boot/systemd > >-boot-241/work/systemd-boot-241-build/src/libsystemd:/var/tmp/portage/sys- > >boot/systemd-boot-241/work/ systemd-boot-241-build/src/basic > >stat: No such file or directory > > > > * ERROR: sys-boot/systemd-boot-241::gentoo failed (compile phase): > > * (no error message) > > > >But it compiles just fine on the main system. > > > >Perhaps something is missing from the rescue system and hasn't been > >caught by the ebuild, but I can't think of what. If 'stat' had said what > >file or directory wasn't present, I'd be able to dig a bit deeper to find > >the problem. > > > >I see the same behaviour on another machine. Both are 64-bit, but only > >this one is ~amd64; the other one has a KEYWORD to enable systemd-boot. > > Have you tried compiling with "MAKEOPTS="-j 1"? (Eg, no parallel build? I knew I'd missed something out - yes, that's the first thing I tried. -- Regards, Peter.
Re: [gentoo-user] Systemd-boot not compiling
On April 8, 2019 1:14:38 PM UTC, Peter Humphrey wrote: >Hello list, > >Is anyone else having trouble emerging systemd-boot-241? This machine >has a >small rescue system as an alternative boot, and I get a mysterious >error when >I emerge the package. The end of the log shows this: > >[248/248] x86_64-pc-linux-gnu-gcc -o bootctl 'bootctl@exe/ >src_boot_bootctl.c.o' -Wl,--no-undefined -Wl,--as-needed -Wl,-z,relro >-Wl,- >z,now -Wl,--gc-sections -O2 -march=haswell -pipe -Wl,-O1 >-Wl,--as-needed - >Wl,--start-group src/shared/libsystemd-shared-241.a src/libsystemd/ >libsystemd_static.a src/basic/libbasic.a /usr/lib64/libblkid.so -lrt >/usr/ >lib64/libcap.so /usr/lib64/libmount.so -lrt -lm -Wl,--end-group >-pthread '- >Wl,-rpath,$ORIGIN/src/shared:$ORIGIN/src/libsystemd:$ORIGIN/src/basic' >-Wl,- >rpath-link,/var/tmp/portage/sys-boot/systemd-boot-241/work/systemd-boot-241- >build/src/shared:/var/tmp/portage/sys-boot/systemd-boot-241/work/systemd- >boot-241-build/src/libsystemd:/var/tmp/portage/sys-boot/systemd-boot-241/work/ >systemd-boot-241-build/src/basic >stat: No such file or directory > * ERROR: sys-boot/systemd-boot-241::gentoo failed (compile phase): > * (no error message) > >But it compiles just fine on the main system. > >Perhaps something is missing from the rescue system and hasn't been >caught by >the ebuild, but I can't think of what. If 'stat' had said what file or >directory wasn't present, I'd be able to dig a bit deeper to find the >problem. > >I see the same behaviour on another machine. Both are 64-bit, but only >this >one is ~amd64; the other one has a KEYWORD to enable systemd-boot. Have you tried compiling with "MAKEOPTS="-j 1"? (Eg, no parallel build? -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
[gentoo-user] Systemd-boot not compiling
Hello list, Is anyone else having trouble emerging systemd-boot-241? This machine has a small rescue system as an alternative boot, and I get a mysterious error when I emerge the package. The end of the log shows this: [248/248] x86_64-pc-linux-gnu-gcc -o bootctl 'bootctl@exe/ src_boot_bootctl.c.o' -Wl,--no-undefined -Wl,--as-needed -Wl,-z,relro -Wl,- z,now -Wl,--gc-sections -O2 -march=haswell -pipe -Wl,-O1 -Wl,--as-needed - Wl,--start-group src/shared/libsystemd-shared-241.a src/libsystemd/ libsystemd_static.a src/basic/libbasic.a /usr/lib64/libblkid.so -lrt /usr/ lib64/libcap.so /usr/lib64/libmount.so -lrt -lm -Wl,--end-group -pthread '- Wl,-rpath,$ORIGIN/src/shared:$ORIGIN/src/libsystemd:$ORIGIN/src/basic' -Wl,- rpath-link,/var/tmp/portage/sys-boot/systemd-boot-241/work/systemd-boot-241- build/src/shared:/var/tmp/portage/sys-boot/systemd-boot-241/work/systemd- boot-241-build/src/libsystemd:/var/tmp/portage/sys-boot/systemd-boot-241/work/ systemd-boot-241-build/src/basic stat: No such file or directory * ERROR: sys-boot/systemd-boot-241::gentoo failed (compile phase): * (no error message) But it compiles just fine on the main system. Perhaps something is missing from the rescue system and hasn't been caught by the ebuild, but I can't think of what. If 'stat' had said what file or directory wasn't present, I'd be able to dig a bit deeper to find the problem. I see the same behaviour on another machine. Both are 64-bit, but only this one is ~amd64; the other one has a KEYWORD to enable systemd-boot. -- Regards, Peter.
