rxvt-unicode build snafu
Again I apologize for including a long log file from the ailing rxvt-unicode on my 'NetBSD nebby.localdomain 9.0_BETA NetBSD 9.0_BETA (GENERIC) #0: Sun Aug 18 14:36:49 UTC 2019 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64' install: Script started on Thu Nov 21 23:41:55 2019 => Bootstrap dependency digest>=20010302: found digest-20190127 ===> Skipping vulnerability checks. WARNING: No /var/db/pkg/pkg-vulnerabilities file found. WARNING: To fix run: `/usr/sbin/pkg_admin -K /var/db/pkg fetch-pkg-vulnerabilities'. => Checksum SHA1 OK for rxvt-unicode-9.22.tar.bz2 => Checksum RMD160 OK for rxvt-unicode-9.22.tar.bz2 => Checksum SHA512 OK for rxvt-unicode-9.22.tar.bz2 ===> Installing dependencies for rxvt-unicode-9.22nb5 == The supported build options for rxvt-unicode are: perl rxvt-term unicode3 xft2 The currently selected options are: perl rxvt-term unicode3 xft2 You can select which build options to use by setting PKG_DEFAULT_OPTIONS or the following variable. Its current value is shown: PKG_OPTIONS.rxvt-unicode = rxvt-term == => Tool dependency pkgconf-[0-9]*: found pkgconf-1.6.0 => Build dependency xorgproto>=2016.1: found xorgproto-2018.4 => Build dependency xcb-proto>=1.4: found xcb-proto-1.13nb1 => Build dependency cwrappers>=20150314: found cwrappers-20180325 => Full dependency perl>=5.30.0<5.32.0: found perl-5.30.0nb1 => Full dependency libXft>=2.3.2nb2: found libXft-2.3.3 => Full dependency libX11>=1.1: found libX11-1.6.7 => Full dependency libXpm>=3.5.4.2: found libXpm-3.5.12nb1 ===> Overriding tools for rxvt-unicode-9.22nb5 ===> Extracting for rxvt-unicode-9.22nb5 ===> Patching for rxvt-unicode-9.22nb5 => Applying pkgsrc patches for rxvt-unicode-9.22nb5 ===> Creating toolchain wrappers for rxvt-unicode-9.22nb5 ===> Configuring for rxvt-unicode-9.22nb5 => Generating pkg-config file for builtin expat package. => Modifying GNU configure scripts to avoid --recheck => Replacing config-guess with pkgsrc versions => Replacing config-sub with pkgsrc versions => Replacing install-sh with pkgsrc version => Replacing Perl interpreter in src/perl/*. checking build system type... x86_64--netbsd checking host system type... x86_64--netbsd configuring for rxvt 9.22 checking for x86_64--netbsd-gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether we are using the GNU C++ compiler... yes checking whether c++ accepts -g... yes checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... (cached) /usr/bin/grep checking for egrep... (cached) /usr/bin/egrep checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking for library containing strerror... none required checking for working libsupc++... ok checking for library containing setlocale... none required checking for library containing gethostbyname... none required checking for library containing socket... none required checking how to run the C++ preprocessor... c++ -E checking sys/inotify.h usability... no checking sys/inotify.h presence... no checking for sys/inotify.h... no checking sys/epoll.h usability... no checking sys/epoll.h presence... no checking for sys/epoll.h... no checking sys/event.h usability... yes checking sys/event.h presence... yes checking for sys/event.h... yes checking port.h usability... no checking port.h presence... no checking for port.h... no checking poll.h usability... yes checking poll.h presence... yes checking for poll.h... yes checking sys/select.h usability... yes checking sys/select.h presence... yes checking for sys/select.h... yes checking sys/eventfd.h usability... no checking sys/eventfd.h presence... no checking for sys/eventfd.h... no checking sys/signalfd.h usability... no checking sys/signalfd.h presence... no checking for sys/signalfd.h... no checking for inotify_init... no checking for epoll_ctl... no checking for kqueue... yes checking for port_create... no checking for poll... yes checking for select... yes checking for
Basic vt100 console "noisy
Date: Wed, 20 Nov 2019 20:14:24 -0500 From: Jason Mitchell To: Clay Daniels Subject: Re: Basic vt100 console "noisy" I wanted to share what Jason sent me privately: "Clay, The extra tty's are accessible by Control-Alt-F2 through F4 if they're enabled (I think they are by default). Jason M." This is good information, which I did not know. I tried it with my older 2014 HP Pavilion that I'm trying to load NetBSD on, and this did not seem to work. However, I was having the same trouble with "noisy system messages" on my OpenBSD install on my new home-built Ryzen 7 3700x machine and it worked like MAGIC! Eliminated the noise entirely, and like he says there are three of these extra tty logins. CTL-ALT-F(1,2,OR 3) What I think I need to do is find room on my new machine for NetBSD:-;
Re: [netbsd-users] Re: Basic vt100 console "noisy"
On Fri, 22 Nov 2019, at 07:40, Rhialto wrote: : : > If you have a serial terminal at hand, it is always fun to try. I > operated a DEC Alpha with a serial console, even though it had display > hardware. I had a real Wyse terminal running in vt52 emulation mode as a console for a number of years until the power supply blew and I was quoted an outrageous price to replace it ... while it was running it was awesome to have that in the corner of the room - with screen running it was as functional as a regular pseudo-terminal ... Regards, Malcolm -- Malcolm Herbert m...@mjch.net
Re: Basic vt100 console "noisy"
On Thu 21 Nov 2019 at 00:21:27 +, Clay Daniels wrote: > Thanks so much Johnny & Olaf. The other consoles look promising. Does this > relate to the NetBSD Guide Chap 3.9 Disk Prep process for selecting > bootblocks? > > http://www.netbsd.org/docs/guide/en/chap-exinst.html#exinst-disk-preparation-process Sort of. In the sense that if you select a serial console, the green output goes to the serial port and not to the VGA screen. Johnny is correct in pointing out that perhaps I should not have called these switchable virtual terminals "console", but people are sloppy and the thing is called "wscons" which makes it harder. > I have just been selecting the BIOS console, and maybe I should select one > of the serial ports, or option g : Use existing bootblocks ? > > I think the console selection is the clue. I will play with this and try a > fresh install with one of the serial ports, like com0. You can even change the console in an existing installation (although personally I've never needed it). Look at the manual page of installboot, and the option -o console=... . You can also (for the current boot only) set the console from the boot loader. See manual page boot(8), command "consdev". If you have a serial terminal at hand, it is always fun to try. I operated a DEC Alpha with a serial console, even though it had display hardware. > Clay -Olaf. -- Olaf 'Rhialto' Seibert -- rhialto at falu dot nl ___ Anyone who is capable of getting themselves made President should on \X/ no account be allowed to do the job. --Douglas Adams, "THGTTG" signature.asc Description: PGP signature
