Omar Polo <o...@omarpolo.com> [2022-07-11, 12:09 +0200]: > Timo Myyrä <timo.my...@bittivirhe.fi> wrote: > >> Timo Myyrä <timo.my...@bittivirhe.fi> [2022-07-10, 20:12 +0300]: >> > Asked about it and there is an open bug for it: >> > https://github.com/coelckers/gzdoom/issues/1615 >> > >> > Let's wait until that is fixed before updating the gzdoom port. >> > >> > timo >> >> Actually found a simple patch on archlinux's port of gzdoom which seems >> to fix the 'cannot find gzdoom.pk3' error. >> >> Here's updated diff: >> - explicitly disable OpenMP for now so it won't pick it up if found >> - added multimedia/libvpx to LIB_DEPENDS (port complains its unused but ldd >> lists it in gzdoom binary ) > > vpx was missing in WANTLIB ;) > > (i've added it locally, no need to re-send the diff.) > >> - patch progdir in i_main.cpp so gzdoom.pk3 is found > > I've opened https://github.com/coelckers/gzdoom/pull/1665 as an > alternative fix for the issue. I was thinking of waiting a bit for > upstream to chime in; if they like the diff I'll commit the update > with that included, if they don't or if it takes long to sort it out > we can commit the update with the hardcoded path to the pk3. what do > you think? > > Thanks, > > Omar Polo
Your diff seems simpler and better so I'd prefer to go with it but I'd wait a bit to see if the upstream has some other fix brewing. Timo
