Error loading PHP 5.5 Module into Apache 1.3 (OpenBSD version) on OpenBSD 5.6 platform
I found the issue and the solution. After investigating my configuration further I noticed I had the Apache 2 version of PHP installed (php-5.5.14p0-ap2) instead of the correct 1.x one (php-5.5.14p0). APR in the 1.x versions of Apache uses "ap_" instead of "apr_" in their method signatures which was the...
cwm window manager - extend “exec program” search path with custom directories
I just tested it and it works fine for me, although I use ksh and not zsh but that shouldn't matter. A few things to look out for: your script has to be executable setting the PATH manually in an xterm while already running cwm won't work, because export only...
What to do after make test fails?
You may want to try using a slightly older version of apr; perhaps one from an OpenBSD packages site (somewhere like this OpenBSD Packages site?) Note: any downloads and installations that you choose to make from sites like these are your decision. Please make sure to read related documentation for...
zsh: command not found: bundle (after gem install bundle)
You can check the directory in which Rubygems will install gem executables with gem environment. One of the first points should be EXECUTABLE DIRECTORY. Make sure this directory is in your $PATH (listed as SHELL PATH btw)...
OpenBSD unable to install therubyracer gem ERROR: Failed to build gem native extension
ruby-on-rails,ruby,rubygems,bundler,openbsd
I was unable to install therubyracer gem in OpenBSD. As a workaround, i have installed nodejs as javascript runtime using OpenBSD package manager. pkg install node and removed therubyracer gem from Gemfile. Then bundle install works fine without any issue....
IPC with imsg? OpenBSD and Linux compatibility?
A quick look at the build script shows the following three files: compat/imsg-buffer.c compat/imsg.c compat/imsg.h So the tmux authors ship a copy of OpenBSD's imsg library, which is implemented entirely in user-space....
Why does this assembly program produce no output?
Since you tag x86_64 and probably are on an x86_64 system. Therefore you need to: as --64 use pushq instead of pushl to push 64bit values on the stack transfer those values to the appropriate registers before syscall .section ".note.opensd.ident", "a" .p2align 2 .long 0x8 .long 0x4 .long 0x1 .ascii...