Re: [gentoo-user] dev-lang/perl upgrade failure
Hi, On Tue, May 10 at 09:11, Matt Connell wrote: > I can't figure out why a perl update isn't building. This is only > happening on one single machine out of the half dozen Gentoo systems I > have running. I've never had issues building perl itself either. > Modules sure, but never the main perl package. > > My search-fu is failing me as well, apparently, so I turn to y'all. > Can someone point me in the right direction? You might want to check out https://forums.gentoo.org/viewtopic-p-8680082.html The solution suggested is to clear out obsolete and unmaintained packages which may be causing your build to hit the error check with. emerge -av --depclean perl-cleaner --all Always a good idea to do a regular cleanup with depclean and I suggest running perl-cleaner with the -p "pretend" option first. HTH -- Bob Dunlop
[gentoo-user] dev-lang/perl upgrade failure
I can't figure out why a perl update isn't building. This is only happening on one single machine out of the half dozen Gentoo systems I have running. I've never had issues building perl itself either. Modules sure, but never the main perl package. My search-fu is failing me as well, apparently, so I turn to y'all. Can someone point me in the right direction? Attached are the output of: - emerge -pqv '=dev-lang/perl-5.34.0-r9::gentoo' as emerge-pretend.txt - emerge --info '=dev-lang/perl-5.34.0-r9::gentoo' as emerge-info.txt And the build log as build.log * Package:dev-lang/perl-5.34.0-r9 * Repository: gentoo * Maintainer: p...@gentoo.org * USE:abi_x86_64 amd64 elibc_glibc gdbm kernel_linux userland_GNU * FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox >>> Unpacking source... >>> Unpacking perl-5.34.0.tar.xz to /var/tmp/portage/dev-lang/perl-5.34.0-r9/work >>> Unpacking perl-5.34.0-patches-1.tar.xz to /var/tmp/portage/dev-lang/perl-5.34.0-r9/work >>> Unpacking perl-cross-1.3.6.tar.gz to /var/tmp/portage/dev-lang/perl-5.34.0-r9/work >>> Source unpacked in /var/tmp/portage/dev-lang/perl-5.34.0-r9/work >>> Preparing source in /var/tmp/portage/dev-lang/perl-5.34.0-r9/work/perl-5.34.0 ... * Adding 0101-Fix-build-with-gdb120.patch to patch bundle * Injecting patch-level info into 0006-List-packaged-patches-in-patchlevel.h.patch.desc ( *List-packaged-patches* ) * Applying 0001-Fix-hpux-hints.patch ... [ ok ] * Applying 0002-aix-gcc-detection-and-shared-library-soname-support.patch ... [ ok ] * Applying 0003-cpan-ExtUtils-MakeMaker-drop-PORTAGE_TMPDIR-from-LD_.patch ... [ ok ] * Applying 0004-Remove-rpath-and-append-LDFLAGS-to-lddlflags.patch ... [ ok ] * Applying 0005-Add-headers-for-opensolaris.patch ... [ ok ] * Applying 0006-List-packaged-patches-in-patchlevel.h.patch ... [ ok ] * Applying 0007-Cleanup-PATH-and-shrpenv.patch ... [ ok ] * Applying 0008-Tweak-enc2xs-to-follow-symlinks-and-ignore-missing-I.patch ... [ ok ] * Applying 0009-darwin-Use-CC-to-link.patch ... [ ok ] * Applying 0010-Provide-a-sensible-INSTALLDIRS-default-for-modules-i.patch ... [ ok ] * Applying 0011-Fix-interix-hints.patch ... [ ok ] * Applying 0012-Set-libperl-soname.patch ... [ ok ] * Applying 0013-Add-etc-perl-to-INC.patch ... [ ok ] * Applying 0014-cpan-ExtUtils-MakeMaker-remove-targets-that-generate.patch ... [ ok ] * Applying 0015-Don-t-force-fstack-protector-on-everyone.patch ... [ ok ] * Applying 0016-Do-not-set-custom-CFLAGS-in-cpan-Digest-SHA.patch ... [ ok ] * Applying 0017-Configure-Don-t-include-sources-in-usr-local-for-com.patch ... [ ok ] * Applying 0018-cpan-IO-Socket-IP-Disable-network-tests.patch ... [ ok ] * Applying 0019-Fix-EUMM-podlocal-tests.patch ... [ ok ] * Applying 0020-Skip-auto-linking-nsl-and-cl.patch ... [ ok ] * Applying 0021-Disable-porting-tests-which-create-fun-false-failure.patch ... [ ok ] * Applying 0022-Disable-PathTools-tests-which-fails-under-sandboxing.patch ... [ ok ] * Applying 0023-Fix-CPAN-FirstTime-defaults-with-nonexisting-site-di.patch ... [ ok ] * Applying 0024-Pass-LD-settings-through-to-subdirectories.patch ... [ ok ] * Applying 0025-Memoize-Storable-respect-nstore-option-not-respected.patch ... [ ok ] * Applying 0026-Better-errors-for-man-pages-from-standard-input.patch ... [ ok ] * Applying 0027-Respect-umask-during-installation.patch ... [ ok ] * Applying 0028-Document-that-CCFLAGS-should-include-Config-ccflags.patch ... [ ok ] * Applying 0029-Fix-parallel-building.patch ... [ ok ] * Applying 0030-Add-support-for-Dgentoolibdirs.patch ... [ ok ] * Applying 0101-Fix-build-with-gdb120.patch ... [ ok ] * Generating patchlevel-gentoo.h >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-lang/perl-5.34.0-r9/work/perl-5.34.0 ... * Scanning for old @INC dirs matching '.*/5[.][0-9]+\([.][0-9]+\|\)$' in: /usr/lib64/perl5 /usr/local/lib64/perl5 /usr/lib64/perl5/vendor_perl * Normalizing/Sorting candidate list: 5.34 5.34 * to remove '5.34' First let's make sure your kit is complete. Checking... Locating common programs... Checking compatibility between /bin/echo and builtin echo (if any)... Symbolic links are supported. Checking how to test for symbolic links... You can test for symbolic links with 'test -h'. Checking for cross-compile No targethost for running compiler tests against defined, running locally Good, your tr supports [:lower:] and [:upper:] to convert case. Using [:upper:] and [:lower:] to convert case. UNCACHED_ERR_FD provides an invalid file descriptor, using stderr aix bsdos dos_djgpp freemint interix linux-android ncr_tower os400 sco_2_3_3 svr5 uwin aix_3catamount dragonfly gnu irix_4 linux netbsdposix-bc sco_2_3_4 ti1500 vos aix_4convexos dynix gnukfreebsd irix_5 lynxos newsos4 qnx solaris_2
Re: [gentoo-user] Bluetooth speakers
On Tuesday, 10 May 2022 13:00:13 BST Peter Humphrey wrote: > On Tuesday, 10 May 2022 10:26:13 BST Michael wrote: > > On Tuesday, 10 May 2022 09:17:32 BST Peter Humphrey wrote: > > > Indeed, and I've now replaced the speakers, the 3.5mm cable and the USB > > > dongle - every sound component is new. When I tested it yesterday in the > > > plasma control panel, I heard one "front left", very loud, and then > > > nothing. I thought some BT stuff must still be lying around somewhere, > > > so > > > I've installed a new system from scratch, using a kernel .config from > > > before I started with BT, and today I still hear no sound. > > > > > > This seems like witchcraft now. > > > > Before you start ritual exorcisms, have you checked you are using the > > > correct 3.5mm jack and it is inserted properly? See below: > I thought of the easy check, eventually. I booted into Windows 10 and was > immediately greeted with its bing-bong-bong sound - over the 3.5mm jack > connection. > > So now I just have to find out what's wrong with my plasma sound system. In the late 90s early 00s I had a Compaq laptop which occasionally will fail to produce any audio output. Booting into Windows would on its own unlock the audio and allow me to enjoy my audio card on Linux once more, until the next time. I never bottomed out what was causing this, but I developed a theory of a dodgy Linux alsa driver which would trip over itself when it tried to initialise the audio device and an always-working-as-intended MSWindows audio driver. Anyway, isn't pulseaudio being replaced by the Pipewire framework? I understand Pipewire is meant to work better with BT audio and A2DP codecs, but I don't know how well it works on Plasma. I haven't installed pulseaudio on this PC, but pipewire seems to be running on a Plasma desktop: $ ps axf | grep -i pipe 4274 tty8 Sl+0:00 | \_ /usr/bin/pipewire 4275 tty8 Sl+0:00 | \_ /usr/bin/pipewire -c pipewire-pulse.conf 15917 pts/1S+ 0:00 \_ grep -E --colour=auto --color=auto -i pipe signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Some symbols render incomplete in text mode
сб, 7 мая 2022 г. в 12:47, Frank Steinmetzger : > > Am Thu, May 05, 2022 at 08:46:39PM +0300 schrieb gevisz: > > > It seems to me that the problem is somehow related > > to redrawing a frame. However, I am still not sure if > > it is a problem of software or hardware. > > > > I have not tried another google-chrome profile so far. > > I would create a new (temporary test) user and log on with that. If the > problem still persists, it’s either a system config, a library (cairo, > freetype et al, graphics driver) or maybe even a hardware issue. Yes. It is exactly how I intended to do this, and sorry for not having done it yet. However, I have found that the problem of the incomplete rendering symbols in text mode appears only after I play youtube videos in google-chrome and persist after exiting it. Playing youtube videos in firefox-bin does not cause this problem to appear, nor does running google-chrome without playing youtube videos in it. Moreover, in Firefox-bin, I even do not have the problem with incomplete rendering symbols in the youtube video player toolbar. So, I already can blame this problem completely on google-chrome. Moreover, I already know how to avoid it. :) P.S. My current version of google-chrome is 101.0.4951.54. However, the problem already appeared in its earlier versions and has survived several updates of the google-chrome.
Re: [gentoo-user] Bluetooth speakers
On Tuesday, 10 May 2022 10:26:13 BST Michael wrote: > On Tuesday, 10 May 2022 09:17:32 BST Peter Humphrey wrote: > > Indeed, and I've now replaced the speakers, the 3.5mm cable and the USB > > dongle - every sound component is new. When I tested it yesterday in the > > plasma control panel, I heard one "front left", very loud, and then > > nothing. I thought some BT stuff must still be lying around somewhere, so > > I've installed a new system from scratch, using a kernel .config from > > before I started with BT, and today I still hear no sound. > > > > This seems like witchcraft now. > > Before you start ritual exorcisms, have you checked you are using the > correct 3.5mm jack and it is inserted properly? See below: I thought of the easy check, eventually. I booted into Windows 10 and was immediately greeted with its bing-bong-bong sound - over the 3.5mm jack connection. So now I just have to find out what's wrong with my plasma sound system. -- Regards, Peter.
Re: 3.5mm jacks (was Re: [gentoo-user] Bluetooth speakers)
On Tuesday, 10 May 2022 11:29:51 BST k...@aspodata.se wrote: > Michael: > ... > > > Jacks have a TS, or TRS, TRRS, or TRRRS contacts arrangement, depending on > > the connectivity they are meant to offer - mono, stereo, stereo+mic and > > whether this is balanced or unbalanced. > > ... > > I have an old laptop (Thinkpad T61p [1]) with a stereo and > microphone jack, both 3.5mm. > > How do one know if it is a TRS or TRRS variant without opening the > case ? > > Maybe it is a trrs jack since when I inserts a trs cable (to speaker) > the ouput sound whines a lot, mostly masking the intended sound. > > I found some specs in [2] and [3]. > > Regards, > /Karl Hammar > > [1] https://www.thinkwiki.org/wiki/Category:T61p > [2] https://www.headphonesty.com/2019/04/headphone-jacks-plugs-explained/ > [3] https://en.wikipedia.org/wiki/Phone_connector_(audio) I'm not familiar with the specifics of your laptop. It is a matter of digging through spec sheets to find out, or opening up the case, but often the socket is enclosed in a plastic molding. Checking part numbers may reveal what the contacts arrangement is. If you're only getting one channel audio or noise/distortion, after the jack has been inserted fully, then it is likely you have a mismatch between the jack & socket contacts. In all likelihood you have a TRRS line-out for stereo earphones and perhaps a TRS line-in for mic mono. Sadly there is a historical mismatch between different manufacturers' pin arrangements, especially so with camcorders and old portable DVD players (remember those?!) So there's no guarantee some mic or earphones released by one manufacturer will always work with other devices. The contacts look the same, but the ground and live connections could be reversed. With PCs the contacts tend to be more standardised. signature.asc Description: This is a digitally signed message part.
3.5mm jacks (was Re: [gentoo-user] Bluetooth speakers)
Michael: ... > Jacks have a TS, or TRS, TRRS, or TRRRS contacts arrangement, depending on > the > connectivity they are meant to offer - mono, stereo, stereo+mic and whether > this is balanced or unbalanced. ... I have an old laptop (Thinkpad T61p [1]) with a stereo and microphone jack, both 3.5mm. How do one know if it is a TRS or TRRS variant without opening the case ? Maybe it is a trrs jack since when I inserts a trs cable (to speaker) the ouput sound whines a lot, mostly masking the intended sound. I found some specs in [2] and [3]. Regards, /Karl Hammar [1] https://www.thinkwiki.org/wiki/Category:T61p [2] https://www.headphonesty.com/2019/04/headphone-jacks-plugs-explained/ [3] https://en.wikipedia.org/wiki/Phone_connector_(audio)
Re: [gentoo-user] Bluetooth speakers
On Tuesday, 10 May 2022 09:17:32 BST Peter Humphrey wrote: > Indeed, and I've now replaced the speakers, the 3.5mm cable and the USB > dongle - every sound component is new. When I tested it yesterday in the > plasma control panel, I heard one "front left", very loud, and then nothing. > I thought some BT stuff must still be lying around somewhere, so I've > installed a new system from scratch, using a kernel .config from before I > started with BT, and today I still hear no sound. > > This seems like witchcraft now. Before you start ritual exorcisms, have you checked you are using the correct 3.5mm jack and it is inserted properly? See below: Jacks have a TS, or TRS, TRRS, or TRRRS contacts arrangement, depending on the connectivity they are meant to offer - mono, stereo, stereo+mic and whether this is balanced or unbalanced. Once I plugged in earphones (earbuds) with a 3.5mm jack in a MoBo and ended up with my ears getting uncomfortably warm in seconds. Whatever voltage that MoBo was applying to the 3.5mm socket was far too high. The earphones were fried while I was scratching my head trying to understand how could this have happened. I made a mental note never to trust the thin clients provided by my employer. Some times the construction of the spring loaded contacts in a plug is so poor, a correctly inserted jack does not provide a good and reliable electrical contact. I'm running a desktop presently where I have to be careful how far in I push a 3.5mm stereo jack, to be able to obtain both stereo channels audio from the speakers. Annoying as this is, I have to fettle with the jack to find the exact position at which I am able to get audio from both channels without distortion. Despite the above mishaps I generally opt for a cable rather than BT for audio. YMMV. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Bluetooth speakers
On Monday, 9 May 2022 15:38:30 BST Michael wrote: > On Monday, 9 May 2022 14:56:42 BST k...@aspodata.se wrote: > > Peter: > > ... > > > > > What would help is some idea of how the whole BT system works, > > > > ... > > > > There are two incompatible types of bluetooth: > > Bluetooth Low Energy (BLE) > > Bluetooth Classic > > > > see: > > https://www.bluetooth.com/learn-about-bluetooth/tech-overview/ > > > > You must check which generation of bluetooth your speaker uses. > > > > If your speaker uses the classic type, this might help you: > > https://wiki.debian.org/Bluetooth/Alsa > > > > /// > > > > More info about bluetooth: > > https://en.wikipedia.org/wiki/Bluetooth > > https://www.bluetooth.com/specifications/specs/ > > > > /// > > > > Current linux bluetooth tools (http://www.bluez.org/) doesn't > > handle bluetooth classic, unless you build bluez with > > --enable-deprecated configure option. > > > > Also, bluez has dropped direct /dev file access for users, you > > > > have to set up and go through dbus regardless wether you like it > > or not. > > > > Regards, > > /Karl Hammar > > I've met some success getting BT to work and I tend to follow these basic > steps: > > 1. Configure the kernel according to the BT chipset available on the PC. > > 2. Power the BT chip by using whatever hardware button is available and > check dmesg identified the device and loaded whatever module and firmware > is necessary. > > 3. Use 'rfkill list' to check the device is not blocked and unblock it if > necessary. > > 4. Run 'rc-service -v bluetooth start'. > > 5. Run 'bluetoothctl' to scan, list, pair and trust any peripherals - > exchange a PIN to facilitate pairing as necessary. > > These steps should be relatively easy to complete and GUI tools are also > available to assist with the above. Any problems thereafter are userspace > related, i.e. whether the applications I use will be able to work with the > BT peripherals. Audio has been problematic on a particular use case, where > neither alsa (bluez-alsa), nor pulseaudio allowed me to output audio via > BT. Eventually I tried blueman which after a couple of restarts helped > pulseaudio to recognise the device and output audio through it. Yes, I went through all that, just as you said, but still I got no sound. > In all cases I prefer cables to temperamental radio connectivity and where > quality matters, like it can be in some audio applications, I would seek to > connect with a cable. Indeed, and I've now replaced the speakers, the 3.5mm cable and the USB dongle - every sound component is new. When I tested it yesterday in the plasma control panel, I heard one "front left", very loud, and then nothing. I thought some BT stuff must still be lying around somewhere, so I've installed a new system from scratch, using a kernel .config from before I started with BT, and today I still hear no sound. This seems like witchcraft now. -- Regards, Peter.
