Greetings! I feel the best solution would be to conditionalize the addition of the -I on the :system-p compile-file option not being set. GCL carries a copy of cmpinclude.h in compiler::*cmpinclude-string* which is written into each file unless :system-p is on. Somewhat wasteful, but much more portable. I'd leave si::*system-directory* alone if at all possible. Several autoloads will break unless this setting and others like it are correct. See si::reset-sys-paths, which is used in the Debian gcl package when installing gcl in a fresh location.
I think this could go into 2.6.8pre if it is important to axiom. Take care, Waldek Hebisch <[EMAIL PROTECTED]> writes: > I wonder if there is a preferred procedure to create executables > with gcl such that the resulting executable can use Lisp > compiler. More precisely, using defualt setting of si::*system-directory* > may lead to problems. Namely, if gcl is installed in a privite > directory (not readable by other users) then the resulting > executable give errors during C compile. This is because > gcl (unconditionally) passes to C compiler -I directive pointing > to original system directory. However when directory specified > in -I directive exists but is not readable by the user invoking > the compiler gcc treats this as an error. > > This problem appeared when trying to install Axiom, see: > > http://lists.nongnu.org/archive/html/axiom-developer/2007-02/msg00212.html > > but I belive is a general problem for gcl created executables. > > So the question is what is the preferred solution, in particular > if creator of the executable should change the value of > si::*system-directory* ? > > -- > Waldek Hebisch > [EMAIL PROTECTED] > > > -- Camm Maguire [EMAIL PROTECTED] ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah _______________________________________________ Gcl-devel mailing list Gcl-devel@gnu.org http://lists.gnu.org/mailman/listinfo/gcl-devel
