protonscr

Not building

protonclosed
ValveSoftware/Proton#3264 · opened 2019-11-28 by KonaArctic · updated 2020-08-24 · 7 comments · github
1 matching comments, n / p to jump
KKonaArctic 2019-11-28 github

Proton ain't compiling. Here's the output:

kona@arcticjieer:~/Proton-proton-4.11-8$ make install
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
vagrant up
Platform: 4 CPUs, 3942 MB memory
Bringing machine 'debian10' up with 'virtualbox' provider...
==> debian10: Checking if box 'generic/debian10' version '2.0.6' is up to date...
==> debian10: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> debian10: flag to force provisioning. Provisioners marked to run always will still run.
vagrant rsync debian10
Platform: 4 CPUs, 3942 MB memory
==> debian10: Rsyncing folder: /home/kona/Proton-proton-4.11-8/ => /home/vagrant/proton
==> debian10:   - Exclude: [".vagrant/", "vagrant_share"]
Platform: 4 CPUs, 3942 MB memory
make: Entering directory '/home/vagrant/build--local'
make downloads -f Makefile NO_NESTED_MAKE=1
make[1]: Entering directory '/home/vagrant/build--local'
make[1]: Nothing to be done for 'downloads'.
make[1]: Leaving directory '/home/vagrant/build--local'
make: Leaving directory '/home/vagrant/build--local'
Connection to 127.0.0.1 closed.
vagrant ssh -c 'make -C "build--local"/  STEAM_DIR=/vagrant/ install'
Platform: 4 CPUs, 3942 MB memory
make: Entering directory '/home/vagrant/build--local'
make install -f Makefile NO_NESTED_MAKE=1
make[1]: Entering directory '/home/vagrant/build--local'
make[1]: *** No rule to make target '../proton/openvr/bin/win32/openvr_api.dll', needed by 'dist/dist/lib/wine/dxvk/openvr_api_dxvk.dll'.  Stop.
make[1]: Leaving directory '/home/vagrant/build--local'
make: *** [../proton/build/makefile_base.mak:17: nested_make] Error 2
make: Leaving directory '/home/vagrant/build--local'
Connection to 127.0.0.1 closed.
make: *** [Makefile:110: install] Error 2
kona@arcticjieer:~/Proton-proton-4.11-8$ 

Host is Debian Bullseye. Thanks!

Kkisak-valve maintainer 2019-11-28 github

Hello @ArcticKona, this reads like #3248. Same question as that issue report, is your openvr submodule up to date?

KKonaArctic 2019-11-28 github

Thanks! It worked.

I got a new error now:

