When running the Dolphin emulator from the stable Debian repos in Debian 12 with KDE I get the below error. However, no error is shown on a nearly identical machine where Dolphin emulator works fine. I already tried removing and then reinstalling dolphin-emu but I still get the same error. libllvm13 is the oldest version that is available in the repos. Installing that didn't help. There is no llvm-libs in the repos that's recommended in another question similar to this. It looks like in the machine where it works I have llvm11 installed locally (not from the repos) but llvm is not in the Debian repos. Bug report 1 When I run env QT_QPA_PLATFORM=xcb dolphin-emu it shows: dolphin-emu: error while loading shared libraries: libLLVM-11.so.1: cannot open shared object file: No such file or directory Update: it does work in Lutris (if the environment variable is configured in the Dolphin settings) so that's a workaround as is [compiling Dolphin](https://github.com/dolphin-emu/dolphin/wiki/Building-for-Linux) . Update: after updating the Dolphin runner in Lutris the Dolphin runner doesn't work anymore either: it shows this in the console: /home/username/.local/share/lutris/runners/dolphin/dolphin-emu: error while loading shared libraries: libavformat.so.60: cannot open shared object file: No such file or directory and I only have the .59 package . That's probably a bug in Lutris (?). Dolphin can be started when changing the executable to /usr/games/dolphin-emu in the Lutris settings for Dolphin.

When I run the PCSX2 runner in Lutris I get this error in the console and PCSX2 doesn't launch:

PCSX2: error while loading shared libraries: libwx_baseu-3.0.so.0: cannot open shared object file: No such file or directory

How do I get this libwx_baseu-3.0? Using Debian 12 with KDE. wxgtk3.2-1 is installed. Update: it works after **disabling "Disable Lutris Runtime" in the runner options for PCSX2**. Update: Maybe that was because I had PCSX2 installed so after it's working again I tried removing that with sudo dpkg --remove PCSX2 but it still shows this error when reenabling the aforementioned option. This filename search in Debian12 shows that the library is contained in libwxbase3.2-1 (which I have installed) but it's at version 3.2.so.0 there. I then tried uninstalling the runner, restarting lutris, then reinstalling the pcsx2 runner. It again doesn't launch if the aforementioned option is not disabled but now with error /tmp/.mount_[uid]/usr/bin/pcsx2-qt: /lib/x86_64-linux-gnu/libQt6Core.so.6: version 'Qt_6.5' not found (required by /tmp/.mount_[uid]/usr/bin/pcsx2-qt). When I disable the option again it does run again but it looks different than before. Previously it was a smaller window with the white pcsx2 image in the background now it looks newer (v1.7.4452) with the Wayland icon on the window. Maybe it's because of X11 to Wayland things. It does work with that option disabled but it should work by default without having to guess which option to change and I don't know why this problem occurred and whether disabling that option has any downsides.

The terminal emulator used in kali-linux is very convenient to use. How to check current terminal emulator name. How to install this emulator in ubuntu/debaian other linux distro.

I was able to get a remote viewer set up on my mac to remote view a Fedora server desktop. I run ~/android-studio/bin/studio.sh to launch Android Studio. I open AVD manager and try to boot up an emulator, but I get message > AVD is allready runing ... and when I try to boot emulator device1 from command line emulator -avd device1 I get message >emulator: ERROR: Running multiple emulators with the same AVD is an experimental feature. Please use -read-only flag to enable this feature. so overwhelming evidence is that device1 emulator is already running, and yet when I run command adb devices I get messages >List of devices attached indicating no running devices ... so whats up? **edit** I delete all *.lock files, and press play; the dialog did not appear, however, the emulator also did not appear, but when I ran adb devices, no devices were shown, and then I pressed play again, I got the same dialog. **edit** I create new device and booted from command line and got $ emulator -avd device3 Warning: QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled ((null):0, (null)) emulator: INFO: QtLogger.cpp:66: Warning: QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled ((null):0, (null)) failed to create drawable failed to create drawable failed to create drawable failed to create drawable failed to create drawable failed to create drawable failed to create drawable failed to create drawable getGLES2ExtensionString: Could not make GLES 2.x context current!

