Re: [Slackbuilds-users] Mumble gtav plugin compile error on Slackware 32-bit
On 3/18/24 19:56, Willy Sudiarto Raharjo wrote: >> Seems there was some sort of omission or regression (or "Who still uses >> 32-bit?") when the gtav plugin is compiled for mumble. This was fixed >> previously in mumble-master but somehow did not end up in mumble-1.4.287 >> >> I've posted the fix to my branch for the next update. However, other >> than a qemu VM (not set up for audio), I'm not able to test fully. > > Thanks for this update > can you also test with latest protobuf3? > https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip > Looks like mumble compiles ok withe protobuf3-26 on Slackware32. I'll test Slackware64 once I clean up my VM. -kb ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Linphone maintenance
Sebastian Arcus writes: > On 08/02/2024 02:56, Willy Sudiarto Raharjo wrote: >>> What WSR is responding is factually wrong. >>> >>> I have submitted the slackbuild for the most recent version of linphone >>> (submitted as linphone-desktop, because nowadays linphone is very >>> different from what it was in the past, and the developers, Belledonne >>> Communications, keep it in a separate repo from the old linphone). >>> >>> The code is here: >>> https://gitlab.com/Lockywolf/lwfslackbuilds/-/tree/master/05_submitted/linphone-desktop?ref_type=heads >>> It was rejected for the reason of being "for the alpha version". >>> (WSR's own responce from Sat, 23 Sep 2023 10:34:46 +0700) >>> do you mind to wait until 5.2.0 is released or go for previous version which is released under stable label? >>> >>> So I have been waiting for the 5.2.0 since. >>> >>> You can roll-back to the most-recent non-alpha, and re-submit, I do not >>> mind. >> They have released 5.2.1 6 days ago >> https://gitlab.linphone.org/BC/public/linphone-desktop/-/tags > > Just checking if we reached any decision on this? Are we happy to use > Lockywolf's > scripts - and move Linphone to version 5.1.2 which compiles on Slackware 15.0 > - and > replace the old Linphone scripts? Is anybody going to take linphone-desktop away from me? -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) signature.asc Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Mumble gtav plugin compile error on Slackware 32-bit
Seems there was some sort of omission or regression (or "Who still uses 32-bit?") when the gtav plugin is compiled for mumble. This was fixed previously in mumble-master but somehow did not end up in mumble-1.4.287 I've posted the fix to my branch for the next update. However, other than a qemu VM (not set up for audio), I'm not able to test fully. Thanks for this update can you also test with latest protobuf3? https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip -- Willy Sudiarto Raharjo OpenPGP_0x3F617144D7238786.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] Mumble gtav plugin compile error on Slackware 32-bit
Hello
Seems there was some sort of omission or regression (or "Who still uses
32-bit?") when the gtav plugin is compiled for mumble. This was fixed
previously in mumble-master but somehow did not end up in mumble-1.4.287
I've posted the fix to my branch for the next update. However, other
than a qemu VM (not set up for audio), I'm not able to test fully.
https://github.com/mumble-voip/mumble/issues/5849
https://github.com/mumble-voip/mumble/pull/5850
8<
From 13c051b36b387356815cff5d685bc628b74ba136 Mon Sep 17 00:00:00 2001
From: Davide Beatrici
Date: Thu, 1 Sep 2022 23:32:57 +0200
Subject: [PATCH] FIX(positional-audio): Force 8 bytes alignment for
CCameraAngles in GTAV plugin
https://en.cppreference.com/w/cpp/language/alignas
This fixes compilation when the implicit alignment is not 8 bytes.
It can be the case with 32 bit targets.
---
plugins/gtav/structs.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/plugins/gtav/structs.h b/plugins/gtav/structs.h
index 2829dc11e1..0e4f76edab 100644
--- a/plugins/gtav/structs.h
+++ b/plugins/gtav/structs.h
@@ -118,7 +118,7 @@ struct CCameraManagerAngles {
ptr_t cameraAngles; // CCameraAngles *
};
-struct CCameraAngles {
+struct alignas(8) CCameraAngles {
uint8_t pad1[960];
ptr_t playerAngles; // CPlayerAngles *
uint8_t pad2[60];
--->8-
-kb
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Segmentation Fault help needed
Hello Antonio!
TL;DR: the error seems to be caused by the MAP_FIXED mmap flag used in
bbccon.c:1728.
You can find a patch attached that solves that issue, but I cannot
guarantee that the program will still work as intended with it. The
program seems to really want to allocate memory at a specific address
and removing that flag breaks that assumption.
The steps I followed to determine the source of the issue:
1. modify the src/console/makefile file to change every optimization
flag (i.e. gcc "-O2" or "-Os") to debug flags ("-O0 -g" for gcc, "-g"
for nasm) and removing any stripping instruction ("-Wl,-s")
2. recompile and run via gdb:
cd console/linux
make -f makefile
gdb ./bbcbasic
(gdb) run
Starting program: /tmp/BBCSDL/console/linux/bbcbasic
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
0x000
0x0001003f in ?? ()
(gdb) bt
#0 0x0001003f in ?? ()
#1 0x0001 in ?? ()
#2 0x000103ae75f6 in ?? ()
#3 0x in ?? ()
(gdb)
3. as can be seen from the gdb backtrace (bt) output, no useful
information can be discerned
4. another way to catch the problem is by stepping one instruction at
a time from the main() function entrypoint (hoping that the error spawns
early in the program code ^_^), so, back in gdb (starting another
session)[1]:
(gdb) run
Starting program: /tmp/BBCSDL/console/linux/bbcbasic
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Breakpoint 1, main (argc=1, argv=0x7fffdf68) at ../../src
/bbccon.c:1683
1683int exitcode = 0 ;
(gdb) next
1684void *immediate = NULL ;
(gdb)
1715pthread_t hThread = 0 ;
(gdb)
1717platform = 1 ;
(gdb)
1719void *base = NULL ;
(gdb)
1721while ((MaximumRAM >= MINIMUM_RAM) && (NULL == (base
= mymap (MaximumRAM
(gdb)
1726if (base != NULL)
(gdb)
1727userRAM = mmap (base, MaximumRAM, PROT_EXEC
| PROT_READ | PROT_WRITE,
(gdb)
Program received signal SIGSEGV, Segmentation fault.
0x0001003f in ?? ()
(gdb)
As can be seen, the SIGSEGV occurred after trying to step over the mmap
function call in bbccon.c at line 1727. By inspecting it in the source
file and by looking at the "mmap" man page, one can see that:
- the MAP_FIXED flag needs some care to be correctly used;
- the SIGSEGV signal can be the result of "Attempted write into a
region mapped as read-only."
I think this means that the "base" address returned by the "mymap"
function does not work well in the following "mmap" call with the
MAP_FIXED flag, probably due to some memory management kernel settings
that are different between Slackware and Debian, like
"/proc/sys/vm/mmap_min_addr" (if I remember correctly).
Hope to be helpful!
--
Alan Alberghini
SBo clone: https://github.com/414n/slackbuilds.org
[1]: after the first "next" instruction no command is echoed in the
following (gdb) prompts because I just pressed ENTER on the keyboard to
repeat the last command entered
--- a/src/bbccon.c 2024-03-18 21:36:19.067053619 +0100
+++ b/src/bbccon.c 2024-03-18 21:36:05.898054258 +0100
@@ -1725,7 +1725,7 @@
if (base != NULL)
userRAM = mmap (base, MaximumRAM, PROT_EXEC | PROT_READ | PROT_WRITE,
- MAP_PRIVATE | MAP_ANON, -1, 0) ;
+ MAP_FIXED | MAP_PRIVATE | MAP_ANON, -1, 0) ;
#endif
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
