Is that PATH correct for Singular 3.0.1-1? I just installed cygwin with Singular (after having to uninstall cygwin from a partition that was getting too full), and in the cygwin tree directory /usr/local/bin is totally empty. The Singular binaries are in /lib/Singular. Moreover, if I try
I get messages from bash:
bash: /usr/bin: is a directory
bash: /bin: is a directory
Finally, singular is not working in any fashion whatsoever: at the bash shell prompt I get error:
Singular : signal 11 (v: 3001/2005111410):
Segment fault/Bus error occurred (r:1153607477)
This is after setting all the Windows environment variables to what they should be, I think -- in particular, using /lib/Singular (and NOT /usr/lib/Singular, which does not exist) for the value of SINGULAR_BIN_DIR.
I get the same type of error if I try to run singular in a Windows command prompt window.
1. I made a really silly mistake when I tried your diagnostic of exporting PATH from within cygwin: I erroneoulsy used semicolons instead of colons to separate paths. Now, if at the bash prompt I do correctly type
then I CAN start Singular without error using command "singular". That's good!
However, I still get the Segment fault... error if I do not export PATH.
Executing "mount" at the bash prompt shows
V:cygwinbin on /usr/bin type system
V:cygwinlib on /usr/lib type system
V:cygwin on / type system (binmode)
along with entries of the form
d: on /cygdrive/d type system (binmode,noumount)
for each of my partitions.
Here is an excerpt from my windows PATH variable:
(I looked at the entire path and see no unusual characters or syntactical errors in it, although of course such might still be there.)
2. Even after doing export PATH, trying to run ESingular from the bash prompt causes a pop-up window "ESingular.exe" with text:
Error: Execution of
-eval '(progn (setq singular-emacs-home-directory
(load-file "/usr/share/Singular/emacs/.emacs-singular ")
"/cygdrive/e/Documents/CygwinHome/" (list ) "singular"))'
3. Still singular also stops with a Segment fault if I try to run itfrom a Windows command prompt. I do have the following Windows environment variables set: