https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=295565
Alexey Shuvaev <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Alexey Shuvaev <[email protected]> --- (In reply to Gleb Popov from comment #1) Hi! TLDR: +1 for adding this OPTION to the port! 1) Considering x11-toolkits/wxgtk32 by itself: having on option to turn degugging on/off is a good thing, IMHO! The users can switch it according to their needs, with default to off (targeting normal users, not the developers). You can find a truncated poudriere log of the successful build of x11-toolkits/wxgtk32 with the added option here: bug #294281, comment #10. My understanding of the --enable-debug/--disable-debug is the presence of debug symbols in the library + switching on/off some assertions again inside the wxWidgets library. However, I have not looked at it really yet, but do so on the next poudriere bulk build run! For now, with the DEBUG switched OFF, I have: file /usr/local/lib/libwx_gtk3u_core-3.2.so.0.4.1 /usr/local/lib/libwx_gtk3u_core-3.2.so.0.4.1: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, for FreeBSD 16.0 (1600018), stripped 2) As of cad/OrcaSlicer...I think its code is just...dirty. Therefore, it does not run reliably yet. Especially on CURRENT. Even less with wxgtk32 with DEBUG option turned ON. Switching DEBUG OFF in wxgtk32 is definitely not a solution, but might help someone to get cad/OrcaSlicer running...at least once! My plan is to switch wxgtk32 DEBUG option back to ON, and probably try to build cad/OrcaSlicer with debug symbols as well. I am not sure, how bad the things are, probably quite bad, looking at the number of patch- files in the port! But then again, having the official DEBUG OPTION in x11-toolkits/wxgtk32 is definitely helping in situations like this one! Thank you for the time looking at it! -- You are receiving this mail because: You are the assignee for the bug.
