Post a reply
Username:
Note:If not registered, provide any username. For more comfort, register here.
Subject:
Message body:
Enter your message here, it may contain no more than 60000 characters. 

Smilies
:D :) :( :o :shock: :? 8) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :!: :?: :idea: :arrow: :| :mrgreen:
Font size:
Font colour
Options:
BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON
Disable BBCode
Disable smilies
Do not automatically parse URLs
Confirmation of post
To prevent automated posts the board requires you to enter a confirmation code. The code is displayed in the image you should see below. If you are visually impaired or cannot otherwise read this code please contact the %sBoard Administrator%s.
Confirmation code:
Enter the code exactly as it appears. All letters are case insensitive, there is no zero.
   

Topic review - Singular, ESingular error under cygwin yet again
Author Message
  Post subject:  Thanks for the fix!!!  Reply with quote
I had just had my machine fixed and I was wondering if something was still broken here. Entered your patch and now it is working.
Post Posted: Mon Aug 20, 2007 4:03 am
  Post subject:  to clarify: ESingular works with export at command line  Reply with quote
Just to clarify: If I start the cygwin Bash shell and execute directly there

Code:
export PATH=PATH=/bin:/usr/bin:usr/X11R6/bin


then ESingular works OK. The only problem I'm having (after I fixed the /bin/Singular script) is getting that command to work if it is placed into the /bin/ESingular script.
Post Posted: Sun Jul 29, 2007 7:11 pm
  Post subject:  Singular, ESingular error under cygwin yet again  Reply with quote
I upgraded cygwin, including its Singular distribution, to the current version and, yet once again, when I run command Singular I'm getting the familiar Segment fault/Bus error after which Singular hangs. Per earlier posts in this forum, if I add the line

Code:
export PATH=/bin:/usr/bin:usr/X11R6/bin


before the final line of script binSingular, then I can run Singular at the Bash command line and I can run the Windows shortcut Singular (rxvt).

However, despite the earlier posts, if I add that line before the final line of script binESingular, still ESingular bombs, with the following error message:

Code:
  Error: Execution of
/bin/xemacs-21.4.20.exe -no-init-file -eval'(progn (setq singular-emacs-home-directory "/usr/share/Singular/emacs")
  (load-file "/usr/share/Singular/emacs/.emacs-singular")
  (singular-other "/usr/lib/Singular/Singular.exe" "/cygdrive/e/Documentation/CygwinHome/" (list) "singular"))'


Part of the problem may be my confusion as to whether simply to edit the existing export PATH lines in the two scrips or add the additional line suggested...

Thus in script "Singular", the last two lines, lines 9 and 10, as distributed are:

Code:
  export PATH="/usr/lib/Singular:$PATH"
  exec /usr/lib/Singular/Singular.exe $*


I replaced that export statement with the following, and all seemed OK:

Code:
  export PATH=/bin:/usr/bin:usr/X11R6/bin


But should it have been, instead, the following:

Code:
  export PATH="/bin:/usr/bin:usr/X11R6/bin:/usr/lib/Singular:$PATH"


(or something else)?

However, similarly editing ESingular still causes that to bomb with the indicated error. The last three lines of ESingular were:

Code:
export PATH="/usr/lib/Singular:/usr/X11R6/bin:$PATH"
export PATH=/bin:/usr/bin:usr/X11R6/bin:/usr/lib/Singular
if [ -z $DISPLAY ]; then export DISPLAY=:0.0; fi
exec /usr/lib/Singular/ESingular.exe $*


I tried replacing the "export PATH" statement with just
Code:
  export PATH=/bin:/usr/bin:usr/X11R6/bin

as well as replacing it, instead, with:
Code:
export PATH="/bin:/usr/bin:usr/X11R6/bin:/usr/lib/Singular:$PATH"

But in each case I got the indicated error when I tried to run command ESingular at the Bash command line.

???
Post Posted: Sun Jul 29, 2007 6:50 pm


It is currently Fri May 13, 2022 11:03 am
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group