I recently discovered [waydroid](https://github.com/waydroid) to easily integrate android apps into my linux laptop. However [it doesn't support bluetooth](https://github.com/waydroid/waydroid/issues/155) . So is there any workaround such to make waydroid work with bluetooth. Or is there any alternative to waydroid which supports bluetooth? By "supports bluetooth" I mean that I could connect to any bluetooth device as if android was running on a native smartphone (the actual sending and receiving is handled by the bluetooth device of the laptop by sure).

I've followed [Waydroid arch-wiki page](https://wiki.archlinux.org/title/Waydroid#Installation) and have installed waydroid, binder_linux-dkms and waydroid-image-gapps. When I run waydroid it works perfectly except for the network part. I do have new interfaces on host machine: 30: waydroid0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:16:3e:00:00:02 brd ff:ff:ff:ff:ff:ff inet 192.168.240.1/24 brd 192.168.240.255 scope global waydroid0 valid_lft forever preferred_lft forever inet6 fe80::216:3eff:fe00:1/64 scope link valid_lft forever preferred_lft forever 31: vethbrQLNw@if2: mtu 1500 qdisc noqueue master waydroid0 state UP group default qlen 1000 link/ether fe:3e:17:46:42:95 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 fe80::fc3e:17ff:fe47:4295/64 scope link valid_lft forever preferred_lft forever but I don't have properly configured network interfaces in waydroid shell 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0@if31: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:16:3e:f9:d3:03 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 fe80::fba7:3c32:8e2f:857/64 scope link stable-privacy valid_lft forever preferred_lft forever So when I try to ping 1.1.1.1 I catch an error: connect: Network is unreachable. And I have no network inside wayland. I don't have ufw or firewalld installed. I've tried: 1. Restart waydroid-container.service 2. Stop nftables.service 3. Restart iptables.service P.S. I have following in journalctl: окт 27 15:16:53 nous dnsmasq: started, version 2.87 cachesize 150 окт 27 15:16:53 nous dnsmasq: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP con> окт 27 15:16:53 nous dnsmasq-dhcp: DHCP, IP range 192.168.240.2 -- 192.168.240.254, lease time 1h окт 27 15:16:53 nous dnsmasq-dhcp: DHCP, sockets bound exclusively to interface waydroid0 окт 27 15:16:53 nous dnsmasq: reading /etc/resolv.conf окт 27 15:16:53 nous dnsmasq: using nameserver 127.0.0.1#53 окт 27 15:16:53 nous dnsmasq: read /etc/hosts - 148944 addresses (127.0.0.1 is because I have unbound installed) waydroid log output: (138954) [15:16:45] % chmod 666 -R /dev/binder (138954) [15:16:45] % chmod 666 -R /dev/anbox-vndbinder (138954) [15:16:45] % chmod 666 -R /dev/anbox-hwbinder (138954) [15:16:45] Container manager is waiting for session to load (139008) [15:16:52] Save session config: /var/lib/waydroid/session.cfg (139008) [15:16:52] UserMonitor service is not even started (139008) [15:16:52] Clipboard service is not even started (138954) [15:16:52] % /usr/lib/waydroid/data/scripts/waydroid-net.sh start vnic is waydroid0 (138954) [15:16:53] % mount /usr/share/waydroid-extra/images/system.img /var/lib/waydroid/rootfs (138954) [15:16:53] % mount -o remount,ro /usr/share/waydroid-extra/images/system.img /var/lib/waydroid/rootfs (138954) [15:16:53] % mount /usr/share/waydroid-extra/images/vendor.img /var/lib/waydroid/rootfs/vendor (138954) [15:16:53] % mount -o remount,ro /usr/share/waydroid-extra/images/vendor.img /var/lib/waydroid/rootfs/vendor (138954) [15:16:53] % mount -o bind /var/lib/waydroid/waydroid.prop /var/lib/waydroid/rootfs/vendor/waydroid.prop (138954) [15:16:53] Save config: /var/lib/waydroid/waydroid.cfg (138954) [15:16:53] % mount -o bind /home/user/.local/share/waydroid/data /var/lib/waydroid/data (138954) [15:16:53] % chmod 777 -R /dev/ashmem (138954) [15:16:53] % chmod 777 -R /dev/dri (138954) [15:16:53] % chmod 777 -R /dev/fb0 (138954) [15:16:53] % chmod 777 -R /dev/video3 (138954) [15:16:53] % chmod 777 -R /dev/video2 (138954) [15:16:53] % chmod 777 -R /dev/video1 (138954) [15:16:53] % chmod 777 -R /dev/video0 (138954) [15:16:53] % lxc-start -P /var/lib/waydroid/lxc -F -n waydroid -- /init (138954) [15:16:53] New background process: pid=139115, output=background (138954) [15:16:53] Save session config: /var/lib/waydroid/session.cfg (139008) [15:17:02] waydroidusermonitor: Received transaction: 1 (139008) [15:17:02] Android with user 0 is ready (146313) [15:40:48] % tail -n 60 -F /var/lib/waydroid/waydroid.log (146313) [15:40:48] *** output passed to waydroid stdout, not to this log ***

I'm a Linux newbie. I recently installed Pop!_OS 22.04 because of its hybrid graphic driver. The problem is that when I open the Android Studio emulator, the system audio starts to crackle and there is a ticking sound whether when the audio is played by the emulator or other applications. There are some backgrounds to this. I had been using the system like this for a month now and the problem got worse. Even when the emulator was not running, the audio crackling continued. Turns out, one of my speakers gave up (front-right), and I suspect this issue to be the culprit. I thought the problem was with the sound driver, so I tweaked and tried everything I found on the web, and I may have changed ALSA, PulseAudio, or PipeWire configs. Therefore, a full reset of sound drivers would be much appreciated. I believe providing the Android emulator config would also help: 1. RAM Size: 2048 MB 2. Heap Size: 228 MB 3. Multicore CPU: 4 Thanks.

**Does anyone know how to get libx86emu x86emu-demo to work?** https://github.com/wfeldt/libx86emu Test.bin 00000000 55 8B EC 51 C7 45 FC 00 00 00 00 8B 45 FC 50 E8 00000010 09 00 00 00 83 C4 04 33 C0 8B E5 5D C3 55 8B EC 00000020 B8 01 00 00 00 5D C3 00: 55 push ebp 01: 8b ec mov ebp,esp 03: 51 push ecx 04: c7 45 fc 00 00 00 00 mov DWORD PTR [ebp-0x4],0x0 0b: 8b 45 fc mov eax,DWORD PTR [ebp-0x4] 0e: 50 push eax 0f: e8 09 00 00 00 call 0x1d 14: 83 c4 04 add esp,0x4 17: 33 c0 xor eax,eax 19: 8b e5 mov esp,ebp 1b: 5d pop ebp 1c: c3 ret 1d: 55 push ebp 1e: 8b ec mov ebp,esp 20: b8 01 00 00 00 mov eax,0x1 25: 5d pop ebp 26: c3 ret ./x86emu-demo -l 0 -s 0 Test.obj I need to be able to execute x86 machine code similar to the above sample. libx86emu decodes and executes the first three instructions then decodes the fourth instruction incorrectly. I only need to be able to emulate 32-bit x86, I don't need any OS support. Only about half of the libx86emu x86test regression tests pass.

I have installed bottles for Windows application emulation. I am trying to start an application via command line but have not been able to start the application automatically. It opens up the bottle but the application does not start and it requires a manual start. I would like to get this to work so I can create a systemd service which launches this app on system boot. OS is AlmaLinux 8. Here's the variation of commands I have tried.

flatpak run com.usebottles.bottles -b NetSync -e 'C:\windows\system32\start.exe /wait C:\Program Files (x86)\BigNet\NetSync\NetSync.exe'
flatpak run com.usebottles.bottles -b NetSync -e 'C:\Program Files (x86)\BigNet\NetSync\NetSync.exe'
flatpak run com.usebottles.bottles -b NetSync -e '/home/rlee/.var/app/com.usebottles.bottles/data/bottles/bottles/NetSync/drive_c/Program Files (x86)/BigNet/NetSync/NetSync.exe'
flatpak run com.usebottles.bottles -b NetSync -e /home/rlee/.var/app/com.usebottles.bottles/data/bottles/bottles/NetSync/drive_c/Program\ Files\ \(x86\)/BigNet/NetSync/NetSync.exe

I'd like to play games on my computer with free software only. The graphics card driver should hence be free software too. I currently have a Nvidea GeForce GTX graphics card and thought about getting a new graphics card after selling it but to date couldn't find a simple list of benchmarked/compared graphics card that are confirmed to work with FOSS drivers under GNU/Linux (asked about it) . The best free driver for Nvidea graphics cards seems to be Nouveau and the graphics card I have is listed here under Code name 'NVE4 (GK104)' which is under Family 'NVE0'. According to this feature matrix , family NVE0 should be relatively well supported. (This also means it doesn't make much sense trying to swap the graphics card if things are supposed to work with that one.) However, it has many glitches and the emulator games I tried didn't work better than just the onboard of mainboard 'B250 PC MATE' as I described in this question . Maybe I installed it the wrong way, needed a newer version of Debian², needed to use Wayland instead of X11³ or missed installing something else such as some Vulkan-related packages. -> **How to get smoothly running emulator games with free software only on Debian/KDE with a Nvidea GeForce GTX graphics card?** If there are problems using the graphics card specifically for emulators on GNU/Linux with Nouveau (as suggested in the other question), which emulators are supposed to be compatible?4 Do I need to install or configure any additional things to a) prevent these glitches and b) make use of the graphics capabilities for emulators? --- ² now running latest Debian 11 stable (xserver-xorg-video-nouveau is v1:1.0.17-1 and KDE Plasma is v5.20.5) ³ I recently switched to Wayland despite the many bugs with it in Debian/KDE because beyond security-improvements it prevents screen tearing allowing me to properly watch videos 4 I tried the emulators Dolphin, PCSX2 and PCSX3 for Wii, PS2, PS3 and GameCube games within Lutris. Some of the games do work but have graphics-problems such as running only very slowly (including the audio).

