I made an archive in which there are the next files: tema1.c (code), Makefile, input.txt, output.txt, and when I upload it on vmchecker(it's a homework checker), after compiling, at EXECUTING TESTS, I receive this error: file 'tema1" is not in the same directory as this script. What does it mean?
Related
I have installed the IUP GUI for Lua (https://www.tecgraf.puc-rio.br/iup/, the website is in English, although it doesn't look like it). I have tried running IUP on my computer using their tutorial code:
require("iuplua")
iup.Message("Hello World 1","Hello world from IUP.")
-- to be able to run this script inside another context
if (iup.MainLoopLevel()==0) then
iup.MainLoop()
iup.Close()
end
but whenever I do I get this error: module 'iuplua' not found and then I get a bunch of other errors below that :
no field package.preload['iuplua']
no file '.\iuplua.lua'
no file 'C:\Users\user\bin\lua\iuplua.lua'
no file 'C:\Users\user\bin\lua\iuplua\init.lua'
no file './iuplua.lua'
no file './iuplua/init.lua'
no file './lua/iuplua.lua'
no file './lua/iuplua/init.lua'
no file 'C:\Users\user\lualibs/iuplua/iuplua.lua'
no file 'C:\Users\user\lualibs/iuplua.lua'
no file 'C:\Users\user\lualibs/iuplua/iuplua/init.lua'
no file 'C:\Users\user\lualibs/iuplua/init.lua'
no file '.\iuplua.dll'
no file 'C:\Users\user\bin\iuplua.dll'
no file 'C:\Users\user\bin\loadall.dll'
no file 'C:\Users\user\bin/clibs/iuplua.dll
This occurs even if I put the file I'm running into the srclua5 folder which contains a file called "iuplua.lua". Why does this occur? Could someone please help?
i am trying to RSync files from a folder, however i would like to define a subset of these files.
I have created a text file with the wildcard names but i get a "no such file" error.
below is my source directory file list, the names will always be there, but the date/time will change so i am using the *wildcard to grab file.
20200207-COE-2020-02-06T2332238.SCH
20200207-SMXH-2020-02-06T23140696.SCH
20200207-SMXH alias-2020-02-06T23140766.SCH
20200128-SARE-2020-01-28T15202081.SCH
20200128-SARH alias-2020-01-28T15161179.SCH
my source list - i tried by entering the wild character in this and in the rsync command line
*SMXH*
*COE*
*SMXH\ alias*
my rsync command
rsync -tv --files-from=/var/tmp/red_badger/bus_names.txt "foo#bar:/apps/schedules/archived/" /var/tmp/red_badger/files --dry-run
error message
receiving file list ... rsync: link_stat "/apps/schedules/archived/*SMXH*" failed: No such file or directory (2)
rsync: link_stat "/apps/schedules/archived/*COE*" failed: No such file or directory (2)
rsync: link_stat "/apps/archived/*SMXH\ alias*" failed: No such file or directory (2)
using the wild card works in one line command
rsync -tv "foo#bar:/apps/schedules/archived/*SMXH\ alias*" .
The --files-from option is for specifying exact filename matches. To use patterns instead of actual file names, use the --include-from option instead.
I have a problem with invoking gcov, it keeps returning - No such file or directory.
When I call
localhost:R-3.0.1 romantsegelskyi$ gcov src/main/eval.c
eval.c: No such file or directory
However file itself and information needed for gcov exists.
localhost:R-3.0.1 romantsegelskyi$ ls src/main/eval*
src/main/eval.c src/main/eval.d src/main/eval.gcda src/main/eval.gcno src/main/eval.o
I have tried specifying --object-directory but still no luck
localhost:R-3.0.1 romantsegelskyi$ gcov src/main/eval.c --object-directory=./src/main
eval.c: No such file or directory
Strangest thing is that it is only the case on OSX, on Linux everything works fine as intended. Any ideas?
Same behavior !! And more strange : I get the result (the .gcov file), following this mesg !! Perhaps, you have the result too ?
There two aspects in the problem :
gcov manual said that gcov should execute by default in the directory where the object file and the gcov data files are. The first and simplest working solution is : go in the appropriate directory and execute gcov cd src/main; gcov eval.c
why the --object-directory=... arg seems not working ? Because the expected value is a directory name and in the example given, it is a file name. So you should write --object-directory=src/main (this work too)
or --object-file=src/main/eval.c (according to the doc. I haven't tried this !)
I've tried using the suggestions in this thread to no avail: How to use copyfile when there are spaces in the directory name?. To be clear, the directory I'm using is already in double-quotes, and I've tried escaping the spaces, but still get the same error. This is the error message I get:
Error: Failed to open PDF file:
C:/Documents
Error: Failed to open PDF file:
and
Error: Failed to open PDF file:
Settings/cpengelly/My
Error: Failed to open PDF file:
Documents/Dropbox/theproject/tmp/working/main
Error: Failed to open PDF file:
pdf.pdf
Errors encountered. No output created.
Done. Input errors, so no output created.
What is going on here?
you just need to put your directory name in double quotes. example -
FileUtils.cp("C:\\Program Files\\FileZilla\\dbghelp.dll","c:\\temp")
Occasionally, we receive ZIP files from our suppliers that are seemingly corrupted. Attempting to list the contents of a ZIP will trigger an error like this:
$>unzip -qql JABL_VER_20120808_165910.zip
unzip: cannot find or open JABL_VER_20120808_165910.zip, JABL_VER_20120808_165910.zip.zip or JABL_VER_20120808_165910.zip.ZIP.
I did a quick read of the unzip man page and coded that snippet to trap the above error
EXIT=`echo $?`
case $EXIT in
> 0-1) echo "Unzip Complete.";;
> *) echo "Unzip Failed.";;
> esac
$>Unzip Failed.
It seems to work. However, there are cases like this one where the error is different:
$>unzip -qql JABL_VER_20120808_175915.zip
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of JABL_VER_20120808_175915.zip or
JABL_VER_20120808_175915.zip.zip, and cannot find JABL_VER_20120808_175915.zip.ZIP, period.
Is there a "surefire" way to trap errors like these?
PS: Not sure if matters but the ZIP files are generated on MS Windows ; We use Red Hat.
exit code 1 isn't good either,
1 one or more warning errors were encountered, but processing completed successfully anyway. This includes zipfiles
where one or more files was skipped due to unsupported compression method or encryption with an unknown password.
you should try
unzip -t zipfilename
and only accept exit code 0
why do you have so many errors? ftp'd file in text mode?