kona@arcticjieer:~/Proton-proton-4.11-8$ make install 
vagrant up
Platform: 4 CPUs, 3942 MB memory
Bringing machine 'debian10' up with 'virtualbox' provider...
==> debian10: Checking if box 'generic/debian10' version '2.0.6' is up to date...
==> debian10: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> debian10: flag to force provisioning. Provisioners marked to run always will still run.
vagrant rsync debian10
Platform: 4 CPUs, 3942 MB memory
==> debian10: Rsyncing folder: /home/kona/Proton-proton-4.11-8/ => /home/vagrant/proton
==> debian10:   - Exclude: [".vagrant/", "vagrant_share"]
Platform: 4 CPUs, 3942 MB memory
make: Entering directory '/home/vagrant/build--local'
make downloads -f Makefile NO_NESTED_MAKE=1
make[1]: Entering directory '/home/vagrant/build--local'
make[1]: Nothing to be done for 'downloads'.
make[1]: Leaving directory '/home/vagrant/build--local'
make: Leaving directory '/home/vagrant/build--local'
Connection to 127.0.0.1 closed.
vagrant ssh -c 'make -C "build--local"/  STEAM_DIR=/vagrant/ install'
Platform: 4 CPUs, 3942 MB memory
make: Entering directory '/home/vagrant/build--local'
make install -f Makefile NO_NESTED_MAKE=1
make[1]: Entering directory '/home/vagrant/build--local'
cp -n ../proton/fonts/liberation-fonts/src/LiberationSans-Regular.sfd ../proton/fonts/liberation-fonts/src/LiberationSans-Bold.sfd ../proton/fonts/liberation-fonts/src/LiberationSerif-Regular.sfd ../proton/fonts/liberation-fonts/src/LiberationMono-Regular.sfd obj-fonts
cp -n ../proton/fonts/liberation-fonts/src/LiberationSans-Regular.sfd ../proton/fonts/liberation-fonts/src/LiberationSans-Bold.sfd ../proton/fonts/liberation-fonts/src/LiberationSerif-Regular.sfd ../proton/fonts/liberation-fonts/src/LiberationMono-Regular.sfd obj-fonts
cp -n ../proton/fonts/liberation-fonts/src/LiberationSans-Regular.sfd ../proton/fonts/liberation-fonts/src/LiberationSans-Bold.sfd ../proton/fonts/liberation-fonts/src/LiberationSerif-Regular.sfd ../proton/fonts/liberation-fonts/src/LiberationMono-Regular.sfd obj-fonts
cp -n ../proton/fonts/liberation-fonts/src/LiberationSans-Regular.sfd ../proton/fonts/liberation-fonts/src/LiberationSans-Bold.sfd ../proton/fonts/liberation-fonts/src/LiberationSerif-Regular.sfd ../proton/fonts/liberation-fonts/src/LiberationMono-Regular.sfd obj-fonts
mkdir -p dist/dist/share/fonts
cp ./obj-fonts/*.ttf "dist/dist/share/fonts"
cp ./obj-fonts/*.otf "dist/dist/share/fonts"
mkdir -p obj-cmake32
Unable to find image 'steam-proton-dev32:latest' locally
docker: Error response from daemon: pull access denied for steam-proton-dev32, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'docker run --help'.
make[1]: *** [../proton/build/makefile_base.mak:300: obj-cmake32] Error 125
make[1]: Leaving directory '/home/vagrant/build--local'
make: *** [../proton/build/makefile_base.mak:17: nested_make] Error 2
make: Leaving directory '/home/vagrant/build--local'
Connection to 127.0.0.1 closed.
make: *** [Makefile:110: install] Error 2
kona@arcticjieer:~/Proton-proton-4.11-8$ 
KKonaArctic 2019-11-28 github

Found a reference: https://github.com/ValveSoftware/Proton/issues/2369
I'm going to sleep


Does not compile

Issue transferred from https://github.com/ValveSoftware/Proton/issues/3499.
@ArcticKona posted on 2020-02-08T17:35:40:

The latest release (proton-5.0-1) does not compile.

With this error message

Unable to find image 'steam-proton-dev32:latest' locally
docker: Error response from daemon: pull access denied for steam-proton-dev32, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'docker run --help'.

Last few lines of terminal output

Thanks!

Aavenda 2020-08-24 github

i have the same issue try to build proton_5.0-next branch. All the submodule are up to date

cp ./obj-fonts/*.ttf "dist/dist/share/fonts"
cp ./obj-fonts/*.otf "dist/dist/share/fonts"
mkdir -p obj-cmake32
Unable to find image 'steam-proton-dev32:latest' locally
docker: Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address.
See 'docker run --help'.
make[1]: *** [../proton/build/makefile_base.mak:303: obj-cmake32] Error 125
make[1]: Leaving directory '/home/vagrant/build-proton_5.0-next-local'
make: *** [../proton/build/makefile_base.mak:17: nested_make] Error 2
make: Leaving directory '/home/vagrant/build-proton_5.0-next-local'
Connection to 127.0.0.1 closed.
make: *** [Makefile:110: install] Error 2

Update:
i run it a second time, the message change

cp ./obj-fonts/*.ttf "dist/dist/share/fonts"
cp ./obj-fonts/*.otf "dist/dist/share/fonts"
mkdir -p obj-cmake32
Unable to find image 'steam-proton-dev32:latest' locally
docker: Error response from daemon: pull access denied for steam-proton-dev32, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'docker run --help'.
make[1]: *** [../proton/build/makefile_base.mak:303: obj-cmake32] Error 125
make[1]: Leaving directory '/home/vagrant/build-proton_5.0-next-local'
make: *** [../proton/build/makefile_base.mak:17: nested_make] Error 2
make: Leaving directory '/home/vagrant/build-proton_5.0-next-local'
Connection to 127.0.0.1 closed.
make: *** [Makefile:110: install] Error 2
Aaeikum 2020-08-24 github

@avenda Likely a problem with your network. Some googling suggests maybe you have a proxy or DNS issue.

Aavenda 2020-08-24 github

@avenda Likely a problem with your network. Some googling suggests maybe you have a proxy or DNS issue.

No proxy o DNS issue behind. I have the stable branch (proton_5.0) in othe folder and i have no issue building proton. i will try to destroy the VM and do a make install again. ill let you know guys

Aavenda 2020-08-24 github

Solved!: vagrant destroy and make install again solve the problem and now i can build successfully. Thanks!

Proton versions

Upstream links

DLLs