id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	difficulty
69	chicken-install does not stop on error	Jim Ursetto		"After a compilation error chicken-install will continue to execute and attempt to install the extension anyway.

For example, install the readline egg without any readline library installed at all:

{{{
  /home/jim/local/chicken-4/bin/csc -feature compiling-extension   -s -O2 readline.scm -lreadline -lhistory -ltermcap
Error: shell command terminated with non-zero exit status 256:
 gcc readline.c -o readline.o -c -fno-strict-aliasing -DHAVE_CHICKEN_CONFIG_H -Os \
  -fomit-frame-pointer -fPIC -DPIC -DC_SHARED -I/home/jim/local/chicken-4/include

  /home/jim/local/chicken-4/bin/csc -feature compiling-extension   -c -O2 -d0 -j readline \
   readline.scm -o readline-static.o -unit readline -lreadline -lhistory -ltermcap
Error: shell command terminated with non-zero exit status 256:
 gcc readline-static.c -o readline-static.o -c -fno-strict-aliasing -DHAVE_CHICKEN_CONFIG_H \
  -Os -fomit-frame-pointer -I/home/jim/local/chicken-4/include

  /home/jim/local/chicken-4/bin/csc -feature compiling-extension   -s -O2 -d0 readline.import.scm

  rm -fr /home/jim/local/chicken-4/lib/chicken/4/readline.so
Error: file does not exist: ""readline.so""
Error: shell command terminated with nonzero exit code 17920
}}}

It probably also prevents the correct analysis of which libraries are on the system, which was reported by Sam Varner, because a failing compile will ""succeed"" from the caller's perspective.

Wild guess, this could have to do with improper parsing of exit status 256 (which happens to be 0 mod 256).  Actual investigation is needed."	defect	closed	major		build system	4.1.x	fixed