libera/#devuan/ Tuesday, 2021-11-09

UsLlike the pipe key having two places on us keyboards and not on uk keaybords.. Or however it was.00:00
UsLΒΆ00:01
Afdal:o00:01
UsLanyway. Gnight.00:02
UsLI must pretend to be an adult tomorrow.00:03
adhocscroll lock was a thing on DOS based systems,00:08
adhocdoes not always work on the same on modern systems though00:08
adhoccrtl+S locks and crtl+Q unlocks scroll in your terminal00:08
adhocnot sure which machine introduced that00:08
adhocworks on my vt22000:09
adhocnot on the old wyse terminal00:09
adhocand pretty sure did not on the wyse 5200:09
adhoci suppose it is as much to do what is in the termcap for that display terminal00:09
AfdalFor some reason I have all my ttys set to autologin01:06
Afdalthat doesn't seem like a great idea01:06
AfdalHow did I do this and how do I set it so that I have to actually login when I go to a tty01:07
adhocAfdal: what does your /etc/inittab look like ?01:21
adhoci have entries like;01:21
adhoc1:2345:respawn:/sbin/getty 38400 tty101:21
adhoc2:23:respawn:/sbin/getty 38400 tty201:21
adhoc2-6 are basicall tthe same with the first character (number) the same as the tty number01:22
adhocthe second column is the run level, in this case run level 2 and 3 being multi-user01:22
* adhoc remember the first glass tty 01:23
adhocand messing with;01:23
adhoc  #T0:23:respawn:/sbin/getty -L ttyS0 9600 vt10001:23
adhocalthough mine was a vt22001:24
Afdal1:2345:respawn:/bin/login -f afdal </dev/tty1 >/dev/tty1 2>&101:24
Afdal2:23:respawn:/bin/login -f afdal </dev/tty2 >/dev/tty2 2>&101:24
Afdaland so on01:24
adhocneat, never seen that before01:24
Afdalwhat's neat about it @_@01:25
adhocauto login, never seen that before01:25
AfdalYeah but how'd that happen in the first place @_@01:25
Afdaland how do I turn it off01:25
adhoci mean, there are issues, but that could be useful for kiosk type systems01:25
AfdalI've never edited this manually01:25
adhocwell, look at my lines above01:25
adhocno idea, but comment them out, copy'n'paste in new lines01:26
gnarfaceAfdal: certainly you can think of something you've done01:26
adhocmode the /bin/login to /sbin/getty 38400 tty101:26
AfdalI hate mysteries -_-01:26
Afdalwhat does that number even mean01:27
Afdalwhat does any of this gibberish mean01:27
adhocserial port speed, effectively01:27
adhoc38400 baud01:27
adhocdivide by 10 gives you approximately the bytes per second01:27
gnarfacewhich installer did you use Afdal?01:28
Afdalwhy getty01:28
Afdaluh the terminal based one01:28
Afdalwhose name I keep forgetting01:28
gnarfacedebootstrap?01:28
Afdalno01:28
* gnarface raises eyebrow01:28
* Afdal raises paw01:29
adhocgetty has been in use on Linux since ... early 1990's01:29
gnarfacedselect?01:29
* fluffywolf spots a furry!01:29
Afdalno01:29
* adhoc is a bit vague when it came in01:29
gnarfacewhich init, Afdal?01:30
Afdalsysvinit at the moment01:30
AfdalI wasn't given a choice01:30
gnarfacedid you have a graphical login thingy at any point?01:30
adhocAfdal: was this a debian system you moved over?01:30
Afdalomg no01:30
fluffywolfand here I thought I was the only devuan user with paws.  :P01:30
Afdalwhat's the name of the heckin installer01:30
adhocfluffywolf: that must make it hard to type01:30
Afdalit was the only installer I even saw01:31
fluffywolfit does!01:31
gnarfaceif that file is wrong then i suspect there might be other things wrong01:32
AfdalWhat's the name of the graphical installer01:32
Afdalon live images01:32
AfdalI can't even find that01:33
gnarfacelive images use refracta something or another01:33
AfdalI hate the modern wweb so much01:33
AfdalYeah it was that01:33
gnarfacerefractasnapshot01:33
AfdalI used that in terminal form01:33
gnarfaceor refractainstaller01:33
gnarfaceone of those01:33
gnarfacei think01:33
Afdalrefractainstaller, yeah01:33
gnarfacei don't know crap about it really01:34
Afdaland yeah there was a display manager but I set it to autologin so I never see it now01:34
Afdalit's the typical one used by Xfce01:34
Afdallightdm probably01:34
Afdalor maybe not01:35
gnarfacewell it matters whether it was refractasnapshot or refractainstaller, you should check the man pages for them01:35
Afdalit was refractainstaller01:36
gnarfacei think refractasnapshot would have mirrored the running livecd01:36
Afdalit was refractainstaller01:36
AfdalI remember the command I ran01:36
gnarfacei have to assume refractainstaller would need configuration01:36
gnarfacemaybe you missed a setting?01:36
Afdal@_@01:36
gnarfaceor maybe it sets this because you set autologin01:36
gnarfaceit might set it in both places01:37
gnarfaceif you set it in the gui, i dunno01:37
AfdalHow do I check which display manager I have installed without logging out01:37
gnarfacedpkg -l01:37
Afdal<.<01:37
gnarfaceif you have more than one you can see the default with the alternatives symlink stuff01:38
Afdal@_@01:39
gnarfacei think it's /etc/alternatives/x-session-manager01:39
gnarfaceor x-login-manager ?01:39
gnarfacesomething like that01:39
gnarfacei don't even have one installed01:39
gnarfacehave you considered using the normal netinstaller?01:39
AfdalWell I'm not reinstalling again now01:39
AfdalThe reason I used terminal based was because I had to install from an ssh01:39
gnarfacewell fyi for the future the regular installers are here: https://files.devuan.org/devuan_chimaera/installer-iso/01:40
gnarface(that's current stable)01:40
gnarfacefresh off the presses01:40
Afdaluhhh yeah01:40
Afdalit's probably lightdm01:42
Afdalseeing as I have a symlink to desktop-lightdm-background in here01:42
Afdalnope, guess not01:43
gnarfacemight be slim?01:43
Afdalthat's definitely installed01:43
Afdalmust be that01:43
gnarfacewell if you're not gonna use it you can just uninstall it01:43
AfdalEvery now and then I have a reason to log out ;o01:44
Afdallike switching window managers or whatever01:44
gnarfacenone of that actually requires slim01:44
Afdalwell certainly I -could- end an X session and go to terminal then start it all up manually01:45
Afdalbut uh <.<01:45
gnarfacestartx01:45
AfdalI like a nice little dropdown menu to choose my window manager/desktop environment session01:45
gnarfaceit's in the xinit package01:45
gnarfacei think it's still there anyway01:46
gnarfaceif it hasn't been chopped by vandals01:46
AfdalThen again maybe I like bein autologged into ttys when I switch to them01:56
AfdalI dunno, what are the security implications of that?01:57
Afdalparticularly on a machine with an ssh server running01:57
gnarfacei feel like it's a pretty apparent security concern01:58
adhocwith physical access, there is no secutiry01:59
adhocwith a user account, you have to assume someone can get root01:59
adhocthe box is therefore hosed.01:59
gnarfacewell, that's not always true around cats and young children01:59
gnarfacethere are layers of security and layers of threat01:59
Afdalyeah if someone is sitting at my machine it doesn't really matter02:07
Afdalbut do ttys pose any kind of thread from a remote session02:07
Neutr1noHow do I remove an script that startup at /etc/init.d/? I have moved the script to another directory but I want that it will removed from the init process02:07
Neutr1noAfdal: good morning02:07
Afdalh-hello02:08
Neutr1noAfdal: greetz from northern germany02:08
gnarfaceAfdal: well if the users gain the wrong permissions on the /dev/ node there's a theoretical possibility they could type stuff on your screen but they've already rooted the box at that point02:09
Afdalmaybe I'll just keep these convenient autologin'd ttys around then :)02:10
gnarfaceNeutr1no: there's a tool called sysv-rc-conf you can use or you could just delete the symlinks in /etc/rc?.d/02:10
Afdalsaves me a step when I have to run to a tty to kill a program or something02:11
gnarfaceyou should make sure to not allow remote root login with sshd... i have concerns about the sshd security level too02:12
Afdaloh definitely, I always have that disabled02:13
Afdalit should really be a default openssh setting02:14
Neutr1nognarface: thank you very much. Nice tool, Thx02:14
Neutr1nognarface: it works02:14
gnarfaceNeutr1no: no problem02:14
Neutr1no:-)02:17
Neutr1no302:18
Neutr1nois there also an tool available to configure source from the package manager?02:34
gnarfacelike automake?02:38
gnarfacewhat do you mean by source? like kernel sources or program sources or apt sources?02:39
u-amarsh04like apt-get build-dep ?02:40
Neutr1noI add an source to /etc/apt/source.list by editing this file. But this source is broken, I want remove it without doing it manualy by editing the file02:42
gnarfacehmm, i actually don't know of any gui tools for that02:42
gnarfacethere's a gui package manager called synaptic, i don't know if it can manage sources too02:43
Neutr1nognarface: thanks02:43
Neutr1noone last question. Is there an good email client with an nice textmode / ncurses gui?02:44
gnarfaceeveryone uses mutt for that i think02:45
onefangOr neomutt.02:47
onefangSynaptic can manage sources.02:47
onefangIn ASCII "mutt" was a renamed neomutt, but in Beowulf it's called neomutt again.  Blame Debian.02:48
gnarfacethere's always emacs post-el too02:50
Neutr1noyou are best. Thanks for your support.02:54
* Neutr1no love the shell and want learn more about unix/linux (bash an textmode shells)03:00
gnarfacehooraaay! we're the best03:03
gnarfacebest way to start is read the man pages03:04
gnarfacebash has a man page too03:04
gnarface(though with bash, the bash-doc package or the online help at gnu.org might be a better place to start)03:05
gnarfacemost the important command-line programs will have a decent man page for reference, the complex stuff often has a *-doc package to accompany it03:06
gnarfacealso typically packages will put some docs in /usr/share/doc/[package name]03:07
gnarfacethough with a lot of packages, all that's in there is boilerplate copyright stuff03:08
Neutr1nognarface: reading RFC's are interested, to. but man and RFC's are very complex and long. My english is not so good and I don't have enough time for that at the moment03:16
Neutrino-can someone help with the configuration from the fvwm window manager?08:15
gnarfaceNeutrino-: i don't know fvwm but it would help someone who does if you lead with what you're trying to accomplish, and what you've tried so far08:24
Neutrino-gnarface: I figured it out by myself just in this moment, it works08:25
Neutrino-gnarface: thnx08:25
gnarfacenp08:26
Neutrino-what is the name from the gui based fvwm theme selector?08:54
chomwittshould  apt-cache search --names-only "^ff.*"  display sffw2 amont the results?09:53
chomwitti think it search 'package names' and not THE package names, which means apt-cache searches also fields like 'Provides' etc10:01
chomwitts/THE package names/THE package name10:02
chomwittbut 'Provides' some times have package names like librust-pango-sys+default-dev that dont look searchable by apt-cache search11:01
chomwittxmm,, so it searches Package names in Provides field but not virtual ones11:17
fsmithredAfdal, did you figure out how to disable autologin?13:18
fsmithredcp /usr/lib/refractainstaller/inittab.debian /etc/inittab13:18
fsmithredthat will get rid of console autologin.13:19
AfdalWhat's the smartest way to run old software that depends on a software library version no longer in the current repository...19:37
AfdalSome kind of container?19:37
gnarfaceif the running kernel is still compatible, you can run it and the whole release version it was from in a chroot19:49
gnarfaceor even just a frankenstein install of mishmashed library versions would work too19:49
gnarfacesince the chroot can be basically disposed of without affecting the parent system19:50
gnarfaceif there's kernel incompatibility too you might need qemu19:50
gnarfaceif it's literally just one library and there's no other dependencies you could also just force the program to load it from a side directory with LD_PRELOAD19:51
gnarface(that's assuming you have a way to get it there without corrupting the package tree)19:51
AfdalI'm not even sure how to get the library actually I:'}19:52
gnarfacedo you know what version and what its name is?19:54
Afdalon a different distro19:54
AfdalI think it's libjpeg819:54
Afdalbut it seems Debian/Devuan has dropped or never used the number distinction at the end19:54
gnarfacechecking...19:55
AfdalDoes Canonical always use the game package names as Debian or do they have their own shenanigans?19:56
Afdalsame*19:56
gnarfaceit was in ceres recently, libjpeg8-dev and libjpeg8-dbg still are, but it looks like they're moving to libjpeg919:56
gnarfacethis doesn't seem to be a package name difference, it's merely time19:56
gnarfaceyou're too late, you just missed it19:56
gnarfaceit might still be in the debian snapshot repos... snapshots.debian.org19:56
gnarfaceor you could see if it works with libjpeg9 instead19:57
Afdalit doesn't19:57
Afdalit's looking for something specifically with an 8 in it19:57
gnarfaceoh, bummer19:57
Afdalshared libraries: libjpeg.so.819:57
gnarfacewell19:57
gnarfacethis would be dirty but you could try symlinking to that from libjpeg919:58
gnarfaceor from that to libjpeg9 i mean19:58
Afdalo:19:58
gnarfacesometimes that works19:58
Afdalwhere are library names usually located?19:58
gnarfacerun this: dpkg -L [package name]19:58
gnarfacethey're typically in /usr/lib/ or /usr/lib/[something arch and distro specific]19:59
Afdalactually, uh19:59
gnarfacefor exampel /usr/lib/x86_64-linux-gnu/19:59
Afdalwait...  why is bare libjpeg not in the Chimaera repo?19:59
Afdalthere's only libjpeg-dev19:59
gnarfaceyour search pattern is wrong, chimaera is on libjpeg6220:00
Afdalwell, there's libjpeg62-turbo20:00
gnarfacehttps://pkginfo.devuan.org/cgi-bin/policy-query.html?c=package&q=%5Elibjpeg.*&x=submit20:00
Afdalis that's the de facto standard lijpeg now?20:00
gnarfacelooks like it20:01
Afdalconfusing20:01
gnarfacelooks like ceres skipped over 7 and 820:01
gnarfacewell, not skipped over but left behind20:01
gnarfaceand neither made it into stable before the cut20:01
Afdaldpkg-query: error: --listfiles needs a valid package name but 'libjpeg62-turbo' is not: ambiguous package name 'libjpeg62-turbo' with more than one installed instance20:02
Afdaloof20:02
gnarfacethat doesn't seem right20:02
gnarfacedo you have multi-arch enabled?20:02
Afdalyes20:02
gnarfacedo you have libjpeg62-turbo for two arches?20:02
Afdaldo I need to designate x86-64 somewhere20:02
AfdalI'm gonna guess probably20:03
gnarfaceit seems to be able to stay installed concurrently with libjpeg820:03
gnarfaceoh, sorry, didn't realize that was a question: dpkg -L libjpeg62-turbo:amd6420:08
gnarfacepackage names won't include symlinks, so this is better: ls -l /usr/lib/x86_64-linux-gnu/libjpeg.*20:09
gnarfaceif you're on ceres i'd just install the old one quick before its gone from snapshots20:10
Afdalhow do I do that20:11
Afdal(I'm on Chimaera)20:12
Afdalso is it /usr/lib/x86_64-linux-gnu/libjpeg.so.62.3.0 or /usr/lib/x86_64-linux-gnu/libjpeg.so.62 that I want to try symlinking20:12
Afdaloh those are only version differences20:13
gnarfaceif you used "ls -l" you can clearly see that libjpeg.so and libjpeg.62 are both symlinks to libjpeg.so.62.3.020:13
gnarfaceso in this case you'd want to try symlinking libjpeg8 to libjpeg.so.62.3.0 as well20:14
Afdalah, that's silly20:14
gnarfacebut i think that going backwards is less likely to work than going forwards20:14
gnarfacei think it would be more likely to work with libjpeg9 than libjpeg62 but it probably won't hurt to try anyway20:14
gnarfaceyou'd be better off getting libjpeg8 on here20:15
gnarfaceeither from snapshots or by building the source package if still possible20:15
Afdalso... ls -s /usr/lib/x86_64-linux-gnu/libjpeg.so.62.3.0 /usr/lib/x86_64-linux-gnu/libjpeg.so.820:15
Afdal?20:15
Afdalerr, ln*20:15
gnarfaceyea20:16
gnarfacethen run "ldconfig" once as root and try the program again20:16
Afdal /usr/lib/x86_64-linux-gnu/libjpeg.so.8: version `LIBJPEG_8.0' not found20:16
Afdallol, dangit20:16
gnarfaceyea, worth a try20:16
gnarfaceusually it doesn't work that way20:16
Afdalthen it's not gonna work with lijpeg9 either20:17
gnarfacesee, there's two dependencies, package dependences and runtime dependencies20:17
gnarfacesometimes the package dependencies are too specific and programs will work with other packages20:17
gnarfacebut usually newer versions, rather than older20:17
Afdalso how do I grab something from this "snapshots" kajigger20:17
Afdalactually, wait20:17
gnarfaceif it's actually specifically checking for LIBJPEG_8.0 symbol maybe that's the only one it'll work with20:18
gnarfacebut that would be weird in and of itself20:18
gnarfacewtf program is this anyway?20:18
AfdalCould I just grab the libjpeg8 from another system partition?20:18
Afdalyeah...20:18
Afdalit's MAME20:18
gnarfaceif you still have it installed elsewhere, sure20:18
gnarfaceoh, you can probably build mame against any libjpeg version20:18
gnarfacei guess i haven't tried in a while so i don't know for sure20:19
Afdalbuilding mame is so complicated -_20:19
Afdal-_-20:19
gnarfaceinstructions are on snapshots.debian.org20:19
Afdaland I dunno how I would build an older version20:19
Afdalso would that just be a ./configure flag then20:19
gnarfacebasically you just add the snapshot repo for a day when it was last seen in the repo, install just that one package, then remove the snapshot repo from your sources again20:19
gnarfacealthough, that would be for a release it was actually inlike ceres20:20
gnarface(sid)20:20
gnarfacehmmm20:20
gnarfaceheh20:20
gnarfaceyea just copy it from another partition into your mame directory and run it like LD_PRELOAD="./libjpeg8.so" mame20:21
gnarfacethat would work too20:21
gnarfacecleanest way would be to build the source package for yourself for chimaera but i have a strong suspicion it won't build right and that's why we're having this discussion in the first place20:21
Afdalokay so how do I export an installed package into a .deb20:21
Afdalso I don't have to copy a zillion directories20:21
gnarfaceyou probably just need that one lib file in your home dir tbh20:22
gnarfacesince nothing else is gonna use it20:22
Afdalhmm20:22
gnarfacecheck to see if the package is still in /var/cache/apt/archives there20:22
gnarfaceif it was installed recently it might still be there20:22
Afdalnaw20:23
gnarfacei forget how to export an installed package back to a deb, i can't remember if there's a way to do that20:23
gnarfacebut seriously, just try copying that one library over and pointing mame to it directly with the LD_PRELOAD environment variable.  it might not need anything else20:24
gnarfaceand it might not need to be in a particular location20:24
AfdalThis is probably what I wanna grab right: /usr/lib/x86_64-linux-gnu/libjpeg.so.8.1.220:25
gnarfacei vaguely recall struggling with this on something some years ago and finding out that the refusal to work with libjpeg62 turned out to be a bug20:25
gnarfaceprobably yea20:25
Afdalokay so expltain to me this LD_PRELOAD variable20:26
AfdalThese sorts of headaches make me seriously want to build appimages for old software when I want to hang on to some particular version20:27
AfdalSometimes I think the library dependency system of loonix is more trouble than it's worth...20:29
gnarfaceLD_PRELOAD just forces it to load whatever library you tell it first, preempting the LD_LIBRARY_PATH20:29
AfdalYeah but how do I use it?20:29
gnarfacei literally typed the command to you20:29
Afdalhmm?20:29
gnarfaceLD_PRELOAD="./libjpeg.so.8.1.2" mame20:29
Afdaloh, ah20:29
Afdalh-here I go :320:29
gnarfaceif only this one program needs it, there's no reason to put it in the global environment20:29
gnarfacechances are they removed it because it's cursed anyway20:30
Afdaluhhh hmm this is a stupid question20:30
gnarface?20:30
Afdalhow do I ./run a binary when it's prefaced with something else first20:31
Afdalin bash20:31
gnarfacewhat do you mean?20:31
AfdalLD_PRELOAD="/home/afdal/oldpackages/libjpeg.so.8.1.2" ./mame20:31
Afdalthat just loads up my currently installed mame20:31
Afdalinstead of the old binary I want to run20:31
gnarfacewell it can be /usr/bin/mame too or whatever20:31
gnarfaceboth those fields can take full paths20:32
Afdaloh rite20:32
Afdaloof that just keeps running my current install20:32
Afdalwhat's up with that...20:32
gnarfacewell which mame are you trying to run?  i'm not sure even what the confusion is20:33
AfdalI'm trying to run an old version on a previous distro20:33
Afdalfrom* a previous distro20:33
gnarfaceLD_PRELOAD="/home/afdal/oldpackages/libjpeg.so.8.1.2" /path/to/wherever/mame20:33
Afdalyeah when I do that it just loads up the current mame installation20:34
Afdalhow do I make bash stop misbehaving I:20:34
gnarfaceit doesn't though20:34
Afdalbut it does tho {:I20:34
gnarfaceit'll definitely load whatever mame binary you point to, but you might be getting confused because that mame binary is going to still default to using the current user's mame configs in ~/20:34
gnarfacewhich you'd have to correct with mame configs i don't remember off the top of my head20:35
gnarfacebut i'm sure it can be set20:35
AfdalI don't think I'm running a symlinked binary...20:35
gnarfaceeven if you're running mame from a partition that was not used by the current distro but used by an old distro, that mame version is still going to use the current user's home directory and all configs20:36
Afdalyeah but it's not like the ~/.mame config tells mame which binary to use20:36
Afdalas evidenced when I try to run ./blah/blah/blah/mame I get thrown that libjpeg8 error20:36
gnarfacehmmm20:37
gnarfacenah we're misdiagnosing something here20:37
gnarfacethe ~/.mame does tell it where the highscores and roms are stored, iirc20:37
Afdal /media/afdal/e099a547-8781-4ef4-afed-326743586a28/usr/games/mame is definitely the right binary20:37
Afdalthat I'm trying to run20:38
AfdalI think this is just a bash syntax issue20:38
Afdalwhat's the trick tho20:38
gnarfacei can't imagine what's going wrong at this point, that should have worked20:39
gnarfaceit did used to work on that install?20:39
Afdalabsolutely20:39
Afdalbash just keeps trying to execute the binary it's normally expecting when you run a bare "mame" command instead of the specific binary I want by telling it the right path20:40
gnarfacewith the full path that shouldn't happen20:40
gnarfaceyou sure it's not actually a symlink or some wrapper script itself?20:41
Afdalnope, not a symlink or script20:41
Afdalit's the whole 250MB whale20:41
Afdal310*20:41
gnarfacewhat if you also set LD_LIBRARY_PATH="/home/afdal/oldpackages:$LD_LIBRARY_PATH"  ?20:42
gnarfacei would try chrooting into the old install to see if it still runs from there20:44
gnarfaceif the old instasll is still intact20:44
Afdallook the issue is bash tries to load up something else when I end any of those ld variable sets with the path to the executable I want to run20:45
AfdalShould I just uninstall my current mame installation...20:45
Afdalugh20:45
gnarfacenah i wouldn't do anything hasty yet till you figure out what's going wrong20:45
Afdalhow do we tell bash to stop being retarded20:46
gnarfacewe seem to be overlooking something important, bash is not smart enough to be retarded20:46
Afdalmaybe I should export these variables to globals first and then run the executable command separately20:46
Afdallolwuttheheck20:47
gnarfacedo you have the "locate" package installed?20:47
AfdalI tried that and now even a bare "./mame" command makes bash open my current installed binary~20:47
Afdalwhat is going on with this goofy system20:47
Afdalokay so it wasn't a syntax issue20:48
Afdaland this is clearly not a symlink I'm trying to run20:48
Afdalyeah I have locate20:48
gnarfacelocate could misbehave this way, that's why i stopped using it20:49
gnarfaceit does path caching20:49
gnarfacethere's a command to flush it... updatedb or something?20:50
gnarfacei forget20:50
Afdalthis is so bizarre20:50
Afdalwhy would fixing the library dependency error of an old binary then make that binary point to a new one somewhere else20:50
AfdalMaybe the smart move is just to run old program versions in containers -_-20:52
AfdalEven symlinking my old libjpeg to /usr/lib/x86_64-linux-gnu/libjpeg.so.8 produces the same behavior20:54
gnarfacesorry, libera lagged me out there, if you said anything after my response at 11:49 Afdal, i missed it21:00
Afdal<Afdal> this is so bizarre21:03
Afdal<Afdal> why would fixing the library dependency error of an old binary then make that binary point to a new one somewhere else21:03
Afdal<Afdal> Maybe the smart move is just to run old program versions in containers -_-21:03
Afdal<Afdal> Even symlinking my old libjpeg to /usr/lib/x86_64-linux-gnu/libjpeg.so.8 produces the same behavior21:03
gnarfacei think there's an important key we're overlooking21:03
gnarfacelike you're ssh'd into a completely different machine or something21:03
gnarfacei dunno i'm out of ideas21:04
gnarfacesomething should have budged21:04
gnarfacei don't know if it would have worked but it should have at least changed behavior21:04
gnarfacei agree that maybe containers are the smarter way to go but this problem seems low enough level it could affect everything21:04
gnarfacea fresh build of mame might be in order21:06
gnarfacebut i think retracing your steps might turn something up too, some simple mistake or oversight21:06
rwpI read just a little bit of the scrollback and I read very unusual stuff being debugged.21:08
rwpTrying to override libjpeg with a different version?  I can't imagine why.21:09
rwpBut if one wants to debug the dynamic loader then something like this might be helpful.21:09
rwpenv LD_TRACE_PRELINKING=1 /lib/x86_64-linux-gnu/ld-2.31.so --list /bin/cat21:09
rwpReplace with the appropriate things you are actually using.  But it will show the libs that are getting linked in and what symbols are doing it.21:09
rwpThere is also just plain old: /lib/x86_64-linux-gnu/ld-2.31.so --list /bin/cat21:10
rwpThe /lib/x86_64-linux-gnu/ld-2.31.so is otherwise known as "ld.so" and the "man ld.so" documents it.21:10
Afdalnaw I'm not debugging anything, just trying to run an old version of a program that requires libjpeg821:11
rwpThere is also "ldconfig -v" which sets up the /etc/ld.so.cache too.21:12
AfdalI dunno what you just said @_@21:12
rwpWhat is the name of the package with the old shared library you need?21:15
rwpIs it possible to simply pull it out of snapshot.debian.net and install it?  That would be the simplest way forward.21:15
rwp(Sorry but I have not read the scroll back buffer in detail about what was previously tried.)21:15
gnarfaceAfdal: can you try it again with LD_PRELOAD and full paths but without located running please?21:15
Afdaluhh how do I stop locate from running?21:15
Afdalis that a system service21:16
gnarface /etc/init.d/located stop21:16
gnarfacei think21:16
gnarfaceshould be a system service yes21:16
AfdalI'll give it a go...21:16
Afdalhmm that doesn't exist21:16
Afdal /etc/init.d/located21:16
rwpIf the library package has a version'd name, as it ought to have, then multiple versions can co-exist.  If not then it's a problem and you will need a chroot or something.21:16
gnarfacehow about just /etc/init.d/locaate ?21:16
Afdalnope21:16
gnarfacedpkg -L locate?21:17
rwpLocate runs from cron.  It's started from cron not init.21:17
gnarfaceoh21:17
gnarfacei would just honestly uninstall it21:17
rwpIt's probably /etc/cron.daily/locate that starts it.21:17
rwpThere are at least three different packages that implement locate-like functionality.  All derived from each other.  So it may be mlocate or one of the others too.21:18
AfdalI'm not even sure what locate does, what's it's purpose?21:18
gnarfacehmmm21:18
AfdalThis was automatically installed on my Devuan installation21:18
rwp"locate" is a fast find of every file on the file system.  By working off of a pre-compiled database of every file on the file system.21:18
gnarfaceyea but if you have two rootfses mounted in parallel with conflicting mame versions it might not be smart enough to handle that well21:19
rwpI don't think locate is part of the default set that is installed.  But with Recommends being what they are if Recommends is not burned out with fire then a lot of cruft gets installed.21:19
rwpPersonally I use locate to find a file or three at least once every other day.  It's very useful to me.  I use it.21:20
rwpBut of course if you don't use it then it has no use for you and it would be better to remove it.21:21
AfdalI use uh21:21
Afdalwhatever Catfish depends on21:21
rwpI happen to know that Linode at least has a customization that disables locate at boot time.  The customer can enable it again though.21:21
AfdalI don't think it's locate21:21
rwpThat's it.  catfish: "Recommends: mlocate | locate"21:22
Afdalo rly21:22
rwpWhich means you probably have the "mlocate" version installed.  It's a modified fork of "locate".21:23
rwpTo demonstrate the use of it "locate libjpeg.so" would locate and print out every file on the system with that name in it.21:24
AfdalI don't even know why this is relevant.  Does bash use locate to index binaries in the background or something?21:25
rwpNo.21:25
rwpIt's relevant because you said, "I'm not even sure what locate does, what's it's purpose?"  You asked.21:25
gnarfacedoesn't it?  i'm pretty sure this is why i stopped using locate over 2 decades ago21:25
Afdalo:21:25
rwpgnarface, Doesn't it what?  I missed the context link there.21:26
AfdalI thought all that stuff happened in some bash config file somewhere21:26
Afdalis it .bashrc21:26
Afdalno...21:26
rwpbash is your command shell.  Full stop.  How is it related to locate?21:26
Afdal@_@21:26
gnarfacerwp: the primary symptom is that if he runs /media/afdal/e099a547-8781-4ef4-afed-326743586a28/usr/games/mame it is still giving him /usr/games/mame no matter what21:27
Afdalisn't it like... when you "install" something it adds a location alias to bash so you can just call the name of the program without adding all that directory fluff21:27
gnarfacerwp: i suspect a possible misdiagnosis too but locate was definitely associated with these type of gremlins for me a long time ago21:28
Afdalall right well lemme try uninstalling it for a sec21:29
Afdalhopefully nothing breaks21:29
gnarfacei've never run into anything that actually needs it or any situation where it was actually notably beneficial21:29
rwpOkay.  I think you are thinking of the shell's internal hashing.  Try "type foo" to see shell tracked aliases.  Try "hash -r" to rehash it, flushing all past knowledge of the commend.21:29
Afdaland yeah, mlocate is the version I have installed21:29
rwpIn this case, "type mame" I guess is what you would ask it.21:30
gnarfacewas there also a daemon in redhat a long time ago called located?  could i be confusing this locate with something else?21:30
AfdalNope, uninstalling mlocate didn't resolve it...21:30
rwpMaybe.  I don't know.  There are several different forks and mutations of the locate task.21:30
gnarfaceAfdal: what if you just log all the way out and back in?21:31
Afdaltype mame21:31
Afdalmame is /usr/games/mame21:31
rwpBut let me assure you that locate, mlocate, or other locate, has nothing to do with PATH and bash running a particular program or other.  Totally separate.21:31
Afdallol why would that do anything21:31
AfdalClearing environmental variables or something?21:31
gnarfaceAfdal: maybe environment variable corruption from hand testing? yea21:31
rwpAfdal, Try "hash -r" to flush the cache.  Then try "type mame" again.  And what is PATH?  echo $PATH21:31
Afdalmame is /usr/games/mame21:32
Afdalecho $PATH21:32
Afdal /home/afdal/bin:/home/afdal/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games21:32
rwpI always have "shopt -s checkhash" set in my ~/.bashrc file too. "checkhash -- If set, bash checks that a command found in the hash table exists before trying to execute it.  If a hashed command no longer exists, a normal path search is performed."21:33
rwpAfdal, So there you go.  It's PATH.  You have path set including /usr/games and so it finds /usr/games/mame from PATH.21:33
gnarfaceyea but if he called the other binary with the full path prefix that shouldn't matter21:33
Afdaluh yes, but that's what should happen when I call "mame"21:33
Afdalwhat shouldn't be happening is that when I do a full directory path ^21:34
AfdalWonder if I can reproduce this with some other program21:34
rwpCalling a program by the full path should not cause a tracked alias to be created for it.21:35
Afdali know rite21:35
rwpSo is /media/afdal/e099a547-8781-4ef4-afed-326743586a28 actually a full OS being mounted there?  And you want the mame from there to use the libs from there?21:37
Afdalyes to both21:37
AfdalI've got the library issue resolved, so I think21:37
rwpOkay.  Then that's certainly possible.  Have done that many times for other programs.  Let me type in a long command line.21:37
AfdalI just wanna get that old binary to run on my current Duvuan environment21:38
gnarfacerwp: incident started because it refused to run against any libjpeg other than libjpeg8 which seems to have just been recently removed21:38
Afdalyou're not gonna tell me to chroot are you...21:38
rwpTry: /lib/x86_64-linux-gnu/ld-2.31.so --library-path /media/afdal/e099a547-8781-4ef4-afed-326743586a28/lib:/media/afdal/e099a547-8781-4ef4-afed-326743586a28/usr/lib /media/afdal/e099a547-8781-4ef4-afed-326743586a28/usr/games/mame21:39
rwpAssuming that you are running an amd64 arch system.  No chroot required.21:40
rwpThat tells the ld.so to use the library path for that OS for running that executable.21:40
Afdalwhat even is ld.so21:40
Afdal /lib/x86_64-linux-gnu/ld-2.31.so --library-path /media/afdal/e099a547-8781-4ef4-afed-326743586a28/lib:/media/afdal/e099a547-8781-4ef4-afed-326743586a28/usr/lib /media/afdal/e099a547-8781-4ef4-afed-326743586a28/usr/games/mame21:41
gnarfacethe linking library21:41
Afdal /media/afdal/e099a547-8781-4ef4-afed-326743586a28/usr/games/mame: error while loading shared libraries: libjpeg.so.8: cannot open shared object file: No such file or directory21:41
rwpThe /lib/x86_64-linux-gnu/ld-2.31.so is the ld.so dynamic linker.  It's what links in libraries to programs.21:41
AfdalIs that any different from the LD_PRELOAD trick21:42
rwpIf that is the error then I don't think it exists in that system directory either.21:42
rwpIt's similar to the LD_PRELOAD trick.  But it loads *everything* from that location rather than cherry picking.21:42
gnarfaceprobably /media/afdal/e099a547-8781-4ef4-afed-326743586a28/lib:/media/afdal/e099a547-8781-4ef4-afed-326743586a28/usr/lib/x86_64-linux-gnu, no?21:42
rwpIt's a way to run RHEL binaries on Devuan for example.  And so forth.  That's mostly how I have used in the past.21:43
Afdalyeah, need the x86_64-linux-gnu bit21:43
rwpWhat does this say: file /media/afdal/e099a547-8781-4ef4-afed-326743586a28/usr/games/mame21:43
Afdal /media/afdal/e099a547-8781-4ef4-afed-326743586a28/usr/games/mame: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=de8f998a127c0b6f8c2d3e1016a04128ae1cb0a0, stripped21:44
Afdalafdal@devuan-desktop:/media/a21:44
rwpIt's a 64-bit amd64 binary.  So that okay, right?21:44
gnarfaceshould be right21:44
Afdalinteresting, progress perhaps: error while loading shared libraries: libpulsecommon-11.1.so: cannot open shared object file: No such file or directory21:44
Afdalso there's another dependency I need to fix first21:44
gnarfaceah ha21:44
gnarfaceprogress!21:45
gnarfaceneeat trick with this   /lib/x86_64-linux-gnu/ld-2.31.so --library-path thing, never seen that rwp21:45
* gnarface didn't even realize that was an executable 21:45
rwpSomething is still not feeling consistent here.  Because if that OS tree had those things installed then it should be there.  And if it not there then something is not consistent.21:45
* gnarface would have already rebuilt mame by now21:46
Afdaloh... wait21:46
Afdalwait21:46
Afdalhol up21:46
gnarfaceget the paths right, i made a mistake21:46
rwpgnarface, We would get RHEL binaries of CAD/EDA programs and I would repackage them to run on our Debian systems using that technique.21:46
AfdalI just realized something embarrassing21:46
gnarfacelooking at the wrong directory?21:46
AfdalThis hasn't been loading the same binaries after all21:46
* gnarface facepalm21:47
* gnarface had that suspicion21:47
AfdalUgh, well crap21:47
Afdalso uh21:47
gnarfacewait does it run though?21:47
Afdalwell this raises even more confusing questions21:47
Afdalapparently the mame binary on my old *buntu installation was NEWER than the one just upgraded to on Chimaera21:47
gnarfacenot surprising21:48
rwpgnarface, Using bash's exec -a option allows creating a script so that ps even shows the correct name running if it is all wrapped up.21:48
Afdalwhich is hilarious and baffling before that was only 18.0421:48
gnarfacethat's just how ubuntu is, they're bleeding-edge21:48
Afdalnot typically when it comes to emulators21:48
AfdalSo uh one of the main reasons I decided to try out Devuan recently is21:48
gnarfacehere's the thing though, this: /media/afdal/e099a547-8781-4ef4-afed-326743586a28/lib:/media/afdal/e099a547-8781-4ef4-afed-326743586a28/usr/lib21:49
AfdalI -just- upgraded my 16.04 *buntu to 18.0421:49
Afdaland created a situation where I can't boot anymore21:49
gnarfacewould actually have to be this: /media/afdal/e099a547-8781-4ef4-afed-326743586a28/lib:/media/afdal/e099a547-8781-4ef4-afed-326743586a28/usr/lib:/media/afdal/e099a547-8781-4ef4-afed-326743586a28/usr/lib/x86_64-linux-gnu21:49
rwpNote that the installer iso is a good rescue boot system if you need it.21:49
AfdalI have no idea why this newer build of mame would be using this ancient libjpeg8 library21:50
rwpgnarface, That's a good modification if that is the correct list of directories.21:50
Afdaltaht's so weird21:50
gnarfacei don't know for sure you wouldn't need i386-linux-gnu in there too.  for Steam or Wine stuff you often would21:50
AfdalWell, in any event, damnit, this means this isn't the version of MAME that I'm looking for and I probably have to compile it to use it again after all >:/21:50
rwpAfdal, When a developer compiles a package and uploads it the program running is the binary built on their system.  Which may be using an old library.21:50
rwpIt's the main reason there is a push for source only uploads.21:50
Afdalunless...21:51
rwpBecause otherwise the main arch by the developer is from their own system.  Meanwhile all of the other arch's are from the build systems.21:51
AfdalI can just grab a .deb from an old *buntu repository21:51
gnarfacecheck if mame is in backports first21:51
Afdalhow do I do that again21:51
gnarfacenevermind, doesn't look like it is21:52
Afdallol21:52
rwpI am with gnarface in that it is probably time to build the mame you want from source.  Probably not that difficult.21:52
Afdalmame is a -gigantic- piece of software21:52
rwpFirst start with "apt-get build-dep mame" to install the build dependencies.21:52
AfdalI'm really hesitant to compile it...21:52
gnarfacei've built it on a raspberry pi model B21:53
AfdalThis is really surprising, the *buntu 18.04 build updated MAME all the way up to a build from August this year.  Normally MAME builds on *buntu are absolutely ancient21:53
rwpWell...  There is that.  Even my 16GB system struggles with 0AD for example.21:53
Jjp137eh the dependencies don't look that bad? https://docs.mamedev.org/initialsetup/compilingmame.html#debian-and-ubuntu-including-raspberry-pi-and-odroid-devices21:53
AfdalMeanwhile Chimaera is on MAME from last January :v21:53
rwpDid you perhaps have an Ubuntu PPA in your sources for something?21:53
AfdalNo?21:54
Afdaleveryone says that's a terrible idea21:54
Afdaloh you mean the sources of the the old system21:54
gnarfaceit is but ubuntu people might have talked you into it for the ubuntu install21:54
Afdalyeah that might have been it21:54
AfdalAhem, well... at least with compiling I'll be able to specify exactly the libraries I want and even make an appimage or whatever so I never have to deal with dependency hell again21:55
gnarfacethat's the idea21:55
gnarfacealso, it gets easier every time21:56
Afdalcompiling from git diffs maybe21:57
AfdalI'm expecting a huge headache compiling an old build -_-21:57
gnarfacewell if you're not actually running this on an ARM SoC i doubt you need any special patches or versions21:58
AfdalAt least the MAME project keeps around source archives for old versions21:58
Afdalthank god for that21:58
rwpGood luck with everything!  I am dropping offline again for a while...21:58
Afdalthanks for the educational experience -_-21:59
gnarfaceany time21:59
Afdalhmm you know what, I do have a ppa .deb that's close to the version I'd like to use22:00
Afdalhow do I install a package of another version alongside a different one again...22:01
gnarfacetheir own dependencies probably prohibit that22:01
gnarfaceit'd have to be coded to share paths safely22:01
Afdalactually that's a .deb made for Trusty, maybe I'd better not mess with something -that- old22:01
gnarfacechimaera should match current debian stable for build deps22:01
Afdalcan't I just like22:02
Afdalgrab the binary from a .dev archive22:02
gnarface... use the version currently in chimaera?22:02
Afdal.deb archive*22:02
gnarfacecurious why you needed libjpeg8 tbh22:02
Afdalfor that other binary compiled for *buntu22:03
gnarfacei never asked what's wrong with the existing version built against the existing libjpeg22:03
gnarfacei just sorta assumed you had a problem with it22:03
gnarfacethere's a version in the chimaera repos that should still work22:03
Afdalversion of what22:03
gnarfacemame22:03
Afdalit's probably not the version I'm interested in22:03
Afdalwhat version?22:03
gnarfacehttps://pkginfo.devuan.org/cgi-bin/policy-query.html?c=package&q=%5Emame%24&x=submit22:04
gnarfacelooks like 0.228 right now22:04
Afdalyeah that's far too new22:04
gnarfacewith some debian pacakges22:04
AfdalI want v0.160 or something close to it22:04
gnarfaceyou sure it matters?22:04
AfdalYeah, so uh22:04
Afdalthe whole reason I'm doing this22:05
Afdalis I have some input replay files I need to view again/dump to video22:05
Afdalthat don't work on newer builds of MAME22:05
gnarfaceoh i see22:05
gnarfacethey're not in a format ffmpeg can handle directly?22:05
Afdalno they're MAME .inp files22:05
Afdalit's a series of player inputs tracked by time that you need the emulator to interpret22:06
gnarfacei see22:06
gnarfacedamn22:07
AfdalYeah the v0.154 in the jessie repo is close but I think when you go backwards the input files never work that way22:07
AfdalSo I guess I'm gonna have to compile this22:07
gnarface0.160 source is still available from mame's site?22:07
Afdalyup22:07
AfdalI just grabbed it22:07
Afdalhttps://www.mamedev.org/oldrel.html22:07
gnarfaceget the build-deps for chimaera mame first and it might just work22:07
gnarface"apt-get build-dep mame"22:08
Afdalthey've got em all even going back to 199722:08
gnarfacealso probably apt-get build-essential22:08
AfdalI just realized there are kids these days who are younger than the MAME project #whoa #wow22:08
eyalrozHello channel denizens... I was wondering if it's possible to install (packaged) GCC 7 or GCC 8 on Devuan Chimaera. I'd like to avoid going to the trouble of building it from source...22:09
gnarfaceyou're probably better off running that in a chroot than integrating it into chimaera, eyalroz22:11
eyalroz@gnarface: Really? I mean, gcc-9 and gcc-10 seem to coexist nicely22:11
gnarfaceeyalroz: last seen in beowulf, so i assume it was pulled for a reason22:12
eyalrozwhy not gcc-7 following the same scheme of directory and file naming?22:12
gnarfacei don't know, i've seen 7 and 8 both come and go through ceres22:12
gnarfacei just assume you're going to run into a conflict with libc6 major version changes22:13
gnarfacei could be wrong22:13
gnarfacebut since it's just for building other things it might not be worth the struggle when you can just debootstrap beowulf into a chroot22:13
gnarfaceif you upgraded through beowulf to chimaera, it would have stayed installed if there wasn't a runtime conflict22:14
gnarfaceor rather, if there wasn't an anticipated runtime conflict that was blocked with package dependencies, that is22:14
eyalrozgnarface: I have actually never tried debootstrapping (into a chroot or otherwise)...22:15
gnarfacewell technically you just debootstrap into a directory and chroot into that directory afterwards22:16
gnarfacetry this: debootstrap beowulf ./ https://deb.devuan.org/merged22:18
gnarfaceor something like that22:19
gnarface(in a spare empty directory)_22:19
gnarfacei forget if you need the /merged part22:19
gnarfacei think you do22:19
Afdalthat's one long build-dep list...22:20
gnarfaceAfdal: one of the reasons i recommend doing stuff like this in a chroot is to not pollute your main install with all those deps22:20
Afdalhmm this old version doesn't even have a configure script22:20
Afdallol too late22:20
gnarfacejust a make file?22:21
Afdalyeah22:21
AfdalThis could get ugly...22:21
gnarfacei don't recall any real problems building it.  the raspberry pi build never ran well but it ran22:21
AfdalI need to learn how to make appimages already22:22
eyalrozgnarface: I'll try it, will see what happens.22:22
gnarfaceAfdal: install checkinstall, and when you finish building it you can auto-package it with "checkinstall make install"22:23
Afdalyeah I know about checkinstall22:23
Afdalbut that's just a deb22:23
gnarfacewell it helps for cleanup later if you have to do it again22:24
AfdalI need it self-contained so I don't have to deal with library problems in the future22:24
gnarfacethe deb checkinstall makes won't enforce any dependencies unless you tell it to explicitly22:24
Afdalo rly22:24
AfdalI never knew that...22:24
eyalrozgnarface: I tried debootstrap'ing, and gort: E: Failed getting release file https://deb.devuan.org/merged/dists/beowulf/Release22:24
gnarfaceAfdal: the binary itself might be a different matter... you should check the READMES22:25
eyalrozs/gort/got22:25
AfdalWell then what the heck do we need appimages/snaps/whatever for?22:25
gnarfaceAfdal: we don't need them, they're harmful22:26
Afdal:o22:26
gnarfaceeyalroz: try it without https22:27
gnarfaceeyalroz: sorry about that, the mirrors in the round-robin mostly don't support https by the round-robin's domain name22:28
eyalrozgnarface: NP, that seems to be doing stuff.22:28
eyalrozLet's see what ends faster - debootstrap'ing or building GCC-8.5.0 (I went for a somewhat newer version).22:29
AfdalWell that was fast, I already feel flabberghasted22:32
Afdalat least when configure scripts throw an error it's not to hard to figure out the problem22:32
Afdalmake errors can be so byzantine -_-22:32
gnarfacescroll up to where the first error starts in the build log output, you should see a library name mentioned usually22:34
gnarfaceif it just mentions a undefined symbol, google usually can match it to the missing library for you22:34
gnarfaceor at least to someone else's complaint about it22:34
gnarfacedon't worry about any other errors, just install that one missing library and try again22:35
Afdalhttps://pastebin.com/umC9Z72f22:35
AfdalDoes anything look like a library here @_@?22:35
gnarfacecould you use paste.debian.net instead please? pastebin has ads22:36
Afdalwhat, really?22:36
AfdalI've never seen an ad on pastebin...22:36
gnarfacethey won't always show if you're in a region they don't think they can monetize22:37
gnarfaceor if you're using an ad blocker22:37
Afdalhttps://paste.debian.net/1218850/22:37
Afdaldoes any of that gibberish look like a library to you22:37
AfdalImagine, browsing the internet without an ad blocker...22:38
gnarfaceno actually it looks like a problem with the gcc version22:38
gnarfacebehavior change22:38
gnarfacesomething used to be allowed that's not22:38
AfdalHow did you deduce that22:38
gnarfacethe words in the error22:38
gnarfaceits clearly saying the code of mame is invalid, but one must assume a long time ago this was allowed22:39
gnarfacehappens all the time22:39
Jjp137it seems that -Werror is being passed to the compiler22:39
AfdalSo I might need to get an old gcc version like that previous user was talking about...22:39
Jjp137and GCC adds new warnings in later versions22:39
Jjp137so you need to find where -Werror is being passed and remove it perhaps22:39
gnarfaceAfdal: maybe but in this case you can probably just change the flag22:39
Afdalthe flag?22:39
gnarfaceAfdal: -Werror22:39
gnarfaceif you google that line you might come up with direct suggestions22:40
gnarfacelikely you'll have to edit the make file or patch this input.h22:40
AfdalI don't know how I would have figured this out on my own ;_;722:40
gnarfacehang out here long enough and you'll get smarter by osmosis22:41
AfdalI feel bad for polluting #devuan chat with compiling issues22:41
gnarfaceso basically "-Werror" is a highly strict mode for gcc, it throws errors if they would have just been warnings22:42
AfdalIf I ask on #mame it'll take 10 years to get an answer or they'll just tell me to use a newer version though -___-22:42
gnarfaceso possibly you can just omit -Werror from the makefile and these warnings will pass harmlessly22:42
gnarfacei wouldn't roll this into a production system because they in some cases can represent security risks, but mame is not secure to begin with so i assume you're not doing this on a public server22:43
Afdalof course not22:43
AfdalIt's my computer, I do what I want~22:43
gnarfaceif too much changed in gcc's behavior since then, this might not be as easy to build as i had hoped22:44
gnarfacebut maybe there will be only one or two of such conflicting default behavior changes22:44
Jjp137okay I downloaded the source for 0.160 and turns out the makefile checks if "NOWERROR" is defined22:44
Jjp137so do: NOWERROR=1 make22:44
gnarfacenice, good find Jjp13722:44
gnarfaceAfdal: ^ try this before you edit any files22:45
Afdalhmm, well it skipped over that error this time and continued22:46
Afdalroadblocked by a different error now22:46
AfdalTypeError: can only concatenate str (not "int") to str22:47
Afdalhmm, is that an error I'm gonna need an older gcc to address22:47
Jjp137that's...Python?22:47
Afdalno it's from a .c file22:47
Jjp137dump the output at paste.debian.net again22:48
AfdalI'll do the whole thing this time22:48
Afdalhttps://paste.debian.net/1218851/22:49
Afdaluh, oh I posed both attempts in that paste22:50
Afdalposted22:50
Afdalbottom half is with NOWERROR=122:50
Afdalhttps://embeddedartistry.com/blog/2017/05/22/werror-is-not-your-friend/22:52
Jjp137if you run `python`, is it Python 2 or 3?22:52
Jjp137(press Ctrl+D to quit Python)22:52
Afdal3.9.222:53
AfdalIs there actually a python dependency in this though22:53
Jjp137yes22:53
Jjp137it tries to run src/build/makelist.py as part of the build process but blows up22:54
Afdaloh I didn't even notice those .py bits22:54
gnarfaceyou should be able to have python2 and python3 installed concurrently and force it to use python2 even if python3 is the system default22:56
Jjp137Afdal, dumb hack: open the makefile, and at line 373, replace '@python' with 'python2', then try again22:59
Afdallol, well certainly more is happening now...23:00
Afdalso many warnings23:00
AfdalThis might just work :v23:02
Afdalso many special drivers for '80s games23:03
Afdalaww man, 40 minutes of compiling only to run into another error23:45
AfdalI think I'm missing some sort of Qt library23:45
AfdalHere's some junk from the last make output before it finally gave up https://paste.debian.net/1218856/23:49
gnarfacemaybe another version conflict, or maybe just missing *-dev packages for the native qt version, can't tell23:55
fluffywolfI don't see any errors there, just warnings23:55
gnarfaceAfdal: is that actually the start of the errors?23:56
Afdalno there's a giant endless list of warnings throughout compiling23:56
gnarfacegotta be something23:57
gnarfacegive us the last few screens worth23:57
gnarfaceor open it in emacs and do a reverse-string search from the end for "error"23:57
Afdalwell23:58
Afdalhttps://paste.debian.net/1218857/23:58
Afdalthat's as far back as my terminal history reaches23:58
gnarfacealright, you're going to have to get a build log into a text file23:59
gnarfacemake > ~/build_log.tmp.log 2>&1 &23:59
gnarfacegotta find the part where this particular series of warnings started from23:59

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!