Hi Evan, The macro is not set in the chicken-config.h file.
I think the easiest way to test would probably to start with a pre-installed virtual image. Instruction from https://www.debian.org/ports/hurd/hurd-install: You can also get a pre-installed image and run it in qemu: $ wget https://cdimage.debian.org/cdimage/ports/current-hurd-i386/debian-hurd.img.tar.gz $ tar xzf debian-hurd.img.tar.gz $ kvm -m 1G -drive file=$(echo debian-hurd*.img),cache=writeback I'll try to look into why it's not writing the macro definition into the generated chicken-config.h file. *Andrew Eggenberger* On Sun, Oct 18, 2020 at 11:32 PM Evan Hanson <[email protected]> wrote: > Hi Andrew, > > > This is confusing because it looks like SEARCH_EXE_PATH is defined to 1 > in > > Makefile.hurd. > > Interesting. Can you confirm that macro is defined in the generated > chicken-config.h file? > > What's the easiest way to run GNU Hurd on another Linux (e.g. Debian), > to reproduce? I used to test Hurd builds with Vagrant, but the base box > went away a few years ago and I don't know of another way to test this. > > Cheers, > > Evan >
