ValveSoftware / ValveSoftware/Proton
Proton 5.13 build error
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 32.8k
- Forks
- 1.6k
- PR merge metrics
- PR metrics pending
Description
Hardware: https://linux-hardware.org/?probe=d802289f2c
Ubuntu 20.10
oooo@Oooo:~/proton$ make install
vagrant up
Platform: 4 CPUs, 4096 MB memory
Bringing machine 'debian10' up with 'virtualbox' provider...
==> debian10: Checking if box 'generic/debian10' version '3.1.12' is up to date...
==> debian10: Machine already provisioned. Runvagrant provisionor use the--provision
==> debian10: flag to force provisioning. Provisioners marked to run always will still run.
vagrant rsync debian10
Platform: 4 CPUs, 4096 MB memory
==> debian10: Rsyncing folder: /home/oooo/proton/ => /home/vagrant/proton
==> debian10: - Exclude: [".vagrant/", "vagrant_share"]
Platform: 4 CPUs, 4096 MB memory
make: Entering directory '/home/vagrant/build-proton_5.13-local'
make downloads -f Makefile NO_NESTED_MAKE=1
make[1]: Entering directory '/home/vagrant/build-proton_5.13-local'
make[1]: Nothing to be done for 'downloads'.
make[1]: Leaving directory '/home/vagrant/build-proton_5.13-local'
make: Leaving directory '/home/vagrant/build-proton_5.13-local'
Connection to 127.0.0.1 closed.
vagrant ssh -c 'make -C "build-proton_5.13-local"/ ENABLE_CCACHE=1 STEAM_DIR=/vagrant/ install'
Platform: 4 CPUs, 4096 MB memory
make: Entering directory '/home/vagrant/build-proton_5.13-local'
make install -f Makefile NO_NESTED_MAKE=1
make[1]: Entering directory '/home/vagrant/build-proton_5.13-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
fontforge -quiet -script ../proton/fonts/scripts/generatefont.pe obj-fonts/LiberationSans-Regular.sfd "Arial" "Arial" "Arial"
/bin/bash: fontforge: command not found
make[1]: *** [../proton/build/makefile_base.mak:1486: obj-fonts/LiberationSans-Regular.ttf] Error 127
make[1]: Leaving directory '/home/vagrant/build-proton_5.13-local'
make: *** [../proton/build/makefile_base.mak:17: nested_make] Error 2
make: Leaving directory '/home/vagrant/build-proton_5.13-local'
Connection to 127.0.0.1 closed.
make: *** [Makefile:115: install] Ошибка 2
FontForge is installed, trying to call it manually opens it
oooo@Oooo:~$ fontforge
Copyright (c) 2000-2020. See AUTHORS for Contributors.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
with many parts BSD http://fontforge.org/license.html. Please read LICENSE.
Version: 20190801
Based on sources from 15:50 UTC 11-Jun-2020-ML-D-GDK3.
Any ideas?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Makefile:115 and build/makefile_base.mak:1486, then reproduce the make install command inside the Vagrant Debian 10 environment. Check how the build invokes fontforge while generating fonts under obj-fonts. Done means the Proton 5.13 build completes past font generation without the command-not-found error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, shell, ubuntu
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100