Created attachment 221410 [details]
Build and package info is available at https://gitlab.com/swills/freebsd-ports/pipelines/239377931
Works for me.
But better to add
I build all with -O3 and wine does not work proper after it, wine-proton hang on:
frame #4: 0x000000006302e211 ntdll.so`find_drive_rootA + 3153
frame #5: 0x0000000063031f20 ntdll.so`unix_to_nt_file_name + 80
frame #6: 0x000000006301e218 ntdll.so`add_path_var + 56
frame #7: 0x000000006302007f ntdll.so`get_dynamic_environment + 559
frame #8: 0x000000007bc5168d
some how it call get_dynamic_environment in infinite loop.
Probably same required for other wine ports.
(In reply to rozhuk.im from comment #2)
> But better to add
The default setting is already CFLAGS="-O2 -pipe -fstack-protector-strong -Wl,-rpath=/usr/local/lib/gcc9 -isystem /usr/local/include -fno-strict-aliasing ". (http://beefy6.nyi.freebsd.org/data/121amd64-default/560362/logs/wine-proton-5.13.2.log)
> I build all with -O3
You know as well as anyone this a dumb thing to do.
wine add many flags inside it is own build system, probably some of them with -O3 gives broken code.
No, I do not know :)
I am using system and all ports with -O3 more than 1 year and see no crashes or other annoying things.
audio/deadbeef, devel/libudev-devd only these two I alnost sure that was have negative effect from -O3.
And now wine. In past I use i386-wine-devel, but now there is no working package for current, so I build wine64.
archivers/file-roller - some times crashes, but I almost sure that this is not related to -O3.
Even security/libtasn1 failure - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252548 not related with -O3.
A commit references this bug:
Date: Sat Feb 6 18:02:10 UTC 2021
New revision: 564231
emulators/wine-proton: Update to 5.13-4
Submitted by: Ales S <firstname.lastname@example.org>