Yeah, same result as before sadly.

Project name: mesa
Build started at 2020-07-07T11:28:20.925677
Main binary: /usr/bin/python
Build Options: -Db_lto=false -Db_pie=true -Db_ndebug=true -Dplatforms=x11,wayland,drm,surfaceless -Ddri-drivers=i915,i965,r100,r200,nouveau -Dgallium-drivers=r300,r600,radeonsi,nouveau,virgl,svga,swrast,iris -Dvulkan-drivers=amd,intel -Dvulkan-overlay-layer=true -Dvulkan-device-select-layer=true -Dswr-arches=avx,avx2 -Ddri3=true -Degl=true -Dgallium-extra-hud=true -Dgallium-nine=true -Dgallium-omx=disabled -Dgallium-opencl=icd -Dgallium-va=true -Dgallium-vdpau=true -Dgallium-xa=true -Dgallium-xvmc=false -Dgbm=true -Dgles1=false -Dgles2=true -Dglvnd=true -Dglx=dri -Dlibunwind=true -Dllvm=true -Dlmsensors=true -Dosmesa=gallium -Dshared-glapi=true -Dvalgrind=false -Dprefix=/usr -Dlibdir=/usr/lib32 -Dlibexecdir=lib -Dsbindir=bin -Dauto_features=enabled -Dbuildtype=plain -Dwrap_mode=nodownload '--native-file crossfile.ini'
None of 'PKG_CONFIG_PATH' are defined in the environment, not changing global flags.
None of 'PKG_CONFIG_PATH' are defined in the environment, not changing global flags.
Project name: mesa
Project version: 20.1.2
Using 'CC' from environment with value: 'gcc -m32'
Using 'CFLAGS' from environment with value: '-O0'
Using 'LDFLAGS' from environment with value: '-Wl,-O0,--sort-common,--as-needed,-z,relro,-z,now'
Using 'CPPFLAGS' from environment with value: '-D_FORTIFY_SOURCE=2'

Thanks for the suggestions regardless x_wing.

View this comment - View article - View full comments

That output is from my trying to use the DEBUG_CFLAGS in makepkg.conf, not from when I was exporting my own values in the PKGBUILD. Here is the relevant Meson log for that:
Project name: mesa
Project version: 20.1.2
Using 'CC' from environment with value: 'gcc -m32'
Using 'CFLAGS' from environment with value: '-O0'
Using 'LDFLAGS' from environment with value: '-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now'
Using 'CPPFLAGS' from environment with value: '-D_FORTIFY_SOURCE=2'
None of 'CC_LD' are defined in the environment, not changing global flags.

And Penumbra still crashes.

View this comment - View article - View full comments

crossfile.ini is created from the PKGBUILD file of the lib32-mesa Arch package:
https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/lib32-mesa

The contents of crossfile.ini in a generated package are as follows:
[binaries]
llvm-config = '/usr/bin/llvm-config32'

As for the CFLAGS, that is being grabbed from what is defined in makepkg.conf as used by the Arch Build System. Setting the 'debug' option in the PKGBUILD makes its append DEBUG_CFLAGS which is where I was instructed to add the "-O0" flag in the linked Frictional Games forum thread:
https://www.frictionalgames.com/forum/thread-54134-post-363860.html#pid363860

Back in April and May adding the "-O0" flag to DEBUG_CFLAGS in makepkg.conf and toggling the 'debug' and '!strip' options in the lib32-mesa PKGBUILD did do the trick. Now doing so causes it to complain about being unable to determine the dynamic linker.

Here is the relevant parts of my makepkg.conf file:
 #-- Compiler and Linker Flags
CPPFLAGS="-D_FORTIFY_SOURCE=2"
CFLAGS="-march=x86-64 -mtune=generic -O3 -pipe -fno-plt"
CXXFLAGS="-march=x86-64 -mtune=generic -O3 -pipe -fno-plt"
LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now"
#-- Make Flags: change this for DistCC/SMP systems
#MAKEFLAGS="-j2"
#-- Debugging flags
DEBUG_CFLAGS="-g -fvar-tracking-assignment -O0"
DEBUG_CXXFLAGS="-g -fvar-tracking-assignments -O0"

I have tried exporting my own CFLAGS in the PKGBUILD containing just the "-O0" flag and with that I can get the lib32-mesa package to build, but Penumbra will still crash when using these builds. I have also tried using the Meson c_args option to set the "-O0" flag to no good effect. I have also tried setting the various "-mno-sse" flags which again do nothing.

View this comment - View article - View full comments