This is copied from Reddit I'm just trying to find an answer to my problem. Thanks in advance for any suggestions or help! I'm running Ubuntu 22.04 on an old, Dell Latitude E6400 (it runs pretty well). I play a few various emulators and I prefer to use a controller (wired xbox one). It was running fine until the latest update (a day or two ago). Now, it will only work if it is plugged in when the system boots,. Otherwise, the system won't recognize it or power it (there is a little white indicator light that lights up when connected to the computer) . Is there anything that can be done to fix this? Update: Just tried using the controller after boot and it Ubuntu isn't recognizing the controller at all it just makes the little led light up. It worked fine until I updated everything. Update 2: Ran "lsusb" and its being recognized by Ubuntu but still isn't working. I checked the controller on a different emulator after boot and it does work (so the initial problem I was having was just the emulator) but if I unplug the controller and try to plug it back in it won't work, I have to restart the system. but it is still recognized in "lsusb" Update 3: I also ran "sudo modprobe xpad" and it did nothing. Forgot to mention that. Update 4: Last one I promise, I plugged in a different controller (still an xbox one) and it works just fine. I am beyond stumped by this. Also, I plugged in the controller to a Windows computer and it worked just fine. This is just crazy to me. It worked no problem up until a couple days ago. I'm probably going to just give up trying to figure this out if no one has any ideas.

