Bug #6975
mrb confused by ugly components of current directory path
Start date:
09/11/2014
Due date:
% Done:
0%
Estimated time:
1.00 h
Description
When building under Jenkins, if you've setup a multiplatform build and specified a rule like
'swarm && slf6.5' for matching build nodes; you get a working directory that has a directory
named "/blah/blah/swarm && slf6.5/blah". This causes mrb newDev to give errors.
To reproduce:
mkdir 'foo && bar' cd 'foo && bar' mkdir baz cd baz mrb newDev -f -q e5:prof
will give errors like:
/grid/fermiapp/products/larsoft/mrb/v1_01_08/bin/newDev.sh: line 400: cd: /uboone/app/users/mengel/work/foo: No such file or directory /grid/fermiapp/products/larsoft/mrb/v1_01_08/bin/newDev.sh: line 425: cd: /uboone/app/users/mengel/work/foo: No such file or directory MRB_BUILDDIR is /uboone/app/users/mengel/work/foo && bar/baz/build_slf6.x86_64 /grid/fermiapp/products/larsoft/mrb/v1_01_08/bin/newDev.sh: line 73: cd: /uboone/app/users/mengel/work/foo: No such file or directory /grid/fermiapp/products/larsoft/mrb/v1_01_08/bin/newDev.sh: line 78: cd: /uboone/app/users/mengel/work/foo: No such file or directory MRB_SOURCE is /uboone/app/users/mengel/work/foo && bar/baz/build_slf6.x86_64/srcs cp: cannot create regular file `/uboone/app/users/mengel/work/foo/CMakeLists.txt': No such file or directory
I think judicious addition of double quotes would make this work.
This isn't high priority, as I have a workaround in Jenkins; but folks could trip over it in
various environments where special characters or spaces end up in directory paths outside of
their control.
History
#1 Updated by Lynn Garren over 5 years ago
- Description updated (diff)
- Status changed from New to Assigned
- Assignee set to Lynn Garren
- Estimated time set to 1.00 h
"Ugh" But, yes, the solution should be simple.