From: Tom B. <tom...@gm...> - 2012-01-19 17:37:14
|
Cliff, sorry I jumped the gun when I thought opendb command was missing, but I forgot it is an mged command and panicked when my "make regress" failed on mged-regress after my work with vls. I get this error and don't know why: testing mged commands... ...all/ ERROR: all/ does not exist! Output: invalid command name "all/" ...t.r/R ERROR: t.r/R does not exist! Output: invalid command name "t.r/R" ...t.s ERROR: t.s does not exist! Output: invalid command name "t.s" -> mged check FAILED make[3]: *** [regress/CMakeFiles/mged-regress] Error 3 make[2]: *** [regress/CMakeFiles/mged-regress.dir/all] Error 2 make[1]: *** [regress/CMakeFiles/mged-regress.dir/rule] Error 2 make: *** [mged-regress] Error 2 In regress/mged.sh there is this line which seems to cause the problem: cmds="`$MGED -c mged.g ? 2>&1 | grep -v Using`" When I change it to this (protect ? in single quotes) the mged-regress works: cmds="`$MGED -c mged.g '?' 2>&1 | grep -v Using`" So what is going on? Best, -Tom |
From: Clifford Y. <cli...@gm...> - 2012-01-20 00:45:39
|
Um... got me there. I'm not seeing that issue... what platform are you running on? In particular, what shell is being used for sh? Any sh script gurus recognize those symptoms? Cliff On Thu, Jan 19, 2012 at 12:36 PM, Tom Browder <tom...@gm...> wrote: > Cliff, sorry I jumped the gun when I thought opendb command was > missing, but I forgot it is an mged command and panicked when my "make > regress" failed on mged-regress after my work with vls. > > I get this error and don't know why: > > testing mged commands... > ...all/ > ERROR: all/ does not exist! > Output: invalid command name "all/" > ...t.r/R > ERROR: t.r/R does not exist! > Output: invalid command name "t.r/R" > ...t.s > ERROR: t.s does not exist! > Output: invalid command name "t.s" > -> mged check FAILED > make[3]: *** [regress/CMakeFiles/mged-regress] Error 3 > make[2]: *** [regress/CMakeFiles/mged-regress.dir/all] Error 2 > make[1]: *** [regress/CMakeFiles/mged-regress.dir/rule] Error 2 > make: *** [mged-regress] Error 2 > > In regress/mged.sh there is this line which seems to cause the problem: > > cmds="`$MGED -c mged.g ? 2>&1 | grep -v Using`" > > When I change it to this (protect ? in single quotes) the mged-regress works: > > cmds="`$MGED -c mged.g '?' 2>&1 | grep -v Using`" > > So what is going on? > > Best, > > -Tom > > ------------------------------------------------------------------------------ > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-d2d > _______________________________________________ > BRL-CAD Developer mailing list > brl...@li... > https://lists.sourceforge.net/lists/listinfo/brlcad-devel |
From: Tom B. <tom...@gm...> - 2012-01-20 01:45:13
|
On Thu, Jan 19, 2012 at 18:45, Clifford Yapp <cli...@gm...> wrote: > Um... got me there. I'm not seeing that issue... what platform are > you running on? In particular, what shell is being used for sh? Any > sh script gurus recognize those symptoms? I'm on Ubuntu 10.10 and I think they now use dash behind the scenes. Best, -Tom |
From: Tom B. <tom...@gm...> - 2012-01-20 01:47:11
|
On Thu, Jan 19, 2012 at 19:44, Tom Browder <tom...@gm...> wrote: > On Thu, Jan 19, 2012 at 18:45, Clifford Yapp <cli...@gm...> wrote: >> Um... got me there. I'm not seeing that issue... what platform are >> you running on? In particular, what shell is being used for sh? Any >> sh script gurus recognize those symptoms? > > I'm on Ubuntu 10.10 and I think they now use dash behind the scenes. I just checked my environment and it shows SHELL=/bin/bash. -Tom |
From: Tom B. <tom...@gm...> - 2012-01-20 03:50:31
|
On Thu, Jan 19, 2012 at 11:36, Tom Browder <tom...@gm...> wrote: ... > In regress/mged.sh there is this line which seems to cause the problem: > > cmds="`$MGED -c mged.g ? 2>&1 | grep -v Using`" > > When I change it to this (protect ? in single quotes) the mged-regress works: > > cmds="`$MGED -c mged.g '?' 2>&1 | grep -v Using`" Can someone try my fix and see if it causes a problem? I don't know why it works and the other doesn't, but maybe it works ANYWAY for all and is acceptable for a check in. I defer to the shell expert, Sean. Best, -Tom P.S. And none this comes close to asking (or explaining) why it stopped working all of a sudden! |
From: Christopher S. M. <br...@ma...> - 2012-01-20 04:01:36
|
On Jan 19, 2012, at 10:49 PM, Tom Browder wrote: > On Thu, Jan 19, 2012 at 11:36, Tom Browder <tom...@gm...> wrote: > ... >> In regress/mged.sh there is this line which seems to cause the problem: >> >> cmds="`$MGED -c mged.g ? 2>&1 | grep -v Using`" >> >> When I change it to this (protect ? in single quotes) the mged-regress works: >> >> cmds="`$MGED -c mged.g '?' 2>&1 | grep -v Using`" > > Can someone try my fix and see if it causes a problem? I don't know > why it works and the other doesn't, but maybe it works ANYWAY for all > and is acceptable for a check in. > > I defer to the shell expert, Sean. You have a single-character file in your directory, probably named 't'. The question mark is a special glob character matching a single character. Nobody's ever happened to have a file with a single character in their directory, so it's always gotten passed to mged as a literal '?'. You hit a double-whammy. With the filename match on the glob and a valid command at that, it's invoking "mged -c mged.g t", getting a table of contents, and processing the resulting object list as commands. Your fix to wrap it in single quotes is the right fix. Cheers! Sean |
From: Tom B. <tom...@gm...> - 2012-01-20 12:33:23
|
On Thu, Jan 19, 2012 at 22:01, Christopher Sean Morrison <br...@ma...> wrote: ... > Your fix to wrap it in single quotes is the right fix. Some would say "better to be lucky than good!" Cheers! -Tom |