I tried to run Mednafen runner on Lutris 5.9.1 on LM 20.3, unsuccessfully. Apparently it requires SDL library version at least 20.0.12. 20.0.10 is present in the system. I tried to install newer version from here . Installation process went well. Now, when type dpkg -l | grep sdl2 I get: ii libsdl2-2.0-0:amd64 2.0.10+dfsg1-3 amd64 Simple DirectMedia Layer ii libsdl2-2.0-0:i386 2.0.10+dfsg1-3 i386 Simple DirectMedia Layer ii libsdl2-dev:amd64 2.0.10+dfsg1-3 amd64 Simple DirectMedia Layer development files ii libsdl2-net-2.0-0:amd64 2.0.1+dfsg1-4 amd64 Network library for Simple DirectMedia Layer 2, libraries but when I type sdl2-config --version I get this: 2.0.20 Could anyone help me, the confused guy? Thank you.

I encountered a problem. A few i386 libraries are missing for PCSX2 runner to run in Lutris. Could anyone help me obtaining them, please? What should I do to install them? I found few similar topics on the web but none of them worked unfortunately. Some of them adviced installing standalone PCSX2 emulator but that would defeat a need for having such runner in Lutris on the first place.

## The Problem I'm trying to install this android emulator using snap. This is what I have done, so far: - installed anbox, following instructions in Snapcraft ; - installed kernel-devel; - tried to install kernel modules . Although, I was not able to install kernel modules because whenever I install kernel-devel it has a different version from my kernel. For example: - I have this kernel: 5.8.18-200.fc32.x86_64 - but kernel-devel has this version: 5.9.15-100.fc32.x86_64 And DKMS outputs this:

