[Bug 265291] x11-wm/fvwm3- FvwmIconMan module crashes on FreeBSD 13 in virtual machine

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265291

--- Comment #18 from anubhav.x61+freebsd@gmail.com ---
(In reply to Felix Palmen from comment #1)

Thank you, dear maintainer! I had manually edited the file (FvwmIconMan/x.c) to
make the sole change of addition of the line in the Git repository checkout at
commit f0ed978, c 20220526. That allowed FvwmIconMan to work!

I could not test the port as was stuck with stage directory path being mangled
during installation (could be some setting that is tickling it; IIRC "pkg"
(1.18.3 here) recently became aware of "flavor") ...

...
===>   Registering installation for fvwm3-1.0.4_5
pkg-static: Unable to access file
/build/ports/src-ports/ports/x11-wm/fvwm3/work/stage/usr/local/share/py310-fvwm3/ConfigFvwmBacker:No
such file or directory
pkg-static: Unable to access file
/build/ports/src-ports/ports/x11-wm/fvwm3/work/stage/usr/local/share/py310-fvwm3/ConfigFvwmButtons:No
such file or directory
pkg-static: Unable to access file
/build/ports/src-ports/ports/x11-wm/fvwm3/work/stage/usr/local/share/py310-fvwm3/ConfigFvwmDefaults:No
such file or directory
...

... "p310-" is there because I have set DEFAULT_VERSIONS for Python to 3.10 in
/etc/make.conf. If I comment out that line, then "py39-" is inserted instead.
Do note that the paths without "py310-" (or, "py39-") do exist.

-- 
You are receiving this mail because:
You are the assignee for the bug.