Thread Rating:
  • 5 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
PCSX2 for Arch Linux
UnrulyMop: I notice by your PS1 that "Console & Emulators" is the directory name where you're building pcsx2-git, however the build log failed to find the files inside "Emulators" directory. It means the space characters are not being handled correctly by PCSX2 cmake. I suggest dropping the spaces and the "&", to avoid further build issues.
Reply

Sponsored links

(07-15-2019, 12:02 AM)josephg Wrote: UnrulyMop: I notice by your PS1 that "Console & Emulators" is the directory name where you're building pcsx2-git, however the build log failed to find the files inside "Emulators" directory. It means the space characters are not being handled correctly by PCSX2 cmake. I suggest dropping the spaces and the "&", to avoid further build issues.

O.o crazy how having someone else look at the data pulls the silliest explanations out of the ether. I'll go test and be right back.

Okay, so it hasn't finished compiling but it's definitely gotten further than yours. I've gone back through your code (in the hope of repaying the favor) and found a segfault owing to the GCC, thus triggering the later failure by corruption. If you haven't already I'd recommend the 'downgrade' application (downgrade gcc gcc-libs) and then select 8.3.

I don't do a lot of 'building' nowadays myself, so having the latest GCC isn't that important to me.

Many thanks!
Reply
If you didn't want to downgrade gcc, the other option would be to install clang and build pcsx2 yourself with it,with:
sh build.sh --clang --clean

or something similar.

There is a patch for gcc 9 that takes care of the segfault, btw. It's just not applied in arch...
Reply
It was reported that one can successfully build PCSX2 (without downgrading GCC) by editing pcsx2-git's PKGBUILD in order to insert
Code:
export CC=/usr/bin/clang
export CXX=/usr/bin/clang++

before the cmake command-line, and then use makepkg to build.

More talk about is also happening in pcsx2-git comments
Reply
Just thought I'd preemptively mention that if you upgrade to pango and lib32-pango to 1.44 and find that pcsx2 errors out on compiling on one of pango's headers, downgrading to 1.43 will take care of it.

Alternatively, you could go over to /usr/include/pango-1.0/pango/pango-coverage.h and change:
Code:
#include <hb.h>

to
Code:
#include <harfbuzz/hb.h>


since that's what's breaking it, but editing system includes isn't a great idea, and next update will probably mess it up again.

pango 1.44 seems like a significant regression. Apparently a bunch of older fonts no longer work with it, and the output generally looks worse than 1.43, judging by the bug reports...

--arcum42
Reply




Users browsing this thread: 3 Guest(s)