Attempting to build the lib32-mesa package as described before now just results in this error:
Build started at 2020-07-05T10:15:07.706677
Main binary: /usr/bin/python
Build Options: -Db_lto=true -Db_pie=true -Db_ndebug=true -Dplatforms=x11,wayland,drm,surfaceless -Ddri-drivers=i915,i965,r100,r200,nouveau -Dgallium-drivers=r300,r600,radeonsi,nouveau,virgl,svga,swrast,iris -Dvulkan-drivers=amd,intel -Dvulkan-overlay-layer=true -Dvulkan-device-select-layer=true -Dswr-arches=avx,avx2 -Ddri3=true -Degl=true -Dgallium-extra-hud=true -Dgallium-nine=true -Dgallium-omx=disabled -Dgallium-opencl=icd -Dgallium-va=true -Dgallium-vdpau=true -Dgallium-xa=true -Dgallium-xvmc=false -Dgbm=true -Dgles1=false -Dgles2=true -Dglvnd=true -Dglx=dri -Dlibunwind=true -Dllvm=true -Dlmsensors=true -Dosmesa=gallium -Dshared-glapi=true -Dvalgrind=false -Dprefix=/usr -Dlibdir=/usr/lib32 -Dlibexecdir=lib -Dsbindir=bin -Dauto_features=enabled -Dbuildtype=plain -Dwrap_mode=nodownload '--native-file crossfile.ini'
Python system: Linux
The Meson build system
Version: 0.54.3
Source dir: /home/hamish/Downloads/lib32-mesa/src/mesa-20.1.2
Build dir: /home/hamish/Downloads/lib32-mesa/src/build
Build type: native build
Program python found: YES (/usr/bin/python)
Running command: /usr/bin/python bin/meson_get_version.py
--- stdout ---
20.1.2
--- stderr ---


None of 'PKG_CONFIG_PATH' are defined in the environment, not changing global flags.
None of 'PKG_CONFIG_PATH' are defined in the environment, not changing global flags.
Project name: mesa
Project version: 20.1.2
Using 'CFLAGS' from environment with value: '-march=x86-64 -mtune=generic -O3 -pipe -fno-plt -g -fvar-tracking-assignment -O0 -fdebug-prefix-map=/home/hamish/Downloads/lib32-mesa/src=/usr/src/debug'
Using 'LDFLAGS' from environment with value: '-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now'
Using 'CPPFLAGS' from environment with value: '-D_FORTIFY_SOURCE=2'

mesa-20.1.2/meson.build:21:0: ERROR: Unable to determine dynamic linker

Which is kind of annoying as I never got around to completing Requiem yet.

View this comment - View article - View full comments

For what it is worth, I found with Requiem that the game will crash when you pick up the first audio log from Eloff Carpenter.

View this comment - View article - View full comments

So my lovely little Gigabyte Radeon RX 460 arrived last night. I can now confirm that on this card using AMDGPU I am getting crashes not only when I flatten the coin in the vice at the start of Black Plague but also when I leave the fishing boat at the start of Overture once again.

View this comment - View article - View full comments

Turns out I still have my old Desura receipt:


I have got my ten dollars worth I have to say.

View this comment - View article - View full comments

Quoting: erolmateiThat said, yes, to fix the issue you need to build Mesa so that it does not use optimized SSE instruction (one of the effects of the -O0 flag btw). This is, imho, not a clean solution.

I am sure it is like swatting a mosquito with a sledge hammer, but it worked for me.

I do wonder if a complete Penumbra source port could be constructed from the Overture code.

View this comment - View article - View full comments

Other than SteamOS/Linux once being listed on the Steam page for it was there ever any other acknowledgement that Shadow Warrior 2 was coming to Linux at all?

View this comment - View article - View full comments

The Linux version of Metro: Last Light Redux was bounced by GOG.com quality control:

QuoteIn this case that responsibility was on us ... We encountered a number of technical issues while preparing our DRM-free Linux and Mac OS X versions and made the call to hold back the releases until we can be confident in the quality of our product. While we are trying to fix the problems, we cannot make any promises if and when the DRM-free versions will be ready."

Source: https://news.softpedia.com/news/Deep-Silver-Refuses-to-Provide-Linux-DRM-free-Builds-to-GOG-com-for-Metro-Last-Light-Redux-481335.shtml

Also seems to be true with Postal 2 as well:

QuoteWe had planned on having Mac and Linux ports done for this release, but we ran into some really bizarre problems in trying to get them to run, that we haven't sorted out yet. So we had to push those plans back for a while. Unfortunately, I can't give you an ETA on when we might get them done. :(

Source: https://www.gog.com/forum/postal_series/linux_version_of_postal_2_and_paradise_lost/post2

Which is why when I played Postal 2 again earlier this year I had to use my old outdated Desura copy like I did with the Penumbra Collection.

View this comment - View article - View full comments