When using SGI's bash (2.05) or any version of bash (2 or 3) on other systems, the command:
... produces, as expected, the result "5".
However, using bash-3 from Nekoware. I get:
... which seems to indicate that bash isn't parsing the line correctly.
Could anyone who reads this quickly try this on their own SGI, and see what happens. I'm interested if IRIX release or architecture makes a difference. I've an Octane running 6.5.28.
(I also see this problem when using an auto-compiled bash from NetBSD's pkgsrc or OpenPKG's source RPM. However, another developers using MIPSpro 7.3.1.2m reports that OpenPKG's build works for him (compiled with CFLAGS=-O). I have MIPSpro 7.3.4m, and compiled with significant optimisations.)
Which is a good point - what are (or, indeed, are there) the standard optimisation options/CFLAGS used for building Nekoware builds?
Cheers,
Stuart
Code: Select all
$ /usr/gnu/bin/bash -c 'A=$(( 2 + 3 )); echo $A'
5
... produces, as expected, the result "5".
However, using bash-3 from Nekoware. I get:
Code: Select all
$ /usr/nekoware/bin/bash -c 'A=$(( 2 + 3 )); echo $A'
2: command not found
... which seems to indicate that bash isn't parsing the line correctly.
Could anyone who reads this quickly try this on their own SGI, and see what happens. I'm interested if IRIX release or architecture makes a difference. I've an Octane running 6.5.28.
(I also see this problem when using an auto-compiled bash from NetBSD's pkgsrc or OpenPKG's source RPM. However, another developers using MIPSpro 7.3.1.2m reports that OpenPKG's build works for him (compiled with CFLAGS=-O). I have MIPSpro 7.3.4m, and compiled with significant optimisations.)
Which is a good point - what are (or, indeed, are there) the standard optimisation options/CFLAGS used for building Nekoware builds?
Cheers,
Stuart