It should find what I pass it! Another hint: Administrator@druffer / $ /usr/src/gforth/gforth-ditc.exe -i /usr/src/gforth/gforth.fi GForth 0.5.9-20030201, Copyright (C) 1995-2003 Free Software Foundation, Inc. GForth comes with ABSOLUTELY NO WARRANTY; for details type `license' Type `bye' to exit bye
Administrator@druffer / $ cd usr Administrator@druffer /usr $ /usr/src/gforth/gforth-ditc.exe -i /usr/src/gforth/gforth.fi /usr/src/gforth/gforth-ditc: cannot open image file /usr/src/gforth/gforth.fi in path .:/usr/local/lib/gforth/site-forth:/usr/lo cal/share/gforth/site-forth:/usr/local/lib/gforth/0.5.9-20030201:/usr/local/ share/gforth/0.5.9-20030201 for reading It I'm in root, then root paths work. If not there, they don't! DaR > -----Original Message----- > From: Anton Ertl [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 05, 2003 9:16 AM > To: [EMAIL PROTECTED] > Subject: Re: [gforth] New snapshot available > > > Dennis Ruffer wrote: > > > > An interesting progression: > > > > Administrator@druffer /usr/src/gforth > > $ ./gforth-ditc.exe -i kernl32l.fi > > GForth 0.5.9-20030201, Copyright (C) 1995-2003 Free > Software Foundation, > > Inc. > > GForth comes with ABSOLUTELY NO WARRANTY; for details type `license' > > Type `bye' to exit > > bye > > > > Administrator@druffer /usr/src/gforth > > $ cp kernl32l.fi /usr/local/share/gforth/0.5.9-20030201/gforth.fi > > > > Administrator@druffer /usr/src/gforth > > $ ./gforth-ditc.exe > > ./gforth-ditc: cannot open image file gforth.fi in path > > > .:/usr/local/lib/gforth/site-forth:/usr/local/share/gforth/sit > e-forth:/u > > > sr/local/lib/gforth/0.5.9-20030201:/usr/local/share/gforth/0.5 > .9-20030201 > > for reading > > > > Administrator@druffer /usr/src/gforth > > $ ./gforth-ditc.exe -i /usr/src/gforth/kernl32l.fi > > ./gforth-ditc: cannot open image file > /usr/src/gforth/kernl32l.fi in path > > .:/usr/local/lib/gforth/site-forth:/usr/local/share/gf > > > orth/site-forth:/usr/local/lib/gforth/0.5.9-20030201:/usr/loca > l/share/gforth > > /0.5.9-20030201 for reading > > > > Apparently, the image opening mechanism can not handle a > full path. It > > seems to do a relative path fine, but as I demonstrated > above, the fully > > qualified path is failing. > > Maybe a problem because ':' is used as path separator? OTOH, you > don't use a drive spec in the path, so this should not matter. > > - anton > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
