Hey ports! I'm working on a port for Fallout 1 Community Edition: https://github.com/alexbatalov/fallout1-ce
I can build this outside of ports fine, with a simple `git clone` and whatever which made me hopeful for porting. I had to do some patches of it so it could be built offline, and support saving on *nix systems however. The port I wrote is attached here. I can successfully build this but it crashes randomly during navigation or the combat loop when built from ports. When I cp WRKSRC after patching to a temp dir and build it myself manually with the same CONFIGURE_FLAGS it is stable. Oddly, When built outside of ports, it seems to have a different checksum: izder456 [/usr/ports/openbsd-wip/games] Tower-OpenBaSeD --> sha256 ~/Projects/fallout1-ce-1.1.0/build/fallout-ce # From temp dir SHA256 (/home/izder456/Projects/fallout1-ce-1.1.0/build/fallout-ce) = 102496fed0b13fce62644b11a468c171ef3d0e95a3456b4d03e2e560057f2943 izder456 [/usr/ports/openbsd-wip/games] Tower-OpenBaSeD --> sha256 $(which fallout-ce) # From ports SHA256 (/usr/local/bin/fallout-ce) = 1d738a7f800fd0e5730c01085dbbfc1b97d61c09140d676e056a65ad4ca80784 This leads me to believe that ports uses some non-default compiler flags that clang on amd64 base doesn't otherwise use by default. I'm building on 7.6-stable in this case, but that shouldn't be relevant here. Does the ports tree use any custom compiler flags or something similar that may be introducing this behavior? If so, how can I figure out the offending build flag to manually disable it for the port and ensure stability (or- maybe patch it to support the flag)? Thanks- -- iz (they/them) > i like to say mundane things, > there are too many uninteresting things > that go unnoticed. izder456 (dot) neocities (dot) org
fallout1-ce-1.1.0.tgz
Description: application/compressed-tar
