On Sun, Jul 21, 2013 at 03:04:00AM +0200, Waldek Hebisch wrote: > Pippijn van Steenhoven wrote: > > > > Yes, unfortunately, the installed aldor does not know where it lives, yet. > > This will be fixed very soon, and there is a ticket for it in the issue > > tracker. Until then, do: > > export ALDORROOT=/usr > > It is pretty easy to fix, but I'm waiting for Peter Broadbery to review my > > recent changes before I continue, and we need to discuss how aldor should > > find out where it lives. There are basically two options, one is > > hard-coding it (by configure), and one is finding aldor in $PATH. I'm in > > favour of the latter, but we'll have to discuss it. > > Using $PATH is tempting, but leads to problems if main executable > is moved. FriCAS had the same problem. After some thought I > think that best solution is to use wrapper script to set > default values for environment variables (values in script are > "hardcoded" by configure). That way main "executable" works > everywhere and it is easy to move installation.
That seems like a good solution. I have uploaded a new package to the archive that puts the main "aldor" executable into $prefix/libexec, and a wrapper script "aldor" into $prefix/bin. The package will be ready in about 10-15 minutes. Pippijn
signature.asc
Description: Digital signature
