call wineboot as a script,

[pabloveliz]

wineboot is a script, and in tkg when you call it directly from this setup script, I get

environment: : command not found

Therefore, to call a script from within a script let's use bash because...

$ file /opt/wine-staging/bin/wineboot
/opt/wine-staging/bin/wineboot: POSIX shell script, ASCII text executable

[misyltoad]

Works fine here with TKG.

wineboot has a shebang of #!/bin/sh, not sure why it doesn't work for you.

Can you give more info about your setup, something seems very broken.

[pchome]

Maybe something wrong in ~/.profile / ~/.bash_profile / ~/.bashrc ?

[adminx01]

Can reproduce environment: : command not found when running setup_dxvk.sh install through bash. Distro: EndeavourOS/Arch.

[airminer]

@pabloveliz @miocrime Could you post the output of the following commands?

$ which wineboot
$ command -v wineboot
$ ls -l $(readlink -f $(command -v wineboot))

[adminx01]

sorry for taking long, did not notice your comment which wineboot /usr/bin/wineboot

command -v wineboot /usr/bin/wineboot

ls -l $(readlink -f $(command -v wineboot)) -rwxr-xr-x 1 root root 2337 Jul 3 19:59 /usr/bin/wineboot

I use wine-tkg.

[WinterSnowfall]

$ file /opt/wine-staging/bin/wineboot
/opt/wine-staging/bin/wineboot: POSIX shell script, ASCII text executable

Out of curiosity, if you create a softlink for wineboot in /usr/bin, does it then work properly for you?

ln -s /opt/wine-staging/bin/wineboot /usr/bin/wineboot

Wine staging (from WineHQ) appears to add a soft link for it under /usr/bin by default (maybe it's missing in your case?): wineboot -> /opt/wine-staging/bin/wineboot

and which wineboot returns: /usr/bin/wineboot

Unless somehow tkg needs something from your .bashrc env (which will not get parsed on a non-interactive shell), it should work with this setup.

[adminx01]

I am not able to replicate the error anymore. Perhaps it was fixed on tkg's side, didn't look through commits.

I guess this can be closed?