Opened 5 months ago
Closed 3 months ago
#18931 closed bug (fixed)
errors in Haiku-PyAPI after updating Haiku 32bit (only in 32bit)
Reported by: | TmTFx | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta5 |
Component: | Build System | Version: | R1/beta4 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | x86 |
Description
After updating haiku few weeks ago, some modules in Haiku-PyAPI (afaik the two I found are BFilepanel and BTranslationUtils(BTranslator?)) generate crashes even after recompiling the libraries. This happens only in Haiku 32bit (64bit is free of errors), on Haiku-PyAPI side there were no changes related to those modules so far, so I open a ticket here 'cause maybe something has been touched in Haiku side
I attach the BFilepanel debug report and the BTranslationUtils debug report
Attachments (4)
Change History (25)
by , 5 months ago
Attachment: | BFilepanel_error.report added |
---|
by , 5 months ago
Attachment: | BTranslationUtils_error.report added |
---|
Sample BTranslationUtils error when using that module in python with Haiku-PyAPI
comment:2 by , 5 months ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
This looks like the EXR libraries need to be recompiled under the new GCC, which is a problem for HaikuPorts.
comment:3 by , 5 months ago
IIRC the EXR libraries have been rev-bumped not that long ago (for gcc13)?
comment:4 by , 5 months ago
like Begasus said, it should already be recompiled. But the syslibs might be not up to date.
comment:5 by , 5 months ago
For what it's worth, I cloned/installed needed packages for HaiQR on 32bit, launches and works ok here?
comment:6 by , 5 months ago
Sorry, I forgot to mention that my test machines are all with nightlies revs not R1B4, I tested on barebone and on virtual machine
comment:7 by , 5 months ago
On 32bit R1B4 it's ok, on 32bit nightly (after running "pkgman full-sync" it crashes here too (even with the updated openexr packages)).
comment:8 by , 5 months ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
It probably needs a GCC packages update at https://cgit.haiku-os.org/haiku/tree/build/jam/repositories/HaikuPorts/x86_gcc2#n209
comment:9 by , 5 months ago
Milestone: | Unscheduled → R1/beta5 |
---|
comment:10 by , 5 months ago
Tried building with the updated gcc version on 32bit (R1B4) and get an error, source uptodate (hrev57801).
https://bpa.st/5LAA (link will stay up for a week)
comment:12 by , 5 months ago
Ah, didn't run configure now, only jam ... although, I thought this wasn't/isn't needed on 32bit? (err nvm, that was for the buildtools)
comment:13 by , 5 months ago
No change, fails on the same place, this is the script I normaly use to build Haiku:
#/bin/sh cd /Share/Haiku/buildtools git pull cd /Share/Haiku/haiku git switch master git pull mkdir -p generated; cd generated ../configure --distro-compatibility official jam -q -j5 @nightly-anyboot
EDIT: swithing to x86 in Terminal for a new check EDIT2: strike that, I see gcc_syslibs 5.4.0 passing by ;) (build failure)
comment:14 by , 5 months ago
You might submit a separate bug report. In the meantime you can build by checkouting an older hrev like hrev57777
comment:15 by , 5 months ago
Probably related to https://dev.haiku-os.org/ticket/18692
OK, I just fiddled a bit with checking the exr ticket, still n00b here, need to figure out how to switch to hrev57777 first :)
comment:17 by , 5 months ago
Errr didn't check that ;) n00b remember, only getting started and grasping a bit on how this all works. Used https://review.haiku-os.org/c/haiku/+/7820 for now.
comment:18 by , 5 months ago
Well ... succes! Took a while, but got 32bit image with gcc13 updated files. To be sure I first created an unchainged regular build and then changed the version in the build/jam/repositories/HaikuPorts/x86_gcc2.
As expected the regular one crashed, the changed one worked out fine.
This should do it for 32bit and 64bit:
diff --git a/build/jam/repositories/HaikuPorts/x86_64 b/build/jam/repositories/HaikuPorts/x86_64 index b81791a9..69040101 100644 --- a/build/jam/repositories/HaikuPorts/x86_64 +++ b/build/jam/repositories/HaikuPorts/x86_64 @@ -83,9 +83,9 @@ RemotePackageRepository HaikuPorts gawk-5.2.2-1 gettext-0.21.1-4 gettext_libintl-0.21.1-4 - gcc-13.2.0_2023_08_10-3 - gcc_syslibs-13.2.0_2023_08_10-3 - gcc_syslibs_devel-13.2.0_2023_08_10-3 + gcc-13.3.0_2023_08_10-1 + gcc_syslibs-13.3.0_2023_08_10-1 + gcc_syslibs_devel-13.3.0_2023_08_10-1 giflib-5.2.1-1 giflib_devel-5.2.1-1 git-2.37.3-1 diff --git a/build/jam/repositories/HaikuPorts/x86_gcc2 b/build/jam/repositories/HaikuPorts/x86_gcc2 index 4dab6a47..dc4f827f 100644 --- a/build/jam/repositories/HaikuPorts/x86_gcc2 +++ b/build/jam/repositories/HaikuPorts/x86_gcc2 @@ -205,9 +205,9 @@ RemotePackageRepository HaikuPorts fribidi_x86_devel-1.0.13-1 game_music_emu_x86-0.6.3-2 game_music_emu_x86_devel-0.6.3-2 - gcc_x86-13.2.0_2023_08_10-3 - gcc_x86_syslibs-13.2.0_2023_08_10-3 - gcc_x86_syslibs_devel-13.2.0_2023_08_10-3 + gcc_x86-13.3.0_2023_08_10-1 + gcc_x86_syslibs-13.3.0_2023_08_10-1 + gcc_x86_syslibs_devel-13.3.0_2023_08_10-1 gettext_x86-0.21.1-4 gettext_x86_libintl-0.21.1-4 giflib_x86-5.2.1-1
comment:19 by , 5 months ago
Component: | - General → Build System |
---|---|
Platform: | All → x86 |
comment:20 by , 3 months ago
comment:21 by , 3 months ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Yes, I suppose so. Any further problems should be dealt with in HaikuPorts, and it looks like there is a ticket there also: https://github.com/haikuports/haikuports/issues/10774
sample erron when using BFilepanel python module