>tfw have a new, empty 2TB surveillance drive
>itching to play some PS2 games but the faggy dev team decided against supporting 64 bit linux
>not in the mood to run a custom 32 bit chroot
>Only option feels like ruining that drive by installing windows on it
Should I do it?
Which retarted distro you're using does not support 32bit libs in parallel???
you can probably figure this out yourself user
I'm using debian Jessie.
pcsx2/PCSX2-1.4.0$ ./P*2
./PCSX2: error while loading shared libraries: libwx_gtk2u_core-3.0.so.0: cannot open shared object file: No such file or directory
losing hope desu
>itching to play some PS2 games but the faggy dev team decided against supporting 64 bit linux
How does either linux or the dev team fuck up so hard to not support 64bit, or have it easy to support?
It works fine here on opensuse TW and Leap.
Looks like you should install some packages...
# aptitude install libwxgtk3.0-0:i386
The following NEW packages will be installed:
glib-networking:i386{a} libatk-bridge2.0-0:i386{a} libatk1.0-0:i386{ab} libatspi2.0-0:i386{a} libavahi-client3:i386{a} libavahi-common-data:i386{a}
libavahi-common3:i386{a} libcairo-gobject2:i386{a} libcairo2:i386{a} libcanberra-gtk3-0:i386{a} libcanberra-gtk3-module:i386{a} libcanberra0:i386{a}
libcolord2:i386{a} libcups2:i386{a} libdatrie1:i386{a} libfontconfig1:i386{a} libfreetype6:i386{a} libgdk-pixbuf2.0-0:i386{a} libgraphite2-3:i386{a}
libgtk-3-0:i386{ab} libgtk2.0-0:i386{a} libharfbuzz0b:i386{ab} libjasper1:i386{a} libjbig0:i386{a} libjpeg62-turbo:i386{a} libjson-glib-1.0-0:i386{a}
liblcms2-2:i386{a} libltdl7:i386{a} libnotify4:i386{a} libpango-1.0-0:i386{ab} libpangocairo-1.0-0:i386{ab} libpangoft2-1.0-0:i386{ab} libpixman-1-0:i386{a}
libpng12-0:i386{a} libproxy1:i386{a} librest-0.7-0:i386{a} libsoup-gnome2.4-1:i386{a} libsoup2.4-1:i386{a} libsqlite3-0:i386{a} libtdb1:i386{a} libthai0:i386{ab}
libtiff5:i386{a} libudev1:i386{a} libvorbisfile3:i386{a} libwayland-client0:i386{ab} libwayland-cursor0:i386{ab} libwxgtk3.0-0:i386 libxcb-render0:i386{a}
libxcb-shm0:i386{a} libxcomposite1:i386{a} libxcursor1:i386{a} libxinerama1:i386{a} libxkbcommon0:i386{ab} notification-daemon:i386{ab}
0 packages upgraded, 54 newly installed, 0 to remove and 8 not upgraded.
Need to get 16.5 MB/17.0 MB of archives. After unpacking 50.8 MB will be used.
The following packages have unmet dependencies:
libatk1.0-0 : Breaks: libatk1.0-0:i386 (!= 2.22.0-1) but 2.14.0-1 is to be installed.
libatk1.0-0:i386 : Depends: libatk1.0-data:i386 (= 2.14.0-1) which is a virtual package.
Breaks: libatk1.0-0 (!= 2.14.0-1) but 2.22.0-1 is installed.
libpango-1.0-0 : Breaks: libpango-1.0-0:i386 (!= 1.40.3-3) but 1.36.8-3 is to be installed.
libpango-1.0-0:i386 : Breaks: libpango-1.0-0 (!= 1.36.8-3) but 1.40.3-3 is installed.
libxkbcommon0 : Breaks: libxkbcommon0:i386 (!= 0.7.0-1) but 0.4.3-2 is to be installed.
libxkbcommon0:i386 : Breaks: libxkbcommon0 (!= 0.4.3-2) but 0.7.0-1 is installed.
libpangocairo-1.0-0 : Breaks: libpangocairo-1.0-0:i386 (!= 1.40.3-3) but 1.36.8-3 is to be installed.
libpangocairo-1.0-0:i386 : Breaks: libpangocairo-1.0-0 (!= 1.36.8-3) but 1.40.3-3 is installed.
notification-daemon : Conflicts: notification-daemon:i386 but 0.7.6-2 is to be installed.
notification-daemon:i386 : Conflicts: notification-daemon but 0.7.6-2 is installed.
libthai0 : Breaks: libthai0:i386 (!= 0.1.26-1) but 0.1.21-1 is to be installed.
libthai0:i386 : Breaks: libthai0 (!= 0.1.21-1) but 0.1.26-1 is installed.
libharfbuzz0b : Breaks: libharfbuzz0b:i386 (!= 1.2.7-1+b1) but 0.9.35-2 is to be installed.
libharfbuzz0b:i386 : Breaks: libharfbuzz0b (!= 0.9.35-2) but 1.2.7-1+b1 is installed.
libwayland-cursor0 : Breaks: libwayland-cursor0:i386 (!= 1.12.0-1) but 1.6.0-2 is to be installed.
libwayland-cursor0:i386 : Breaks: libwayland-cursor0 (!= 1.6.0-2) but 1.12.0-1 is installed.
libpangoft2-1.0-0 : Breaks: libpangoft2-1.0-0:i386 (!= 1.40.3-3) but 1.36.8-3 is to be installed.
libpangoft2-1.0-0:i386 : Breaks: libpangoft2-1.0-0 (!= 1.36.8-3) but 1.40.3-3 is installed.
libgtk-3-0 : Breaks: libgtk-3-0:i386 (!= 3.22.5-1) but 3.14.5-1+deb8u1 is to be installed.
libgtk-3-0:i386 : Breaks: libgtk-3-0 (!= 3.14.5-1+deb8u1) but 3.22.5-1 is installed.
libwayland-client0 : Breaks: libwayland-client0:i386 (!= 1.12.0-1) but 1.6.0-2 is to be installed.
libwayland-client0:i386 : Breaks: libwayland-client0 (!= 1.6.0-2) but 1.12.0-1 is installed.
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) libatk-bridge2.0-0:i386 [Not Installed]
2) libatk1.0-0:i386 [Not Installed]
3) libcanberra-gtk3-0:i386 [Not Installed]
4) libcanberra-gtk3-module:i386 [Not Installed]
5) libgtk-3-0:i386 [Not Installed]
6) libgtk2.0-0:i386 [Not Installed]
7) libharfbuzz0b:i386 [Not Installed]
8) libpango-1.0-0:i386 [Not Installed]
9) libpangocairo-1.0-0:i386 [Not Installed]
10) libpangoft2-1.0-0:i386 [Not Installed]
11) libthai0:i386 [Not Installed]
12) libwayland-client0:i386 [Not Installed]
13) libwayland-cursor0:i386 [Not Installed]
14) libwxgtk3.0-0:i386 [Not Installed]
15) libxkbcommon0:i386 [Not Installed]
16) notification-daemon:i386 [Not Installed]
Leave the following dependencies unresolved:
17) libnotify4:i386 recommends notification-daemon:i386
Accept this solution? [Y/n/q/?]
Option 17.
>this is your life
you can not select option 17, you can only select them all.
Holy shit, I was watching a WebM comp as background noise and this exact WebM played as I saw it in this thread. What does this mean?
Just emulate it, fgt.
Looking for meaning in coincidental events is a sign of mental frailty.
Ok, that's dumb.
I'm too used to zypper's way of dependency handling, it looks the same but you can select which option to use.
the inability to detect sarcasm is a sign of mental frailty.
>itching to play some PS2 games but the faggy dev team decided against supporting 64 bit linux
Can you not run 32bit application on 64bit linux?
That's not even something I have to think about on Windows.
You can. Every normal distro has it enabled by default but special snowflake muh
fuck no, that's not the problem. I can't install the i386 packages without replacing the amd64 packages.
otherwise, I could run it in a chrooted 32 bit session.
Get the source code and add 64bit support
Lol
if only it was so easy
I was in the same boat as you are now.
I just gave up, bought a used PS2 with a matrix 2.0 chip and a HDMI adaptor, made a share with samba, and now I play may gaymens over Lan. It's not the best, but I feel pretty comfy playing on a ps2.
*My
In Arch it's as easy as enabling multi-lib and issuing an update ;^) Why make things harder for yourself by using debian?
It'snot the same thing, you faggot. Debian has multi-lib too but I odn't want the hassl eof setting up a chrooted session to play games. I'd ratehr install iwndows.
Is there nay way to root a ps2 without a physical chip?
>Unironically using arch
Wew lad, I prefer not to use arch and play in my ps2
Not that I am aware of. And to play over lan(or a USB stick) you will need to install OPL on a memory car(or just buy one with it pre installed)