Your kernel headers for kernel 5.8.18-200.fc32.x86_64 cannot be found at
/lib/modules/5.8.18-200.fc32.x86_64/build or /lib/modules/5.8.18-200.fc32.x86_64/source.

--- ## Details -> In order to install anbox, I used this:

sudo snap install anbox --devmode --beta

-> In order to install kernel-devel, I am using this:

sudo dnf install kernel-devel

-> I have tried to install the correct headers using this command, as recommended in this other question :

sudo yum install "kernel-devel-uname-r == $(uname -r)"

-> Launching anbox doesn't work, even if I use this recommended command:

anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity

## Question Updates ### 1. Kernel mismatch I had to update my OS, to get the new kernel. There's no mismatch problem, anymore. Before @ajgringo619 hint, I was not able to update it because my dnf.conf had an install limit:

installonly_limit=1

This would result in this error:

Error: 
 Problem: The operation would result in removing the following protected packages: kernel-core
(try to add '--skip-broken' to skip uninstallable packages)

After changing dnf.conf, I was able to update my kernel and solve mismatch issues. ### 2. Unable to install anbox modules I'm still unable to install modules. Now, due to modpost error .

I had before in my machine running Windows 10, then I decided to switch back again to Arch Linux. Before installing Arch Linux I backed up my hidden Android directory that has AVD data directory which is located in: **C:\\Users\Khalid\\.android** After switching to Arch, I installed android emulator on it and added all the the required environment variables by the android emulator to .bashrc, these are the environment variables defined:

export EXTERNAL_DRIVE=/run/media/user12/EXTERN_DRIVE/Android
export ANDROID_HOME=/opt/android-sdk
export ANDROID_EMULATOR=$ANDROID_HOME/emulator
export ANDROID_EMULATOR_HOME=$EXTERNAL_DRIVE/.android/
export ANDROID_AVD_HOME=$ANDROID_EMULATOR_HOME/avd/
export ANDROID_TOOLS=$ANDROID_HOME/cmdline-tools/tools
export ANDROID_CMDLINE_TOOLS=$ANDROID_HOME/cmdline-tools/tools/bin
export ANDROID_PLATFORMS=$EXTERNAL_DRIVE/android-sdk/platforms
export ANDROID_PLATFORM_TOOLS=$ANDROID_HOME/platforms

After that I listed the available avds by executing the command: **avdmanager list avd** But I get an error:

The following Android Virtual Devices could not be loaded:
        Name: Nexus_5X_API_26_Google_Play
        Path: /run/media/user12/EXTERN_DRIVE/Android/.android/avd/Nexus_5X_API_26_Google_Play.ini
       Error: Corrupted AVD ini file: /run/media/user12/EXTERN_DRIVE/Android/.android/avd/Nexus_5X_API_26_Google_Play.ini
    ---------
        Name: Nexus_5_API_23_Marshmallow
        Path: /run/media/user12/EXTERN_DRIVE/Android/.android/avd/Nexus_5_API_23_Marshmallow.ini
       Error: Corrupted AVD ini file: /run/media/user12/EXTERN_DRIVE/Android/.android/avd/Nexus_5_API_23_Marshmallow.ini

I also tried to see if I am going to emulate the machine by doing: **emulator -avd Nexus_5X_API_26_Google_Play** But I got the following error:

PANIC: Cannot find AVD system path. Please define ANDROID_SDK_ROOT

Can anyone tell me what could be wrong about this or why I am I getting this error?

