Juan Jose Garcia-Ripoll wrote:
>
> Hi Waldek, congratulations for Fricas. I started using it recently and I am
> very impressed. I have some comments.
>
Thanks for kind words.
>
> - It was not obvious to me that Fricas had a graphical interface. This
> prevented me from using for some time. Some notes about how to start
> fricas
> and how to best use it would be welcome for newbies.
> - I use OS X. This is another reason why I was not able to use the
> graphical interface: one has to explictly supply --x-includes and
> --x-libraries. Would it be possible to automatically detect this?
I do not know: FriCAS uses autoconf. So it should work or fail in
similar way as other autoconf-using programs. FriCAS do performs
a few extra checks, notably for Xpm library so they are likely culprit.
Could you send me output of 'configure' (in particular 'config.log')?
> - I had to fix ECL on a couple of places. The problem is that is a file
> on Fricas called float.lsp. This float.lsp, when compiled, leads to a
> float.h which,as you may guess, conflicts with /usr/include/float.h
> I have
> changed the extension of header files in CVS, so that now the files
> generated will be float.c float.eclh and float.data, no conflicts expected.
> - Fricas from CVS fails to build at all with ECL. Unfortunately SBCL from
> Fink also does not build Fricas. I believe the problems are totally
> unrelated, but I would like to be able to debug the problem with Fricas:
> all
> I get is an "Internal Error" message, no debugger, no hints on how to
> proceed.
>
Apparently you are building on case-insentive filesystem (otherwise
there should be no conflict between "FLOAT.h" and "float.h").
That in the past we tried to eliminate conflicts due to filenames
clashing when compared in case-insentive way, but I am not sure
if this was recently tried. Anyway, looks like possible common
problem.
If you have build FriCAS (or build advanced far enough) then
)set break break
at FriCAS command line make FriCAS error handler execute "BREAK"
on error, so you get dropped into Lisp debugger. When debugging
build problems I run 'make' with output redirected to a file,
like
make > mlogg
when build fails I look trough log to find first error (ATM build
may contunue much beyond the core failure point). Then
I interactively re-run failing command. At early stages
executables like 'lisp', 'bootsys' and 'depsys' just present
normal Lisp prompt. Later 'interpsys' and 'AXIOMsys' use
FriCAS prompt.
When using ECL you may want to change ecl-specific part at the
end of src/lisp/fricas-package.lisp (currently this part
sets safety to 1, but for debugging one should probably use
higher debug setting).
> I believe it should be pretty easy to bundle Fricas and ECL in a DMG bundle
> for easy distribution in OS X. You may consider this for the upcoming
> release.
>
I have no access to OS X. However, if somebody provided such combination
I would be happy to put it on sourceforge for download.
--
Waldek Hebisch
[email protected]
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/fricas-devel?hl=en.
