Custom Query (1630 matches)

Dependency chains such as a -> b -> c must be handled by installing a first, then b, then c. However, chicken-install creates a list of dependencies of c, and then tries to install them in an order that is not necessarily correct.

For example, the probdist library requires the srfi-4-utils library, which in turns requires srfi-4-comprehensions, which requires srfi-42. `chicken-install probdist' downloads srfi-4-utils, srfi-4-comprehensions, and srfi-42, and then proceeds to try to install srfi-4-comprehensions, which fails because srfi-42 has not been installed yet.

To follow FHS, the repository path should be located in /var/.... This can be optional by supplying a build-time option.

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.