Re: [Chicken-users] Hypergiant egg install fails, and some other eggs

[Robert Herman]

I saw the compilation failed, and other errors, and the ellipses hint at yet more trace information, but my original question is really about some eggs installing, and a variety of others failing on Windows. I will try them on my Linux box to see if I have similar issues with library locations, and it may teach me something about getting it working on Windows. Termbox is just one of the eggs that fail for me on Windows. I solved other failures due to missing dlls needed on Windows. Maybe Termbox is too reliant on a linux terminal as the target, but how come Blas fails, when I have the Blas libraries installed, and working in other language implementations? The Blas CHICKEN egg fails with the same 'setup-api' error at the end. Is the 'setup-api' the beginning of the trace for all failed setups? I will try and see why other eggs fail and look into tracing them, and share what I find. I really want to be able to make CHICKEN my platform on Windows. Thanks for the help.

Rob

On 2 October 2015 at 17:29, Peter Bex <address@hidden> wrote:

On Fri, Oct 02, 2015 at 11:08:09AM +0800, Robert Herman wrote:
> BTW, here is the log from just trying to install Termbox with no
> dependencies to compare with the Hypergiant log. I'm wondering if it might
> be the forward slashes in the change to current directory in the second
> line below? However, it seems to be missing or has a faulty 'setup-api'
> extension per the last lines:

You are looking too far down!  The real error occurs sooner:

> installing termbox:v0.11 ...
> changing current directory to
> C:\Users\Robert\AppData\Local\Temp/tempb606.13000/
> termbox
>   "c:\chicken-iup\bin\csi" -bnq -setup-mode -e "(require-library
> setup-api)" -e
> "(import setup-api)" -e "(setup-error-handling)" -e
> "(extension-name-and-version
>  '(\"termbox\" \"v0.11\"))" "termbox.setup"
>   "c:\chicken-iup\bin\csc" -feature compiling-extension -setup-mode    -s
> -O3 -d
> 1 utf8.c ctermbox.c termbox.scm -j termbox
> ctermbox.c:9:23: fatal error: sys/ioctl.h: No such file or directory
> compilation terminated.

^^^^^^ This is the real reason it's failing.

I suppose ioctl is too much of a UNIXism to work on Windows.  And that
kind of makes sense, because terminals are very much a UNIX thing.
I wouldn't expect termbox to work on Windows because it doesn't really
have the concept of a terminal, except for CMD.COM, but that works in a
way that's much different from a UNIX terminal.

> Error: shell command terminated with non-zero exit status 1: ""gcc"
> "ctermbox.c"
>  -o "ctermbox.o" -c  -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H
> -DC_EN
> ABLE_PTABLES -Os -DPIC -DC_SHARED -Ic:\\chicken-iup\\include
> -Ic:\\chicken-iup\\
> lib\\include -I"c:\chicken-iup/include/chicken/""
>
> Error: shell command failed with nonzero exit status 1:
>
>   "c:\chicken-iup\bin\csc" -feature compiling-extension -setup-mode    -s
> -O3 -d
> 1 utf8.c ctermbox.c termbox.scm -j termbox
>
>
> Error: shell command terminated with nonzero exit code
> 70
> "\"c:\\chicken-iup\\bin\\csi\" -bnq -setup-mode -e \"(require-library
> setup-api)
> \"...

I guess the reason this shows up at the end is because that was the
original command that failed.  The "..." indicates that more code is
there, but it has been elided.  That would be the setup-file from the
termbox egg.

Basically, you'd have to do the same as with C code: look for the
first error in the output. The rest of the failing output is just
a result of cascading down (or up) the error.

Cheers,
Peter