Linux/Bash/.SH question
-
No, really, not a programming issue :) I have a .sh archive called cs-m68k which contains the sources for a Windows -> m68K cross compiler and associated tools. Using SUSE under VMware I check the shell is 'executable', which it is. If I then execute ./cs-m68k.sh I get a BASH error claiming grep and sed cannot be found. Naturally, If I type grep on the same command line I get grep, ditto sed. Anyone got any ideas as to why the archive will not unpack? Behaviour is similar under Cygwin and MSys too. Thx++ Jerry
-
No, really, not a programming issue :) I have a .sh archive called cs-m68k which contains the sources for a Windows -> m68K cross compiler and associated tools. Using SUSE under VMware I check the shell is 'executable', which it is. If I then execute ./cs-m68k.sh I get a BASH error claiming grep and sed cannot be found. Naturally, If I type grep on the same command line I get grep, ditto sed. Anyone got any ideas as to why the archive will not unpack? Behaviour is similar under Cygwin and MSys too. Thx++ Jerry
Jerry Evans wrote:
I have a .sh archive
Aren't .sh files usually scripts (like Windows batch files)? Can you open it in vi / vim / (one of the other countless text editors included in every Linux distro)
-
Jerry Evans wrote:
I have a .sh archive
Aren't .sh files usually scripts (like Windows batch files)? Can you open it in vi / vim / (one of the other countless text editors included in every Linux distro)
sure. problem is the script is not executing correctly. sed & grep & friends should be invoked but something (bash?) does not want them to run
-
Jerry Evans wrote:
I have a .sh archive
Aren't .sh files usually scripts (like Windows batch files)? Can you open it in vi / vim / (one of the other countless text editors included in every Linux distro)
those are shell archive... you need to use
unsharto extract the content.This signature was proudly tested on animals.
-
No, really, not a programming issue :) I have a .sh archive called cs-m68k which contains the sources for a Windows -> m68K cross compiler and associated tools. Using SUSE under VMware I check the shell is 'executable', which it is. If I then execute ./cs-m68k.sh I get a BASH error claiming grep and sed cannot be found. Naturally, If I type grep on the same command line I get grep, ditto sed. Anyone got any ideas as to why the archive will not unpack? Behaviour is similar under Cygwin and MSys too. Thx++ Jerry
Could be a path issue. Make sure that: 1) sed et al, are in your path 2) make sure the script isn't doing something weird, such as changing the path, or hard coding where it thinks sed should be 3) perhaps the path is too long? I think there is a limit, but I'm pretty sure it's more than 256 chars.
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! Personal 3D projects Just Say No to Web 2 Point Blow
-
Could be a path issue. Make sure that: 1) sed et al, are in your path 2) make sure the script isn't doing something weird, such as changing the path, or hard coding where it thinks sed should be 3) perhaps the path is too long? I think there is a limit, but I'm pretty sure it's more than 256 chars.
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! Personal 3D projects Just Say No to Web 2 Point Blow
Thanks Jim, It looks like the script is modifying the path ... :(
-
No, really, not a programming issue :) I have a .sh archive called cs-m68k which contains the sources for a Windows -> m68K cross compiler and associated tools. Using SUSE under VMware I check the shell is 'executable', which it is. If I then execute ./cs-m68k.sh I get a BASH error claiming grep and sed cannot be found. Naturally, If I type grep on the same command line I get grep, ditto sed. Anyone got any ideas as to why the archive will not unpack? Behaviour is similar under Cygwin and MSys too. Thx++ Jerry
Jerry Evans wrote:
No, really, not a programming issue
No, but it's a linux question. Those should only ever, ever, be answered by Sir Richard, on a text based browser, over a varsity usenet connection. How dare you bring even a hint of such arcana to a slave of the anti-christ such as CodeProject?
-
Thanks Jim, It looks like the script is modifying the path ... :(
Gag, good luck. Can you alter the script to adjust for this? Have fun :)
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! Personal 3D projects Just Say No to Web 2 Point Blow
-
No, really, not a programming issue :) I have a .sh archive called cs-m68k which contains the sources for a Windows -> m68K cross compiler and associated tools. Using SUSE under VMware I check the shell is 'executable', which it is. If I then execute ./cs-m68k.sh I get a BASH error claiming grep and sed cannot be found. Naturally, If I type grep on the same command line I get grep, ditto sed. Anyone got any ideas as to why the archive will not unpack? Behaviour is similar under Cygwin and MSys too. Thx++ Jerry
The makers and users of Linux don't seem to understand standards and usability.
-
The makers and users of Linux don't seem to understand standards and usability.
true that.