Ok, where do I have to look for the camera?
Spoiler: Compare package versions and file hashes.
MSYS2, GDB и управление памятью
Эта история началась с того, что мне захотелось поработать с интерпретатором одного очень экзотического языка программирования, а закончилась тем, что я освоил не менее экзотические (для меня) нюансы работы с памятью в С в Windows и POSIX, и того, как работает отладчик gdb в Windows. ну очень экзотического
Das #Barcamp #Graz 2025 wird in den #lightningtalks der Linuxtage angekündigt.
Save-the-date : 17.05.2025
Lightning talks sind #Kurzvorträge bei denen man sich kurzfristig zu einem (max. 5 Minuten langen) #Vortrag meldet.
Außerdem diesmal noch dabei:
#pijul, #msys2, #openwrt und #orgmode, Methoden zu #spam-Verhinderung, #softskills,
#private.coffee ,
In case anyone is wondering why #ssh (#openssh) is failing silently on #msys2 - seems they pushed out a version that depends on an msys2 runtime version that's stuck in some kind of release queue: https://github.com/msys2/MSYS2-packages/issues/5320
Almost forgot.
Yesterday I tried installing #MSYS2. I think I need to redo it later with better luck.
I don't know how else to phrase it, but once I tried running full update, the MSYS2 environment just *shat itself.* I must emphasise that I do not use this kind of expression lightly.
First it said the pacman database was funky. Then bash started whining about not being able to create processes.
*What.*
...I uninstalled the whole thing before things got even weirder.
Last time I tried using #Cygwin was early 2000s. All I can remember about that experience was that it was mildly janky, and I heard that MinGW was coming to fix all that. ...I guess at this pace we'll never get rid of the jank.
Earlier I said that I had plans of starting a #cplusplus project but had to stop it because setting the build dependencies up in Windows is still an absolute nightmare. Annnd that the libraries are available in #Python anyway, so I should probably just write this in Python.
OK, after the first assessment, I'm no longer that sure.
One of the things I want to use is #SDL3, which does have Python library. ...with incredibly liberal application of `ctypes` on top of it. This is going to be an absolute headache *anyway*.
I'm mildly at some bargaining phase, like, um, maybe I cold bite the bullet and go with #MSYS2 after all.
The #Geany developers are looking for a new maintainer for the Windows builds of Geany.
The Windows builds of Geany were created previously on a Windows 7 VM which is not supported any longer.
We are looking for a new maintainer who likes to take care of the Windows builds, knows MSYS2 and has access to a Windows system with a recent version to be able to build and test Geany on Windows.
For more details and comments, see https://github.com/geany/geany/issues/4189.
@malanalysis seriously need a powershell for bash scripters , using #msys2 is getting old.
The method I use to build #emacs on #windows #msys2
https://gist.github.com/LdBeth/d663a7d3ea27776bfe211241ad7fa5e5
#schule mit #foss:
In einer nächsten Stunde gibt's Linux serviert.
#alpine mit #xfce läuft auch eingequetscht in unsere Win-VMs, dank #msys2 + #qemu
https://www.qemu.org/
https://www.msys2.org/
https://alpinelinux.org/
Pro tip: running "pacman -Ss | grep installed" will get all installed packages with their repos if you use a distro that uses pacman, like Arch, or environments like MSys2.
Some more #GTK4 cross-compilation to non-free systems with #WINE + #MSYS2/ #Darling + #Homebrew shenanigans - here we have the Apple-provided and built XCode toolchain & homebrew running on Darling on Linux building the GTK 4 Hello World example, which then successfully runs on real macOS 14!
Reddit tells me that #MSYS2 is one of the more comprehensive and up-to-date distributions of #MinGW-w64, so i'm gonna use that.
the funny thing about this one is that it uses regular pacman
(neofetch came by default - that was not my doing!)
@wader I think I can add a bit of explanation here. MSVCRT.DLL (as a "standard C library") was included with windows for a long time, but they quickly ran into issues with it, most likely caused by not having sane mechanisms for versioning. So, what they did was including a C runtime with each release of their compiler (#MSVC) and expect this runtime to be redistributed with software using it. MSVCRT.DLL had its public API/ABI frozen in a state with #C89 and partial(!) #C99 support and was declared "private" to the OS.
#Mingw (which is also distributed by #MSYS2) nevertheless continued linking to MSVCRT.DLL (and I see why, it's really stupid to have tons of copies of the C runtime ...). So, while the compilers support newer C standards, the standard lib doesn't, and therefore you need quite some hacks and workarounds. And I wouldn't be surprised to find lots of funny misbehavior, that's why I think the issue might indeed be the strftime() from MSVCRT.DLL.
[...]
