All scripts must updated to /bin/bash instead of /bin/sh. Many distributions uses dash (which is ash) for default shell. Actually not a problem but ./gen does not work :)
Under investigation
The issue is that some scripts have bash-only constructs, and and these fail when the default shell is not bash.
The solution is either: 1. modify the scripts to be purely sh compatible 2. demand that all environments include bash
Quick fix: edit the top line for any failing scripts from
1
#!/bin/sh
to
#!/bin/bash
Anonymous
You seem to have CSS turned off. Please don't fill out this field.
more info here:
https://unix.stackexchange.com/questions/496505/is-it-correct-to-use-bin-sh-in-the-hashbang-if-the-bourne-shell-isnt-available
fix committed in svn revision 66: https://sourceforge.net/p/pascal-p5c/code/HEAD/tree/
Tested on Ubuntu live 19.10
Main release should happen in a couple of weeks after testing on a wider variety of systems
Fix now incorporated in new release, 1.2.
Nicholas: can you confirm this is now working OK for you?
Under investigation
The issue is that some scripts have bash-only constructs, and and these fail when the default shell is not bash.
The solution is either:
1. modify the scripts to be purely sh compatible
2. demand that all environments include bash
Quick fix: edit the top line for any failing scripts from
#!/bin/sh
to
#!/bin/bash
more info here:
https://unix.stackexchange.com/questions/496505/is-it-correct-to-use-bin-sh-in-the-hashbang-if-the-bourne-shell-isnt-available
fix committed in svn revision 66:
https://sourceforge.net/p/pascal-p5c/code/HEAD/tree/
Tested on Ubuntu live 19.10
Main release should happen in a couple of weeks after testing on a wider variety of systems
Fix now incorporated in new release, 1.2.
Nicholas: can you confirm this is now working OK for you?
Last edit: Trevor Blight 2020-01-14