Re: [gentoo-user] net-mail/metamail - removal
On 13/12/2022 21:01, the...@sys-concept.com wrote: I just noticed that "net-mail/metamail" is masked and scheduled for removal 12/23/2022 I'm using "mailto" which is part of metamail. Is there any alternative package that contain this function "mailto" Frankly metamail has been dead for decades - the last release was nearly 30 years ago. If you want to send MIME-encoded email from a command line then just about any normal mail client such as "mail" from GNU's mailutils package (Gentoo: net-mail/mailutils) should suffice.
[gentoo-user] net-mail/metamail - removal
I just noticed that "net-mail/metamail" is masked and scheduled for removal 12/23/2022 I'm using "mailto" which is part of metamail. Is there any alternative package that contain this function "mailto" -- Thelma
RE: [OT] Re: [gentoo-user] NAS and replacing with larger drives
> -Original Message- > From: Peter Humphrey > Sent: Sunday, December 11, 2022 3:35 AM > To: gentoo-user@lists.gentoo.org > Subject: [OT] Re: [gentoo-user] NAS and replacing with larger drives > > On Friday, 9 December 2022 10:34:00 GMT I wrote: > > > in the 1970s the national grid was monitored and analysed with a > > Ferranti Argus 500 machine with 24KB RAM and a 2MB disk. It was common > > for American visitors to believe that was just driving the control > > engineers' > > displays, and where was the main computer? > > Er... There was no RAM in those days, not of the type we know today. In fact > it was 2-microsecond core store. Each tiny ferromagnetic toroid was threaded > with one X wire, one Y wire and (I think it was) a sync pulse wire. A > remarkable labour of love to build such a thing. > > -- > Regards, > Peter. > Well, it wasn't built with transistors, but it was Random Access Memory. As opposed to Sequential Access Memory like mercury delay lines. And it was periodic refresh, just like most modern RAM. That 24KB though would have been literally 196,608 ferrite cores (assuming it was an 8 bit byte on that system), and they were probably hand-soldered. Although it looks like the original Argus line used 12 bit words. So it was probably a 6 bit byte. Still, a lot of soldering. Interestingly, the Argus 400 and 500 series was one of the first systems to use multilayer PCBs and the company had to develop a lot of the techniques for creating those themselves. LMP
Re: [gentoo-user] Gaming on gentoo
On Tue, 13 Dec 2022 13:49:54 + Artur Tamm wrote: > sourceforge tarball was a prebuilt binary (at least the one I downloaded). The source is there too in a different directory. > I saw that the source code is here: > https://github.com/sezero/quakespasm/tree/master/Quake > The default Makefile might need some editing for a successful compilation. I just grabbed the linux-64 archive from sourceforge. I have never run the prebuilt binaries before but I tried it just to see what would happen. The quakespasm-sdl2 segfaulted the same as my own build but the quakespasm (sdl I suppose?) does run here. So that is something! I can run their sdl quakespasm but not my own built here. That is better than nothing but I'd still like to hear about your experience. I'd be happy if I could build and run my own if I can figure out what the issue is.
Re: [gentoo-user] Gaming on gentoo
sourceforge tarball was a prebuilt binary (at least the one I downloaded). I saw that the source code is here: https://github.com/sezero/quakespasm/tree/master/Quake The default Makefile might need some editing for a successful compilation. Artur On Tue, 13 Dec 2022 at 13:45, Alan Ianson wrote: > On Tue, 13 Dec 2022 15:32:38 +0200 > Artur Tamm wrote: > > > did you try to compile quakespasm yourself? > > Yes, I emerged 0.94.1 and also the git version (0.95.1) using the > quakespasm-.ebuild. Both of those are from the gentoo guru repository. > I also built 0.95.1 myself from the tarball at the quakespasm sourceforge > site but none of those will run for me here. I'm not sure why. > > >
Re: [gentoo-user] Gaming on gentoo
On Tue, 13 Dec 2022 15:32:38 +0200 Artur Tamm wrote: > did you try to compile quakespasm yourself? Yes, I emerged 0.94.1 and also the git version (0.95.1) using the quakespasm-.ebuild. Both of those are from the gentoo guru repository. I also built 0.95.1 myself from the tarball at the quakespasm sourceforge site but none of those will run for me here. I'm not sure why.
Re: [gentoo-user] Gaming on gentoo
did you try to compile quakespasm yourself? On Tue, 13 Dec 2022, 15:25 Alan Ianson, wrote: > On Tue, 13 Dec 2022 12:28:18 + > Artur Tamm wrote: > > > I can test out quakespasm in the evening (for me) as I need to extract > the > > pak file to test it (as it exitied while trying to load it). > > I just built ironwail (https://github.com/andrei-drexler/ironwail) and > that runs fine here. Ironwail is a quakespasm fork, fairly recent I think. > > Still, I like to get to the bottom of my issues with quakespasm and > darkplaces if I can. > >
Re: [gentoo-user] Gaming on gentoo
On Tue, 13 Dec 2022 12:28:18 + Artur Tamm wrote: > I can test out quakespasm in the evening (for me) as I need to extract the > pak file to test it (as it exitied while trying to load it). I just built ironwail (https://github.com/andrei-drexler/ironwail) and that runs fine here. Ironwail is a quakespasm fork, fairly recent I think. Still, I like to get to the bottom of my issues with quakespasm and darkplaces if I can.
Re: [gentoo-user] Gaming on gentoo
On Tue, 13 Dec 2022 12:28:18 + Artur Tamm wrote: > I can test out quakespasm in the evening (for me) as I need to extract the > pak file to test it (as it exitied while trying to load it). I appreciate that, please let us know how it goes for you. I may have to disable use flags or something. I'm not sure exactly but if you have success with quakespasm (or darkplaces) can you post the output of "ldd quakespasm (or darkplaces)"? That might shed some light on why it fails here.
Re: [gentoo-user] Gaming on gentoo
I can test out quakespasm in the evening (for me) as I need to extract the pak file to test it (as it exitied while trying to load it). Arutr On Tue, 13 Dec 2022 at 12:24, Alan Ianson wrote: > On Tue, 13 Dec 2022 12:12:19 + > Artur Tamm wrote: > > > Hi, > > > > It seems that the game is a binary blob and requires some older > libraries. > > Have you installed some 32bit libraries. You can check what you need with > > 'ldd some_binary'. For 32bit libraries you might want to use 'abi_x86_32' > > for the needed libraries or enable it globlly in make.conf and then > > recompile everything. > > I do have some 32bit games I'll be trying to run but I haven't looked at > that yet. This is a 64bit quakespasm (as far as I know). > > This is what ldd has to say about quakespasm.. > > alan@irondust:~$ ldd /usr/bin/quakespasm > linux-vdso.so.1 (0x7ffe7b188000) > libm.so.6 => /lib64/libm.so.6 (0x7f7f78f9) > libOpenGL.so.0 => /usr/lib64/libOpenGL.so.0 (0x7f7f78f64000) > libvorbisfile.so.3 => /usr/lib64/libvorbisfile.so.3 > (0x7f7f78f5a000) > libvorbis.so.0 => /usr/lib64/libvorbis.so.0 (0x7f7f78f2c000) > libogg.so.0 => /usr/lib64/libogg.so.0 (0x7f7f78f21000) > libmad.so.0 => /usr/lib64/libmad.so.0 (0x7f7f78efe000) > libSDL2-2.0.so.0 => /usr/lib64/libSDL2-2.0.so.0 > (0x7f7f78882000) > libc.so.6 => /lib64/libc.so.6 (0x7f7f786b4000) > /lib64/ld-linux-x86-64.so.2 (0x7f7f79085000) > libGLdispatch.so.0 => /usr/lib64/libGLdispatch.so.0 > (0x7f7f785fc000) > libasound.so.2 => /usr/lib64/libasound.so.2 (0x7f7f7850f000) > libpulse.so.0 => /usr/lib64/libpulse.so.0 (0x7f7f784b9000) > libX11.so.6 => /usr/lib64/libX11.so.6 (0x7f7f78377000) > libXext.so.6 => /usr/lib64/libXext.so.6 (0x7f7f7836) > libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x7f7f78353000) > libXi.so.6 => /usr/lib64/libXi.so.6 (0x7f7f7833f000) > libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x7f7f78336000) > libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x7f7f78329000) > libpulsecommon-16.1.so => /usr/lib64/pulseaudio/ > libpulsecommon-16.1.so (0x7f7f7829f000) > libdbus-1.so.3 => /usr/lib64/libdbus-1.so.3 (0x7f7f78252000) > libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x7f7f78228000) > libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x7f7f7821b000) > libsndfile.so.1 => /usr/lib64/libsndfile.so.1 (0x7f7f781a5000) > libasyncns.so.0 => /usr/lib64/libasyncns.so.0 (0x7f7f7819d000) > libXau.so.6 => /usr/lib64/libXau.so.6 (0x7f7f78198000) > libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x7f7f7819) > libbsd.so.0 => /usr/lib64/libbsd.so.0 (0x7f7f78179000) > libmd.so.0 => /usr/lib64/libmd.so.0 (0x7f7f7816c000) > alan@irondust:~$ > > Everything there looks good to me. I have since built darkplaces and have > a similar experience with that. > > There must be some detail in the works that I am missing. > > I appreciate your input. > >
Re: [gentoo-user] Gaming on gentoo
On Tue, 13 Dec 2022 12:12:19 + Artur Tamm wrote: > Hi, > > It seems that the game is a binary blob and requires some older libraries. > Have you installed some 32bit libraries. You can check what you need with > 'ldd some_binary'. For 32bit libraries you might want to use 'abi_x86_32' > for the needed libraries or enable it globlly in make.conf and then > recompile everything. I do have some 32bit games I'll be trying to run but I haven't looked at that yet. This is a 64bit quakespasm (as far as I know). This is what ldd has to say about quakespasm.. alan@irondust:~$ ldd /usr/bin/quakespasm linux-vdso.so.1 (0x7ffe7b188000) libm.so.6 => /lib64/libm.so.6 (0x7f7f78f9) libOpenGL.so.0 => /usr/lib64/libOpenGL.so.0 (0x7f7f78f64000) libvorbisfile.so.3 => /usr/lib64/libvorbisfile.so.3 (0x7f7f78f5a000) libvorbis.so.0 => /usr/lib64/libvorbis.so.0 (0x7f7f78f2c000) libogg.so.0 => /usr/lib64/libogg.so.0 (0x7f7f78f21000) libmad.so.0 => /usr/lib64/libmad.so.0 (0x7f7f78efe000) libSDL2-2.0.so.0 => /usr/lib64/libSDL2-2.0.so.0 (0x7f7f78882000) libc.so.6 => /lib64/libc.so.6 (0x7f7f786b4000) /lib64/ld-linux-x86-64.so.2 (0x7f7f79085000) libGLdispatch.so.0 => /usr/lib64/libGLdispatch.so.0 (0x7f7f785fc000) libasound.so.2 => /usr/lib64/libasound.so.2 (0x7f7f7850f000) libpulse.so.0 => /usr/lib64/libpulse.so.0 (0x7f7f784b9000) libX11.so.6 => /usr/lib64/libX11.so.6 (0x7f7f78377000) libXext.so.6 => /usr/lib64/libXext.so.6 (0x7f7f7836) libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x7f7f78353000) libXi.so.6 => /usr/lib64/libXi.so.6 (0x7f7f7833f000) libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x7f7f78336000) libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x7f7f78329000) libpulsecommon-16.1.so => /usr/lib64/pulseaudio/libpulsecommon-16.1.so (0x7f7f7829f000) libdbus-1.so.3 => /usr/lib64/libdbus-1.so.3 (0x7f7f78252000) libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x7f7f78228000) libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x7f7f7821b000) libsndfile.so.1 => /usr/lib64/libsndfile.so.1 (0x7f7f781a5000) libasyncns.so.0 => /usr/lib64/libasyncns.so.0 (0x7f7f7819d000) libXau.so.6 => /usr/lib64/libXau.so.6 (0x7f7f78198000) libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x7f7f7819) libbsd.so.0 => /usr/lib64/libbsd.so.0 (0x7f7f78179000) libmd.so.0 => /usr/lib64/libmd.so.0 (0x7f7f7816c000) alan@irondust:~$ Everything there looks good to me. I have since built darkplaces and have a similar experience with that. There must be some detail in the works that I am missing. I appreciate your input.
Re: [gentoo-user] Gaming on gentoo
Hi, It seems that the game is a binary blob and requires some older libraries. Have you installed some 32bit libraries. You can check what you need with 'ldd some_binary'. For 32bit libraries you might want to use 'abi_x86_32' for the needed libraries or enable it globlly in make.conf and then recompile everything. Artur On Tue, 13 Dec 2022 at 08:37, Alan Ianson wrote: > On Mon, 12 Dec 2022 21:17:35 -0800 > Alan Ianson wrote: > > > Hello list, > > > > I am a gentoo newbie. I have installed gentoo about a month ago and have > been busy since in my free time getting it up and running. > > > > I have a problem with quakespasm, it segfaults on startup.. this is what > I get.. > > Just as a follow up on my own post.. ;) > > I ran valgrind against quakespasm and it says this.. > > alan@irondust:~$ valgrind -q /usr/bin/quakespasm > > valgrind: Fatal error at startup: a function redirection > valgrind: which is mandatory for this platform-tool combination > valgrind: cannot be set up. Details of the redirection are: > valgrind: > valgrind: A must-be-redirected function > valgrind: whose name matches the pattern: strlen > valgrind: in an object with soname matching: ld-linux-x86-64.so.2 > valgrind: was not found whilst processing > valgrind: symbols from the object with soname: ld-linux-x86-64.so.2 > valgrind: > valgrind: Possible fixes: (1, short term): install glibc's debuginfo > valgrind: package on this machine. (2, longer term): ask the packagers > valgrind: for your Linux distribution to please in future ship a non- > valgrind: stripped ld.so (or whatever the dynamic linker .so is called) > valgrind: that exports the above-named function using the standard > valgrind: calling conventions for this platform. The package you need > valgrind: to install for fix (1) is called > valgrind: > valgrind:On Debian, Ubuntu: libc6-dbg > valgrind:On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo > valgrind: > valgrind: Note that if you are debugging a 32 bit process on a > valgrind: 64 bit system, you will need a corresponding 32 bit debuginfo > valgrind: package (e.g. libc6-dbg:i386). > valgrind: > valgrind: Cannot continue -- exiting now. Sorry. > > I'm not exactly sure what the above says/means. Are there gentoo packages > I can install to get better info? > > I'll keep at this and see what I can find. Any ideas/thoughts/help would > be welcome. :) > >
[gentoo-user] Gaming on gentoo
On Mon, 12 Dec 2022 21:17:35 -0800 Alan Ianson wrote: > Hello list, > > I am a gentoo newbie. I have installed gentoo about a month ago and have been > busy since in my free time getting it up and running. > > I have a problem with quakespasm, it segfaults on startup.. this is what I > get.. Just as a follow up on my own post.. ;) I ran valgrind against quakespasm and it says this.. alan@irondust:~$ valgrind -q /usr/bin/quakespasm valgrind: Fatal error at startup: a function redirection valgrind: which is mandatory for this platform-tool combination valgrind: cannot be set up. Details of the redirection are: valgrind: valgrind: A must-be-redirected function valgrind: whose name matches the pattern: strlen valgrind: in an object with soname matching: ld-linux-x86-64.so.2 valgrind: was not found whilst processing valgrind: symbols from the object with soname: ld-linux-x86-64.so.2 valgrind: valgrind: Possible fixes: (1, short term): install glibc's debuginfo valgrind: package on this machine. (2, longer term): ask the packagers valgrind: for your Linux distribution to please in future ship a non- valgrind: stripped ld.so (or whatever the dynamic linker .so is called) valgrind: that exports the above-named function using the standard valgrind: calling conventions for this platform. The package you need valgrind: to install for fix (1) is called valgrind: valgrind:On Debian, Ubuntu: libc6-dbg valgrind:On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo valgrind: valgrind: Note that if you are debugging a 32 bit process on a valgrind: 64 bit system, you will need a corresponding 32 bit debuginfo valgrind: package (e.g. libc6-dbg:i386). valgrind: valgrind: Cannot continue -- exiting now. Sorry. I'm not exactly sure what the above says/means. Are there gentoo packages I can install to get better info? I'll keep at this and see what I can find. Any ideas/thoughts/help would be welcome. :)
