Package Details: epsxe 2.0.5-31

Git Clone URL: https://aur.archlinux.org/epsxe.git (read-only, click to copy)
Package Base: epsxe
Description: Enhanced PSX emulator
Upstream URL: https://epsxe.com
Keywords: emulator playstation
Licenses: unknown
Conflicts: bin32-epsxe
Submitter: None
Maintainer: hav3lock
Last Packager: hav3lock
Votes: 229
Popularity: 0.120522
First Submitted: 2007-05-02 16:59 (UTC)
Last Updated: 2023-07-22 01:14 (UTC)

Pinned Comments

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 32 Next › Last »

Konzertheld commented on 2020-04-27 19:13 (UTC)

@hav3lock Confirmed. Thanks for the change!

hav3lock commented on 2020-04-27 19:05 (UTC)

@tallero Issues with the actual emulator itself should be reported to upstream. I only maintain the AUR package for epsxe.

hav3lock commented on 2020-04-27 19:02 (UTC)

Epsxe no longer requires ncurses5-compat-libs. This package also now supports i686 again.

Konzertheld commented on 2020-04-27 16:44 (UTC)

Workaround: Build ncurses5-compat-libs yourself.

  1. Clone the ncurses5-compat-libs git repository
  2. Check out this commit https://aur.archlinux.org/cgit/aur.git/commit/?h=ncurses5-compat-libs&id=4c625da1deb571feda59661b36af3eb7f68c19a9
  3. Run makepkg -si
  4. Install epsxe

caesarhenrique commented on 2020-04-24 12:43 (UTC)

so....

$ epsxe

/opt/epsxe/epsxe: /usr/lib/libncurses.so.5: version `NCURSES_5.0.19991023' not found (required by /opt/epsxe/epsxe)

/opt/epsxe/epsxe: /usr/lib/libcurl.so.3: no version information available (required by /opt/epsxe/epsxe)

aki42 commented on 2020-04-23 14:24 (UTC) (edited on 2020-04-23 14:30 (UTC) by aki42)

Same as A.J like below.

$ epsxe

/opt/epsxe/epsxe: /usr/lib/libncurses.so.5: version `NCURSES_5.0.19991023' not found (required by /opt/epsxe/epsxe)

/opt/epsxe/epsxe: /usr/lib/libcurl.so.3: no version information available (required by /opt/epsxe/epsxe)

A.J commented on 2020-04-22 10:24 (UTC)

not working with the latest ncurses5-compat-libs

ZimbiX commented on 2020-04-05 02:57 (UTC) (edited on 2020-04-05 03:05 (UTC) by ZimbiX)

Curiously, I'm getting an error from the find command:

find: The current directory is included in the PATH environment variable, which is insecure in combination with the -execdir action of find. Please remove the current directory from your $PATH (that is, remove ".", doubled colons, or leading or trailing colons)

My $PATH doesn't have anything like that, so that's confusing.

I don't need the docs, so I just commented out the find and then it builds fine.

Edit: Nevermind; user error! I was removing paths programmatically to avoid other path complaints from find, and didn't realise I was ending up with a trailing colon. Here's what worked:

PATH=$(echo -n $PATH | tr : '\n' | grep -vE '(~|/home)' | sed -z '$ s/\n$//' | tr '\n' :) yay -S epsxe

tallero commented on 2020-01-26 04:19 (UTC)

crashing on "Generator room" in Crash Bandicoot.

hav3lock commented on 2019-03-18 06:48 (UTC)

@dodd73 Of course! :)

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 32 Next › Last »