Humm it's odd, because I built it without even having wine (winegcc) on my machine. Could it be that it tries to use wine if it's installed but fails?
Sadly that made no difference, I'm still getting command not found. Can you share your setup notes for your build host?
I'm having the same issue. It should be using winegcc from build/tools.win(32|64)/bin and you can see the PATH being updated to include those binaries here: https://github.com/ValveSoftware/Proton/blob/proton_3.7/build_proton.sh#L334
Though I've noticed that for me, PATH is getting clobbered within the chroot environment
$ PATH="/usr/bin" schroot --chroot steamrt_scout_beta_i386 env | grep PATH
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/
I've not yet had much time to dig in further - let me know if you find anything!
@thronezilla good spot! I can confirm the same behaviour with $PATH, it's easy to reproduce with schroot --chroot steamrt_scout_beta_amd64 -- env
What I can't figure out is how to stop it... I've tried:
I even resorted to using strace on schroot to try and see how it was being overridden... no luck yet!
I'm getting the same error, have you found any solution to this?
proton 3.7x1 2018-08
I think I have the build environment correctly set up - DXVK builds, then Wine kicks off, gets most of the way through, and then fails missing winegcc:
winegcc is definitely present in the host enviroment:
Do I need to make it available to the chroots as well?