[Sep 2020 ed.] PCem MSYS2 build guide (with wxWidgets)

[dns2kv2]

Just share an update from my previous test, might save the day for others.

got this hick cup while updating pcem:

Code: Select all

mingw32-make clean
CDPATH="${ZSH_VERSION+.}:" && cd . && C:/msys32/usr/bin/sh.exe /home/{your username}/pcem/missing aclocal-1.15
aclocal-1.15: error: aclocal: file '/msys32/usr/share/aclocal/xsize.m4' does not exist
mingw32-make: *** [Makefile:354: aclocal.m4] Error 1

The cure is easy, add another "autoreconf -i" command before "mingw32-make clean" command:

Code: Select all

#clean previous build, redownload & update pcem sources then recompile pcem
#open MSYS2 MinGW 32-bit shell (C:\msys32\mingw32.exe) and run below command:
cd ~/pcem
autoreconf -i
mingw32-make clean
hg pull && hg update default
autoreconf -i
./configure --enable-networking --enable-release-build
mingw32-make -j

[Zilog]

Hi To,
i have this problem when compile pcem on Windows:

collect2.exe: error: ld returned 1 exit status
mingw32-make[1]: *** [Makefile:908: pcem.exe] Error 1
mingw32-make[1]: Leaving directory 'D:/_msys64/home/user/pcem/src'
mingw32-make: *** [Makefile:364: all-recursive] Error 1

Very Thanks a lot for all help.

[shermanp]

Just made a few updates to the OP. No major changes, but I went through it again on the latest version of MSYS2 (still slow, sigh...).

Main changes are using an updated version of the npcap SDK, and using git to clone the github pcem repository.

[A. Naim]

"error: perl: signature from "David Macek <david.macek.0@gmail.com>" is invalid
:: File /var/cache/pacman/pkg/perl-5.32.0-2-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature))."

[shermanp]

Note, if you haven't updated MSYS2 in a while, there's been some package maintainer changes and corresponding signing key changes. I found it easier to restart from scratch with a fresh MSYS2 reinstall.

[JosepMa]

I saw that there are some instructions in the news sections. But indeed, it can need multiple steps depending on when it was last updated
https://www.msys2.org/news/

I had to do this:
Follow instructions in the 2020-06-29 news.
Then follow instructions in the 2020-05-22 news.
In your case (problems with .zst), you might probably need to do 2020-05-31 news.
Then a package -Syu,
Then Follow 2020-06-15 news.

That got my msys2 up to date.

[A. Naim]

Note, if you haven't updated MSYS2 in a while, there's been some package maintainer changes and corresponding signing key changes. I found it easier to restart from scratch with a fresh MSYS2 reinstall.

Thanks; it compiles now.

I saw that there are some instructions in the news sections. But indeed, it can need multiple steps depending on when it was last updated
https://www.msys2.org/news/

I had to do this:
Follow instructions in the 2020-06-29 news.
Then follow instructions in the 2020-05-22 news.
In your case (problems with .zst), you might probably need to do 2020-05-31 news.
Then a package -Syu,
Then Follow 2020-06-15 news.

That got my msys2 up to date.

Thanks, but it's a little too late now.

[JonyP27]

After I compiled the lastest v17 using this guide I cannot run the resulting .exe file and it gives the following errors:

"The procedure entry point _divmoddi4 could not be located in the DLL (dynamic-link library) C:\msys64\home\[user]\pcem\pcem.exe"
"The procedure entry point _divmoddi4 could not be located in the DLL (dynamic-link library) C:\msys64\home\[user]\pcem\libopenal-1.dll"

These errors appear even after copying all the necessary .dll files from the msys64 bin folder itself. Maybe it has to do with the OpenAL lib?

[JonyP27]

Nvm, I updated MSYS2's files and copied the libraries again to the executable folder and it worked. There were libraries that wouldn't work and didn't have to do with the OpenAL one, I think.