Differences

This shows you the differences between two versions of the page.

--- using_chicken_on_sdf [2021/03/17 20:41] – created hc9
+++ using_chicken_on_sdf [2021/03/17 20:44] – [Install Eggs] hc9
@@ Line 54: / Line 54: @@
 Then create some environment variables so Chicken will know to use your new repository for eggs, and will compile against SDF's system libraries when installing eggs:
-export CHICKEN_INCLUDE_PATH=${HOME}/chicken/lib/chicken/6\\  export CHICKEN_REPOSITORY=${HOME}/chicken/lib/chicken/6\\  export CSC_OPTIONS="-I/usr/pkg/include -L/usr/pkg/lib -static-libs"
+  export CHICKEN_INCLUDE_PATH=${HOME}/chicken/lib/chicken/6
+  export CHICKEN_REPOSITORY=${HOME}/chicken/lib/chicken/6
+  export CSC_OPTIONS="-I/usr/pkg/include -L/usr/pkg/lib -static-libs"
 (You may also wish to put the above lines in a shell startup file, like ~/.bash_profile, so that the variables will be set every time you log in to SDF.)
@@ Line 64: / Line 66: @@
 If the install was successful, we can check whether everything's working. Start the Chicken interpreter with csi and run this Scheme program to load the readline egg:
-  (use readline)
+''(use readline)''
 Then run this program to use readline in this interpreter session:
-  (current-input-port (make-gnu-readline-port))
+''(current-input-port (make-gnu-readline-port))''
 Now check if you have readline support in the interpreter. Run a trivial program like 42 and then hit the Up key and check if "42" gets entered at the prompt. If so, the readline egg is installed and working. You can put the first two Scheme programs (the ones that load the egg and make it work) into a ~/.csirc file and the interpreter will run those programs at the beginning of each session.
@@ Line 75: / Line 77: @@
 $Id: chicken.html,v 1.15 2011/08/29 06:43:41 ab9 Exp $ [[http://sdf.org/?tutorials/chicken|Using Chicken on SDF]] - traditional link (using [[wp>Revision_Control_System|RCS]])