Re: [Chicken-users] Travis CI

Hi Hugo, On Wed, 30 Apr 2014 20:56:30 -0300 Hugo Arregui wrote: > Sorry for the late response!. No problem at all! >>Instead of just running "chicken-install -test", you can install >>salmonella and run it. It'll perform some extra checks that >>chicken-install doesn't. In case you run salmo

Re: [Chicken-users] Travis CI

Hi Mario, Sorry for the late response!. Instead of just running "chicken-install -test", you can install salmonella and run it. It'll perform some extra checks that chicken-install doesn't. In case you run salmonella, you'll probably also want to run "salmonella-log-viewer salmonella.log" to

Re: [Chicken-users] build with CC="gcc -m32"

Hi Tomas, On Wed, 30 Apr 2014 22:06:44 +0200 Tomas Hlavaty wrote: > I tried to build 32bit chicken scheme on x86-64 linux: > > $ make PLATFORM=linux ARCH=x86 C_COMPILER="gcc -m32" PREFIX=~/sw/chicken32 > > and all seemed well. > > However, it seems that the compiled csc has a bug, where it treat

Re: [Chicken-users] build with CC="gcc -m32"

Tomas Hlavaty scripsit: > However, it seems that the compiled csc has a bug, where it treats the > env var value as executable name instead of letting the shell interpret it: Letting the shell interpret things is a Bad Idea. I recommend that you put a script somewhere that looks like this: #!/b

[Chicken-users] build with CC="gcc -m32"

Hi, I tried to build 32bit chicken scheme on x86-64 linux: $ make PLATFORM=linux ARCH=x86 C_COMPILER="gcc -m32" PREFIX=~/sw/chicken32 and all seemed well. However, it seems that the compiled csc has a bug, where it treats the env var value as executable name instead of letting the shell interpr