The state of Meld on Macs is currently in flux. TLDR: currently, the best
way to run Meld is to install Homebrew and then run
brew install dehesselle-meld.
Update 2025-04-21: Starting today, it seems that Homebrew renamed the
dehesselle-meld cask to just meld, https://formulae.brew.sh/cask/meld.
So, brew install --cask meld should work (possibly after updating
Homebrew), and simple brew install meld might work too.
| ### Test on https://github.com/yousseb/meld/releases/tag/osx-20 | |
| ### OSX - 3.21.0 (r4) Sonoma | |
| ### !!! Note: You need put the Meld.app r4 build to the /Applications path first. | |
| #!/bin/zsh | |
| #Fix libpng16.16.dylib not found | |
| install_name_tool -change /usr/local/opt/libpng/lib/libpng16.16.dylib @executable_path/../Frameworks/libpng16.16.dylib /Applications/Meld.app/Contents/Frameworks/libfreetype.6.20.0.dylib | |
| #Fix libbrotlidec.1.dylib not found |
| #!/usr/bin/env bash | |
| brew install openssl | |
| git clone git://anongit.mindrot.org/openssh.git | |
| cd openssh | |
| # The './configure' script does not exist, so we have to build it | |
| autoreconf |
In general, check the crt/host_config.h file to find out which versions are supported.
Sometimes it is possible to hack the requirements there to get some newer versions working, too :)
Thrust version can be found in $CUDA_ROOT/include/thrust/version.h.
Download Archives: https://developer.nvidia.com/cuda-toolkit-archive
Release notes for CUDA Toolkit (CTK):
| # If you're looking into the C10M problem (10 million concurrent connections) | |
| # you might want to play with DPDK (Originally proprietry Intel, now open source) | |
| # | |
| # C10M: http://c10m.robertgraham.com/ | |
| # DPDK: http://dpdk.org/ | |
| # | |
| # This is a quick summary how to install dpdk on ubuntu | |
| # running inside virtualbox on a mac | |
| # On my Mac: |
| A non-maskable interrupt (NMI) is an interrupt type which differs from standard interrupt mechanism by enforcing attention from the interrupt processor (usually the CPU). This solution discusses an NMI is in more depth and how they are handled. | |
| ### What is an Interrupt ? ### | |
| Modern systems architecture has created tightly coupled connect between system components. Work for components can be handed off to a component for completion. Rather than wait for the component the main CPU can be tasked to do other pending work. | |
| When the component has completed its work it will raise a signal to the main processor. The main processor considers this signal an "interrupt", as the current work on the CPU will be interrupted immediately Each component has a number assigned to it. | |
| ### Why "mask" an interrupt ? ### |