;;
;; The invocation `csc -link NAME ...` tries to link the extension NAME
;; statically.
;;
;; It resolves NAME.o first from the CWD and include path, then the egg
;; repository, just like with dynamic libraries.
;;
;; If NAME.o isn't found, it checks NAME's extension information for a
;; (static FILE1 FILE2 ...) clause and uses the files listed.
;;
;; So it's basically just like running "csc -uses bar foo.scm bar.o"
;; manually, except that it knows where to find "bar.o".
;;

$ ls
bar.o
foo.scm
$ csc -verbose -link bar foo.scm
chicken foo.scm ...
gcc foo.c -o foo.o ...
gcc foo.o bar.o -o foo ...