Hi,
When I am in the directory e.g.
build.linux32x86/squeak.cog.spur/build.assert
and I run ./mvm I get:
./mvm: line 18: ../../scripts/checkSCCSversion: No such file or directory
so if I change mvm to call ../../../scripts/checkSCCSversion it works fine.
The "makeall*" scripts don't fail, I think, because they trap the error and ignore it:
~/src/opensmalltalk-vm/build.linux32x86/squeak.cog.spur$ ./makeallclean ./mvm: line 22: ../../scripts/checkSCCSversion: No such file or directory clean? for f in *; do case "$f" in mvm) ;; *) rm -rf $f; esac; done
I assume the other platforms don't fail simply because they nest their build directories only two-deep rather than three:
~/src/opensmalltalk-vm$ find . -name mvm ./build.linux32x86/newspeak.stack.spur/build.debug/mvm [...] ./build.macos32x86/pharo.cog.v3/mvm [...] ./build.win64x64/squeak.stack.spur/mvm [...] ./build.linux32ARMv6/squeak.stack.v3/build.debug/mvm
So, my question: does this matter? Does checkSCCSversion make a difference on linux? If so, would it be worth my while to prepare a PR which updates all mvm scripts within nested linux build directories to invoke ../../../scripts/checkSCCSversion rather than ../../scripts/ checkSCCSversion ?
Thanks, Tim J
Hi Tim,
yes this matters. If you have tej energy can you cane the various mvm scripts under the build.linux*** directories? If not, I can do it with a friend and ed - .
On Sat, Jun 8, 2019 at 9:50 AM Tim Johnson digit@sonic.net wrote:
Hi,
When I am in the directory e.g.
build.linux32x86/squeak.cog.spur/build.assert
and I run ./mvm I get:
./mvm: line 18: ../../scripts/checkSCCSversion: No such file or directory
so if I change mvm to call ../../../scripts/checkSCCSversion it works fine.
The "makeall*" scripts don't fail, I think, because they trap the error and ignore it:
~/src/opensmalltalk-vm/build.linux32x86/squeak.cog.spur$ ./makeallclean ./mvm: line 22: ../../scripts/checkSCCSversion: No such file or directory clean? for f in *; do case "$f" in mvm) ;; *) rm -rf $f; esac; done
I assume the other platforms don't fail simply because they nest their build directories only two-deep rather than three:
~/src/opensmalltalk-vm$ find . -name mvm ./build.linux32x86/newspeak.stack.spur/build.debug/mvm [...] ./build.macos32x86/pharo.cog.v3/mvm [...] ./build.win64x64/squeak.stack.spur/mvm [...] ./build.linux32ARMv6/squeak.stack.v3/build.debug/mvm
So, my question: does this matter? Does checkSCCSversion make a difference on linux? If so, would it be worth my while to prepare a PR which updates all mvm scripts within nested linux build directories to invoke ../../../scripts/checkSCCSversion rather than ../../scripts/ checkSCCSversion ?
Thanks, Tim J
Hi Eliot,
OK, thanks. I think I came up with something:
for f in $(find . -name mvm -exec grep -q checkSCCS {} ; -print | awk -F/ 'NF == 5 { print $0 }') ; do printf "g/checkSCCSversion/s/..//& ..//\nw\nq" | ed ${f} ; done
...and will submit a PR this afternoon/evening.
Tim J
On Jun 12, 2019, at 6:30 PM, Eliot Miranda wrote:
Hi Tim,
yes this matters. If you have tej energy can you cane the
various mvm scripts under the build.linux*** directories? If not, I can do it with a friend and ed - .
On Sat, Jun 8, 2019 at 9:50 AM Tim Johnson digit@sonic.net wrote:
Hi,
When I am in the directory e.g.
build.linux32x86/squeak.cog.spur/build.assert
and I run ./mvm I get:
./mvm: line 18: ../../scripts/checkSCCSversion: No such file or directory
so if I change mvm to call ../../../scripts/checkSCCSversion it works fine.
The "makeall*" scripts don't fail, I think, because they trap the error and ignore it:
~/src/opensmalltalk-vm/build.linux32x86/squeak.cog.spur$ ./ makeallclean ./mvm: line 22: ../../scripts/checkSCCSversion: No such file or directory clean? for f in *; do case "$f" in mvm) ;; *) rm -rf $f; esac; done
I assume the other platforms don't fail simply because they nest their build directories only two-deep rather than three:
~/src/opensmalltalk-vm$ find . -name mvm ./build.linux32x86/newspeak.stack.spur/build.debug/mvm [...] ./build.macos32x86/pharo.cog.v3/mvm [...] ./build.win64x64/squeak.stack.spur/mvm [...] ./build.linux32ARMv6/squeak.stack.v3/build.debug/mvm
So, my question: does this matter? Does checkSCCSversion make a difference on linux? If so, would it be worth my while to prepare a PR which updates all mvm scripts within nested linux build directories to invoke ../../../scripts/checkSCCSversion rather than ../../scripts/ checkSCCSversion ?
Thanks, Tim J
-- _,,,^..^,,,_ best, Eliot
Hi Tim,
On Thu, Jun 13, 2019 at 7:54 AM Tim Johnson digit@sonic.net wrote:
Hi Eliot,
OK, thanks. I think I came up with something:
for f in $(find . -name mvm -exec grep -q checkSCCS {} ; -print | awk -F/ 'NF == 5 { print $0 }') ; do printf "g/checkSCCSversion/s/..//&..//\nw\nq" | ed ${f} ; done
Here scripts are good too:
for f in `find . -name mvm`; do ed - $f <<END g/FOO/s//BAR/ w q END done
...and will submit a PR this afternoon/evening.
Tim J
On Jun 12, 2019, at 6:30 PM, Eliot Miranda wrote:
Hi Tim,
yes this matters. If you have tej energy can you cane the various mvm
scripts under the build.linux*** directories? If not, I can do it with a friend and ed - .
On Sat, Jun 8, 2019 at 9:50 AM Tim Johnson digit@sonic.net wrote:
Hi,
When I am in the directory e.g.
build.linux32x86/squeak.cog.spur/build.assert
and I run ./mvm I get:
./mvm: line 18: ../../scripts/checkSCCSversion: No such file or directory
so if I change mvm to call ../../../scripts/checkSCCSversion it works fine.
The "makeall*" scripts don't fail, I think, because they trap the error and ignore it:
~/src/opensmalltalk-vm/build.linux32x86/squeak.cog.spur$ ./makeallclean ./mvm: line 22: ../../scripts/checkSCCSversion: No such file or directory clean? for f in *; do case "$f" in mvm) ;; *) rm -rf $f; esac; done
I assume the other platforms don't fail simply because they nest their build directories only two-deep rather than three:
~/src/opensmalltalk-vm$ find . -name mvm ./build.linux32x86/newspeak.stack.spur/build.debug/mvm [...] ./build.macos32x86/pharo.cog.v3/mvm [...] ./build.win64x64/squeak.stack.spur/mvm [...] ./build.linux32ARMv6/squeak.stack.v3/build.debug/mvm
So, my question: does this matter? Does checkSCCSversion make a difference on linux? If so, would it be worth my while to prepare a PR which updates all mvm scripts within nested linux build directories to invoke ../../../scripts/checkSCCSversion rather than ../../scripts/ checkSCCSversion ?
Thanks, Tim J
-- _,,,^..^,,,_ best, Eliot
vm-dev@lists.squeakfoundation.org