3/27 10:22:09 term Node 3 TypeError: options is null
/usr/bin/env: \u2018usr/bin/dosemu.bin\u2019: No such file or directory
and whereis does state dosemu.bin exists at /usr/bin
btw, I updated the source again this morning, today, just the same as the last few days when building there has been an binary file popping up in the build directory that is unnamed
, I renamed it, ran it, at it appears to be
chksmb, even though the build process is building a chksmb it is the same size as chksmb also 152176 as of now.
But back to these errors with DOSEmu, etc, I don't know what could be causig the type error, Rob, I've replace xtrn_sec.js with one directly from CVS to be sure and I'm still getting these errors.
/usr/bin/env: \u2018usr/bin/dosemu.bin\u2019: No such file orThose "\u2018" are unicode characters. Maybe you pasted them and they're supposed to be regular (ASCII) quotes or something else? I'm pretty sure that would be a problem right there.
directory
Huh? You can't have a file that is "unnamed".
I'm not really sure what you meay by file or directory that is "unnamed". Please clarify.
A different .js then.
A different .js then.
Ok, I'm still working with it..
Huh? You can't have a file that is "unnamed".
Yes, strange enough when you do an ls after the build it is showing up as just nothing the only way I was able to see it was in MC "Midnight Commander" where it only showed the file size.
no crapping you man.
if it had a name, it was named " " <-- the dark void between the quotes.
By: Nightfox to KK4QBN on Tue Mar 27 2018 12:54:46
Could it be that the file/directory name was spaces? That "dark
void" might just be a space (and how do you know it's only one
character of dark void?)
Could it be that the file/directory name was spaces? That "dark void" might just be a space (and how do you know it's only one character of dark void?)
Nightfox
here is an ls -l of my /sbbs/src/sbbs3/gcc.linux.x64.exe.release build,
-rwxr-xr-x 1 kk4qbn kk4qbn 152176 Mar 4 15:24
-rwxr-xr-x 1 kk4qbn kk4qbn 152176 Mar 15 02:44 chksmb
Re: Still problems
By: KK4QBN to Nightfox on Wed Mar 28 2018 08:27:26
By: Nightfox to KK4QBN on Tue Mar 27 2018 12:54:46
Could it be that the file/directory name was spaces? That "dark
void" might just be a space (and how do you know it's only one
character of dark void?)
here is an ls -l of my /sbbs/src/sbbs3/gcc.linux.x64.exe.release build, these were built on the 15th of march, I also had a build do it yesterday, but after renaming the file and telling you guys about it I ran the cleanall script and tried to replicated it in the actual folder I build my working executables in, but this is how I noticed it.. I knew I was'nt high :)
-rwxr-xr-x 1 kk4qbn kk4qbn 152176 Mar 4 15:24
-rwxr-xr-x 1 kk4qbn kk4qbn 294888 Mar 15 02:44 addfiles
-rwxr-xr-x 1 kk4qbn kk4qbn 152176 Mar 4 15:24
-rwxr-xr-x 1 kk4qbn kk4qbn 152176 Mar 15 02:44 chksmb
you can also see the file size is the same...
here is an ls -l of my /sbbs/src/sbbs3/gcc.linux.x64.exe.release
build,
you should try "ls -lQ" instead...
-rwxr-xr-x 1 kk4qbn kk4qbn 152176 Mar 4 15:24
-rwxr-xr-x 1 kk4qbn kk4qbn 294888 Mar 15 02:44 addfiles
That's a first for me. Are you saying if you remove the file it gets recreated too?
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 31 |
Nodes: | 8 (0 / 8) |
Uptime: | 86:41:14 |
Calls: | 2,069 |
Calls today: | 2 |
Files: | 11,134 |
Messages: | 946,735 |