Hi again,
It looks like the problem is with the debian/rules file. It sets
PLATFORM=linux. When I change it to PLATFORM=hurd. SEARCH_EXE_PATH is in
chicken-config.h as expected and dpkg-build -B succeeds. It seems to be
portable if I set PLATFORM=$(shell dpkg-architecture -q DEB_TARGET_ARCH_OS)
in
Hey Andrew,
On 2020-10-19 19:29, Andrew Eggenberger wrote:
> 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
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://c
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
Hi,
I noticed Chicken 5.2.0 is now failing to build as a debian package on Gnu
Hurd with the error.
runtime.c: In function 'C_resolve_executable_pathname':
runtime.c:12849:3: error: #error "Please either define SEARCH_EXE_PATH in
Makefile. or implement C_resolve_executable_pathname for your
platf
