Re: [Chicken-users] Hypergiant egg install fails, and some other eggs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/10/15 11:09 AM, Peter Bex wrote: > On Sun, Oct 04, 2015 at 10:50:24AM -0600, Jeremy Steward wrote: >> I suppose as one of the few people who has used / uses CHICKEN >> on Windows I should chime in :) > > Thanks for this! > >> On 02/10/15 12:57 PM, Peter Bex wrote: >>> The reason behind this seems to be that Blas itself is a bit of >>> an old-fashioned library[...] >> >> BLAS is problematic not because it is old, but because it is >> made available through multiple implementations. For example, >> BLAS can be made available through Intel's MKL, ATLAS, OpenBLAS, >> and of course the original netlib.org reference implementation. >> Keep in mind BLAS is often implemented in Fortran and then >> exported to C, so depending on your implementation you might also >> need to expose `-lgfortran` to csc as well. > > Thanks for explaining this. It's good to know about that. Do > none of the BLAS implementation offer pkg-config support, though? > Even if you only support one BLAS library, it can still be > installed in several different locations, depending on the platform > and packaging system used. As far as I can tell, none of the ones I mentioned above do. The OpenBLAS guys would do it, but their issue tracker on Github suggested they don't know how to write pkg-config files [1]. As for Intel's MKL, it's proprietary. This means 1) I haven't utilized it much, and 2) I have never seen it play nice with FOSS tooling. It could very well export pkg-config bindings, but I doubt it. As for ATLAS and netlib BLAS, they both suffer from being maintained by a single developer who hasn't updated the software much (beyond architecture compatibility) in years. That isn't to say that ATLAS is out of date or bitrotted (it is in fact quite optimized and useful), but the code itself is robust and well-tested, and prioritizes platform compatibility over new features (IMO, I don't know or talk with the developer, but this is the impression I get). >> Agreed, please do not give up. Currently the way I use CHICKEN >> on Windows is through Cygwin, because it is currently the easiest >> way to install and link things (using plain MinGW64 is an >> exercise in patience, IMO). Hopefully the midipix project >> (http://midipix.org/) picks up, which will provide a much better >> way to use CHICKEN (and other C libraries / programs) on >> Windows. > > Wow, this Midipix project sounds very promising! Definitely > something to keep an eye on, so we can (eventually?) get rid of the > mess that is cygwin & mingw. > > Cheers, Peter > Indeed, it would be a great day when Windows is as easy to support as Linux or BSD! [1] https://github.com/xianyi/OpenBLAS/issues/598 - -- Jeremy Steward -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJWEWtRAAoJEHVwwAZUeZnZh8AQAKjGh/LqhSce/3gzWXSFeL8Z ESk7ttbO3qszc266w9gTFBpA6HGaloLawy+3/PfknHnbV8lvr24Thn/gikfx0ja/ L/9BpCKwr48eQelWmKVQdf5VPaAk2xk49tqhtqF0WMsUX6ppBeIiNMQH1F4EY074 M6iAZXfvdaxiuYx7i3hhKiNHiXuCWRDqEF8Uot10FIgbnvlF5wmJbbJjKXrYmX/R sa1JeUmLZYamSRbYP/PY0o+X/brnhWrYD5nrAcbZZeyWXPSYjQuvySk3DLXsly3+ YP0H3darVuQu5s81WNLDMm5xm6pGs2PbAFZy24YHHBuVtKG44gdPyGTAI5NeZL/V IDzsTWz80pD2mEkp5ll5pSn72giUofYo9ryYLL2oYhBeomqmv0x2kcmJdreHfjc7 6OCjoRNaIjzdfcu2kRZQBn/ZllWuNEPhxOKB296ptaWN8aBk3fX/ryDYF5S79KfW uwpsueOzHvnACvIesJD/7YmCde+Z20560nV8GBdiu8dJdpYCoQWY1wLrDCYhF1Z2 AS9jxUpkAMYjHsPWBFM5O3vifytpuJDvebLRhP6U9Eydgw+0Uz1M45NZzH/y7pLT 0KABXqWvHiBnwmaSN7wuJlwAIc7B3bAO4MCGPMXGYY4aEPRLsw8nCG8b/8FT2QU/ WiBsGMsp17ccdbQUkW4N =f0Rp -END PGP SIGNATURE- ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Hypergiant egg install fails, and some other eggs
On Sun, Oct 04, 2015 at 10:50:24AM -0600, Jeremy Steward wrote: > I suppose as one of the few people who has used / uses CHICKEN on > Windows I should chime in :) Thanks for this! > On 02/10/15 12:57 PM, Peter Bex wrote: > > The reason behind this seems to be that Blas itself is a bit of an > > old-fashioned library[...] > > BLAS is problematic not because it is old, but because it is made > available through multiple implementations. For example, BLAS can be > made available through Intel's MKL, ATLAS, OpenBLAS, and of course the > original netlib.org reference implementation. Keep in mind BLAS is > often implemented in Fortran and then exported to C, so depending on > your implementation you might also need to expose `-lgfortran` to csc > as well. Thanks for explaining this. It's good to know about that. Do none of the BLAS implementation offer pkg-config support, though? Even if you only support one BLAS library, it can still be installed in several different locations, depending on the platform and packaging system used. > Agreed, please do not give up. Currently the way I use CHICKEN on > Windows is through Cygwin, because it is currently the easiest way to > install and link things (using plain MinGW64 is an exercise in > patience, IMO). Hopefully the midipix project (http://midipix.org/) > picks up, which will provide a much better way to use CHICKEN (and > other C libraries / programs) on Windows. Wow, this Midipix project sounds very promising! Definitely something to keep an eye on, so we can (eventually?) get rid of the mess that is cygwin & mingw. Cheers, Peter signature.asc Description: Digital signature ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Hypergiant egg install fails, and some other eggs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I suppose as one of the few people who has used / uses CHICKEN on Windows I should chime in :) On 02/10/15 12:57 PM, Peter Bex wrote: > On Sat, Oct 03, 2015 at 02:29:35AM +0800, Robert Herman wrote: >> 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? > > Hard to say without more info. The Blas egg is a bit of a pain to > get working, even on *nix. It has its own attempt at > "auto-detection" of how it should invoke the compiler & linker, > which is quite error-prone and probably very Linux-oriented anyway. > The reason behind this seems to be that Blas itself is a bit of an > old-fashioned library, and doesn't have a way to discover how to > link against it (no pkg-config, for example). BLAS is problematic not because it is old, but because it is made available through multiple implementations. For example, BLAS can be made available through Intel's MKL, ATLAS, OpenBLAS, and of course the original netlib.org reference implementation. Keep in mind BLAS is often implemented in Fortran and then exported to C, so depending on your implementation you might also need to expose `-lgfortran` to csc as well. The "auto-detection" code is more or less attempting to figure out which BLAS library you're using, and tries to deduce which files to link into the build process. You can, for example, try the following: #include #include int main() { cblas_ddot(0, NULL, 0, NULL, 0); return 0; } You'll then want to compile this as follows: gcc test.c -o test -lm -lblas OR gcc test.c -o test -lm -lcblas If either of those work, you should be good to go with regards to installing BLAS automatically. Otherwise, you may need to figure out where libblas.dll or libcblas.dll reside and you'll need to expose those libraries in your INCLUDE path. If you're getting weird errors with blas or atlas-lapack, you can post here and I can try to help. I did some work with atlas-lapack earlier this year (and I mean to do more), but I've had good success with it on Windows thus far. >> 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. > > Don't give up! It's just that you're charting new territory; not > many people are currently using CHICKEN on Windows. Most egg > authors will be happy to patch their eggs to make things work, if > you can inform them what is needed to make things build on > Windows. Agreed, please do not give up. Currently the way I use CHICKEN on Windows is through Cygwin, because it is currently the easiest way to install and link things (using plain MinGW64 is an exercise in patience, IMO). Hopefully the midipix project (http://midipix.org/) picks up, which will provide a much better way to use CHICKEN (and other C libraries / programs) on Windows. I suppose midipix / musl-libc support should be it's own thread though. Cheers, - -- Jeremy Steward -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJWEVjOAAoJEHVwwAZUeZnZ31YP/jmwMZYQ0T7UjGdoZ5an1lXH NSBuEebN1888RzMbmNVe/nWLq/RhTrEZZpGJ4m4/IeWA09PBLSLEhe/E4JBAjV1d v3Rx5UlAUTSP4zh9rP4sZO9EV09X7xbTh2IoIjU3udyJ9SJv/XqHU0RyIsv4xmum EjNXoCOswBkfZLZ8ErsKUPyYWykS1F8vQ0QSxNoYdnfiDnhtfpNKV3w4+f6CUtKo QxHWzUf8UGT9My0PHd0ZMgqsxumuXTSZs9OTFEphjys4BOSz/ppVROe840Nj8GOb qutG0/ELRoEJoMcgBhNZSVXqFkvgRAkoB7U9iv5pc1e+5+qDgNKgUyqTxNdPH8pA DRskUMotAcwqjF5gSp6j04HikI7resIHzmshzyO+rT9Az6AervDereFIBCULzeTh D7/iwCjvEaDxUlFDt5nOeXA0APVSpzYYwKqKAnQQ3Mu7gNt18EzC0kuVmqakTAuC 4X6uKyoKFFUk7e16tQAyzfpzvrtpRVm4J/I2wBuRF+vmFlGObAWg1pPkdS+mIbsZ /v1VGiQxW3f7AHa2jiMHkj7lipqKOHCglD3dh9kpEJMdOHxFaZSRwA0EbxWoh/rm 5MCZ0VkikZC2FiVvnAqyqqUnk0dV9YY+0+SPcLR8Vr5RFETr1h2dgh6QzX+ZUSpO 87yk7FsY40OB1HW29Icj =YCKH -END PGP SIGNATURE- ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Hypergiant egg install fails, and some other eggs
On Sat, Oct 03, 2015 at 02:29:35AM +0800, Robert Herman wrote: > 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? Hard to say without more info. The Blas egg is a bit of a pain to get working, even on *nix. It has its own attempt at "auto-detection" of how it should invoke the compiler & linker, which is quite error-prone and probably very Linux-oriented anyway. The reason behind this seems to be that Blas itself is a bit of an old-fashioned library, and doesn't have a way to discover how to link against it (no pkg-config, for example). > 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? Yes, it is. The way chicken-install works is it loads a .setup-file, and prepends it with (require-extension setup-api). Again, if you want to know why it failed, look for the very first mention of an error in the output. I fully agree this is not ideal, and the error output could use some work to get better information. > 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. Don't give up! It's just that you're charting new territory; not many people are currently using CHICKEN on Windows. Most egg authors will be happy to patch their eggs to make things work, if you can inform them what is needed to make things build on Windows. > Thanks for the help. No problem! Cheers, Peter signature.asc Description: Digital signature ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Hypergiant egg install fails, and some other eggs
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 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 > ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Hypergiant egg install fails, and some other eggs
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 signature.asc Description: Digital signature ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Hypergiant egg install fails, and some other eggs
Thanks, for the quick response! I will do that. Termbox is small enough to work on to solve this issue. I did reinstall setup-helper egg again just in case. On 2 October 2015 at 11:12, Evan Hanson wrote: > On 2015-10-02 11:03, Robert Herman wrote: > > In any case, Termbox has not dependencies > > IIRC termbox bundles a C library (perhaps just one file?) that it compiles > during chicken-install. In that sense, it does have one dependency. It'd be > worth checking that, to see whether it makes some assumptions about the > platform, and whether it's compatible with your Windows environment. > > Cheers, > > Evan > ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Hypergiant egg install fails, and some other eggs
On 2015-10-02 11:03, Robert Herman wrote: > In any case, Termbox has not dependencies IIRC termbox bundles a C library (perhaps just one file?) that it compiles during chicken-install. In that sense, it does have one dependency. It'd be worth checking that, to see whether it makes some assumptions about the platform, and whether it's compatible with your Windows environment. Cheers, Evan ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Hypergiant egg install fails, and some other eggs
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: 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. 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) \"... C:\> On 2 October 2015 at 11:03, Robert Herman wrote: > Maybe Hypergiant was the wrong egg to use as example, because of all of > its dependencies. I installed GLFW and GLEW in Windows (SystemWOW64 > directory for 32-bit dlls), and in MinGW (c:\MinGW-32\ming32\bin > directory). I did a command in the MinGW command prompt to find out which > directories it searches, and the Windows version doesn't have a usr/bin or > usr/lib, so I put it there. > In any case, Termbox has not dependencies and it too fails with the > '(require-library setup-api)' at the end. > Unfortunately, I have to work on Windows for my company, and some family > members. I have a linux box, Mac and I am currently hacking a USB TV Stick > with an ARM processor. I am not tied to Windows, but I have to tell you, > CHICKEN has allowed me in one day to create fast, small executeables fairly > easy on Windows with a GUI (IUP), so I am hooked! Hypergiant looks exactly > what I was looking for per the video I watched of it. I'll keep hacking on > it to figure out the dependencies and loccation issues. I am a bit > concerned about the Termbox error though. Thanks, and great work! > > Rob > > On 2 October 2015 at 05:40, Alex Charlton > wrote: > >> Hi Robert, >> >> As it seems your goal is to get Hypergiant running on Windows, I have to >> let you know that you're venturing into uncharted territory. It's not >> something I've ever tried before! >> >> That said, there error that you've shared with us is fairly >> straight-forward: >> >> > ingw32/bin/ld.exe: cannot find -lglfw >> >> This is the source of the problem which is saying that it's not able to >> link to GLFW. This could mean that you don't have GLFW ( >> http://www.glfw.org/) installed in the right place (which could also be >> the case for other eggs that depend on external libraries) or that the egg >> itself is not linking to it correctly. The latter is certainly possible, >> since I don't think it's been tested on Windows before. >> >> If you want more help working through this, just send me an email. If you >> find that the egg is doing something wrong, I'm happy to patch it for you. >> Of course, if you want to continue conversing with this lovely mailing >> list, feel free to do that, too ;-) Maybe someone here has gotten >> Hypergiant running on Windows. >> >> Cheers, >> Alex >> >> On Thu, Oct 1, 2015 at 12:20 PM Robert Herman >> wrote: >> >>> I am running Windows 10, with MinGW-64 32-bit version, since I have the >>> Windows binary for CHICKEN-IUP which is 32-bit. Some eggs have installedj >>> fine - format, sql-de-lite, Spiffy, and other spiffy eggs, numbers, srfi's, >>> gl-math, awful, and awful-server, but others - blas, hypergiant, >>> hyperscene, and termbox fail with the same type of error - (require-library >>> setup-api). >>> I would like to be able to load blas, atlas-lapack, hypergiant, and >>> hyperscene for math and game dev. >>> I always run chicken-install, csi and csc from the MinGW command window. >>> Below is the last half of the log of my command line when trying to install >>> the hypergiant egg. I have installed glfw and glew on windows with paths >>> set outside of CHICKEN-IUP. Hypergiant has a lot of dependencies, but some >>> of the smaller eggs fail in a similar fashion. Any ideas? Thank you. >>> >>> HTTP/1.1 200 OK >>> Date: Thu, 01 Oct 2015 12:43:42 GMT >>> Server: Apache/2.2.29 (Unix) DAV/2 SVN/1.8.10 PHP/5.4.32 >>> mod_fastcgi/2.4.6 >>> Connection: close >>> Transfer-Encoding: chunked >>> Content-T
Re: [Chicken-users] Hypergiant egg install fails, and some other eggs
Maybe Hypergiant was the wrong egg to use as example, because of all of its dependencies. I installed GLFW and GLEW in Windows (SystemWOW64 directory for 32-bit dlls), and in MinGW (c:\MinGW-32\ming32\bin directory). I did a command in the MinGW command prompt to find out which directories it searches, and the Windows version doesn't have a usr/bin or usr/lib, so I put it there. In any case, Termbox has not dependencies and it too fails with the '(require-library setup-api)' at the end. Unfortunately, I have to work on Windows for my company, and some family members. I have a linux box, Mac and I am currently hacking a USB TV Stick with an ARM processor. I am not tied to Windows, but I have to tell you, CHICKEN has allowed me in one day to create fast, small executeables fairly easy on Windows with a GUI (IUP), so I am hooked! Hypergiant looks exactly what I was looking for per the video I watched of it. I'll keep hacking on it to figure out the dependencies and loccation issues. I am a bit concerned about the Termbox error though. Thanks, and great work! Rob On 2 October 2015 at 05:40, Alex Charlton wrote: > Hi Robert, > > As it seems your goal is to get Hypergiant running on Windows, I have to > let you know that you're venturing into uncharted territory. It's not > something I've ever tried before! > > That said, there error that you've shared with us is fairly > straight-forward: > > > ingw32/bin/ld.exe: cannot find -lglfw > > This is the source of the problem which is saying that it's not able to > link to GLFW. This could mean that you don't have GLFW ( > http://www.glfw.org/) installed in the right place (which could also be > the case for other eggs that depend on external libraries) or that the egg > itself is not linking to it correctly. The latter is certainly possible, > since I don't think it's been tested on Windows before. > > If you want more help working through this, just send me an email. If you > find that the egg is doing something wrong, I'm happy to patch it for you. > Of course, if you want to continue conversing with this lovely mailing > list, feel free to do that, too ;-) Maybe someone here has gotten > Hypergiant running on Windows. > > Cheers, > Alex > > On Thu, Oct 1, 2015 at 12:20 PM Robert Herman wrote: > >> I am running Windows 10, with MinGW-64 32-bit version, since I have the >> Windows binary for CHICKEN-IUP which is 32-bit. Some eggs have installedj >> fine - format, sql-de-lite, Spiffy, and other spiffy eggs, numbers, srfi's, >> gl-math, awful, and awful-server, but others - blas, hypergiant, >> hyperscene, and termbox fail with the same type of error - (require-library >> setup-api). >> I would like to be able to load blas, atlas-lapack, hypergiant, and >> hyperscene for math and game dev. >> I always run chicken-install, csi and csc from the MinGW command window. >> Below is the last half of the log of my command line when trying to install >> the hypergiant egg. I have installed glfw and glew on windows with paths >> set outside of CHICKEN-IUP. Hypergiant has a lot of dependencies, but some >> of the smaller eggs fail in a similar fashion. Any ideas? Thank you. >> >> HTTP/1.1 200 OK >> Date: Thu, 01 Oct 2015 12:43:42 GMT >> Server: Apache/2.2.29 (Unix) DAV/2 SVN/1.8.10 PHP/5.4.32 mod_fastcgi/2.4.6 >> Connection: close >> Transfer-Encoding: chunked >> Content-Type: text/plain >> reading chunks .. >> reading files ... >> ./BSD-LICENCE >> ./hashtest.c >> ./z3.meta >> ./z3.scm >> ./z3.setup >> ./z3bdtest.c >> ./z3betest.c >> ./z3blib.c >> ./z3blib.h >> ./z3crc32.h >> ./z3ddtest.c >> ./z3detest.c >> ./z3dlib.3 >> ./z3dlib.c >> ./z3dlib.h >> ./z3fdtest.c >> ./z3fetest.c >> ./z3flib.3 >> ./z3flib.c >> ./z3flib.h >> ./z3lib.3 >> ./z3lib.h >> ./z3liblib.h >> z3 located at C:\Users\Robert\AppData\Local\Temp/tempc7f2.14752/z3 >> checking platform for `opengl-glew' ... >> checking dependencies for `opengl-glew' ... >> checking platform for `z3' ... >> checking dependencies for `z3' ... >> checking platform for `hyperscene' ... >> checking dependencies for `hyperscene' ... >> checking platform for `gl-type' ... >> checking dependencies for `gl-type' ... >> missing: freetype, opengl-glew, gl-utils >> retrieving ... >> connecting to host "chicken.kitten-technologies.co.uk", port 80 ... >> requesting "/henrietta.cgi?name=freetype&mode=default" ... >> reading response ... >> HTTP/1.1 200 OK >> Date: Thu, 01 Oct 2015 12:43:44 GMT >> Server: Apache/2.2.29 (Unix) DAV/2 SVN/1.8.10 PHP/5.4.32 mod_fastcgi/2.4.6 >> Connection: close >> Transfer-Encoding: chunked >> Content-Type: text/plain >> reading chunks . >> reading files ... >> ./freetype.meta >> ./freetype.scm >> ./freetype.setup >> freetype located at >> C:\Users\Robert\AppData\Local\Temp/tempc7f2.14752/freetype >> checking platform for `freetype' ... >> checking dependencies for `freetype' ... >> checking platform for `glfw3' ... >> checking dependencies for `glfw3' ..
Re: [Chicken-users] Hypergiant egg install fails, and some other eggs
Hi Robert, As it seems your goal is to get Hypergiant running on Windows, I have to let you know that you're venturing into uncharted territory. It's not something I've ever tried before! That said, there error that you've shared with us is fairly straight-forward: > ingw32/bin/ld.exe: cannot find -lglfw This is the source of the problem which is saying that it's not able to link to GLFW. This could mean that you don't have GLFW (http://www.glfw.org/) installed in the right place (which could also be the case for other eggs that depend on external libraries) or that the egg itself is not linking to it correctly. The latter is certainly possible, since I don't think it's been tested on Windows before. If you want more help working through this, just send me an email. If you find that the egg is doing something wrong, I'm happy to patch it for you. Of course, if you want to continue conversing with this lovely mailing list, feel free to do that, too ;-) Maybe someone here has gotten Hypergiant running on Windows. Cheers, Alex On Thu, Oct 1, 2015 at 12:20 PM Robert Herman wrote: > I am running Windows 10, with MinGW-64 32-bit version, since I have the > Windows binary for CHICKEN-IUP which is 32-bit. Some eggs have installedj > fine - format, sql-de-lite, Spiffy, and other spiffy eggs, numbers, srfi's, > gl-math, awful, and awful-server, but others - blas, hypergiant, > hyperscene, and termbox fail with the same type of error - (require-library > setup-api). > I would like to be able to load blas, atlas-lapack, hypergiant, and > hyperscene for math and game dev. > I always run chicken-install, csi and csc from the MinGW command window. > Below is the last half of the log of my command line when trying to install > the hypergiant egg. I have installed glfw and glew on windows with paths > set outside of CHICKEN-IUP. Hypergiant has a lot of dependencies, but some > of the smaller eggs fail in a similar fashion. Any ideas? Thank you. > > HTTP/1.1 200 OK > Date: Thu, 01 Oct 2015 12:43:42 GMT > Server: Apache/2.2.29 (Unix) DAV/2 SVN/1.8.10 PHP/5.4.32 mod_fastcgi/2.4.6 > Connection: close > Transfer-Encoding: chunked > Content-Type: text/plain > reading chunks .. > reading files ... > ./BSD-LICENCE > ./hashtest.c > ./z3.meta > ./z3.scm > ./z3.setup > ./z3bdtest.c > ./z3betest.c > ./z3blib.c > ./z3blib.h > ./z3crc32.h > ./z3ddtest.c > ./z3detest.c > ./z3dlib.3 > ./z3dlib.c > ./z3dlib.h > ./z3fdtest.c > ./z3fetest.c > ./z3flib.3 > ./z3flib.c > ./z3flib.h > ./z3lib.3 > ./z3lib.h > ./z3liblib.h > z3 located at C:\Users\Robert\AppData\Local\Temp/tempc7f2.14752/z3 > checking platform for `opengl-glew' ... > checking dependencies for `opengl-glew' ... > checking platform for `z3' ... > checking dependencies for `z3' ... > checking platform for `hyperscene' ... > checking dependencies for `hyperscene' ... > checking platform for `gl-type' ... > checking dependencies for `gl-type' ... > missing: freetype, opengl-glew, gl-utils > retrieving ... > connecting to host "chicken.kitten-technologies.co.uk", port 80 ... > requesting "/henrietta.cgi?name=freetype&mode=default" ... > reading response ... > HTTP/1.1 200 OK > Date: Thu, 01 Oct 2015 12:43:44 GMT > Server: Apache/2.2.29 (Unix) DAV/2 SVN/1.8.10 PHP/5.4.32 mod_fastcgi/2.4.6 > Connection: close > Transfer-Encoding: chunked > Content-Type: text/plain > reading chunks . > reading files ... > ./freetype.meta > ./freetype.scm > ./freetype.setup > freetype located at > C:\Users\Robert\AppData\Local\Temp/tempc7f2.14752/freetype > checking platform for `freetype' ... > checking dependencies for `freetype' ... > checking platform for `glfw3' ... > checking dependencies for `glfw3' ... > install order: > ("glfw3" > "freetype" > "opengl-glew" > "z3" > "srfi-99" > "gl-utils" > "gl-type" > "hyperscene" > "glls" > "noise" > "soil" > "random-mtzig" > "bitstring" > "hypergiant") > installing glfw3:0.6.1 ... > changing current directory to > C:\Users\Robert\AppData\Local\Temp/tempc7f2.14752/ > glfw3 > "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 > '(\"glfw3\" \"0.6.1\"))" "glfw3.setup" > "c:\chicken-iup\bin\csc" -feature compiling-extension -setup-mode-O2 > -d0 - > lglfw -lopengl32 -lgdi32 -J -s glfw3-bindings.scm > > C:/minGW-32/mingw32/bin/../lib/gcc/i686-w64-mingw32/5.2.0/../../../../i686-w64-m > ingw32/bin/ld.exe: cannot find -lglfw > collect2.exe: error: ld returned 1 exit status > > Error: shell command terminated with non-zero exit status 1: ""gcc" > "glfw3-bindi > ngs.o" -o "glfw3-bindings.so" -Wl,--enable-auto-import -shared > -Lc:\chicken-iup\ > lib -lglfw -lopengl32 -lgdi32 -L"c:\chicken-iup/lib/" -lchicken -lm > -lws2_32" > > Error: shell command failed with nonzero exit status 1: > > "c:\chicken-iup\bin\csc" -feature compiling-extension -setup-mode-O2 > -d0 - > lgl