There is a game I want to run (I am on debian 4.9) but it is kind of sketch so I want to run it in some kind of emulator so it thinks it's the only thing on my machine so it can't delete my files or upload them to somewhere. If it's mining bitcoin or putting me in a botnet or whatever I don't care really as long as it only does that when the game is running. (When I close it it stops and it doesn't start except when I start it.) I was thinking of just setting all my read permissions to me only and running it under another user, but I'd also like to be able to use my computer and files like normal while it is running, so this isn't really a great solution. Also ideally I don't want this to lag out the game too much. How do I do this?

I have installed anbox. anbox version anbox 0.0~git20181014-1~bpo9+1-Debian Have a try to install an apk after downloading weixin7013android1640.apk. adb install weixin7013android1640.apk * daemon not running. starting it now on port 5037 * * daemon started successfully * error: no devices/emulators found Why no emulator found in my os?How to fix it? Do as @A.B suggested to follow official manual: official manual sudo wget https://build.anbox.io/android-images/2018/07/19/android_amd64.img -o /var/lib/anbox/android.img sudo systemctl start anbox-container-manager.service sudo systemctl status anbox-container-manager.service anbox-container-manager.service - Anbox Container Manager Loaded: loaded (/lib/systemd/system/anbox-container-manager.service; enabled; Active: active (running) since systemctl --user start anbox-session-manager.service systemctl --user status anbox-session-manager.service anbox-session-manager.service - Anbox Session Manager Loaded: loaded (/usr/lib/systemd/user/anbox-session-manager.service; disabled; vendor preset: enabled) Active: active (running) since Try it with one sample apk. wget https://f-droid.org/FDroid.apk adb install FDroid.apk Success. Now it is time to install the weixin apk. adb install weixin7013android1640.apk Failed to install weixin7013android1640.apk: Failure [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113] Please download the weixin apk from download weixin apk to install with adb in your debian https://dldir1.qq.com/weixin/android/weixin7013android1640.apk Every coder here install the weixin7013android1640.apk successfully with adb command on your debian,please paste all your steps ,i install it successfully following your steps ,then get 500 points for the issue.

I was trying to install pcsx 1.10 from source. After the configure step, make was executing until Utils.hpp:31:21: error: gtk/gtk.h: No such file or directory In file included from About.cpp:54: Utils.hpp:31:21: error: gtk/gtk.h: No such file or directory Then another one million of errors showed up. The file gtk.h is already present on: /usr/include/gtk-2.0/gtk/gtk.h Tried another time, this time changing the configuration to include the environment variables made to detect gtk files: ./configure --prefix=/media/34GB/Arquivos-de-Programas-Linux/Pcsx-df-1.10/ --enable-nautilusburn=false GTK2_CFLAGS=/usr/include/gtk-2.0/ GTK2_LIBS=/usr/lib/gtk-2.0/ This time the compilation process terminated with: /usr/bin/ld: /usr/lib/gtk-2.0/: No such file: File format not recognized collect2: ld returned 1 exit status Any suggestions?

I have been told to install VMWare ESX on the Solaris server, but I could not find resources about this issue on the web, how is that possible?

I tried to install mcu8051ide on Mac OSX, but I faced to some problem of package dependency. Please see the error message below. $ mcu8051ide --check-libraries MCU 8051 IDE v1.4.10 Checking libraries... 1/9 Checking for library BWidget Library present ... YES Version 1.8 ... YES 2/9 Checking for library Itcl Library present ... YES Version 3.4 ... YES 3/9 Checking for library md5 Library present ... YES Version 2.0 ... YES 4/9 Checking for library Tk Library present ... YES Version 8.5 ... YES 5/9 Checking for library img::png Library present ... NO ! Version 1.3 ... NO ! 6/9 Checking for library tdom Library present ... YES Version 0.8 ... YES 9/9 Checking for library Tcl Library present ... YES Version 8.2 ... YES RESULTS: Number of fails: 1 PROGRAM WILL NOT RUN, please install the missing libraries I tried to install the missing package by command: $ brew install homebrew/dupes/tcl-tk But it didn't seem to work. Then I tried to install it manually by went to tkimg website and download it. I unzip it and got several *dylib files. Honestly, I don't know how to deal with these kind of thing. Anyone has some more simple idea to get this done?