While attempting to use Quarto on JupyterNotebook, Quarto gives the following error on quarto render yippee.ipynb --to html:
/usr/local/bin/quarto: line 7: dirname: command not found
/usr/local/bin/quarto: line 8: readlink: command not found
/usr/local/bin/quarto: line 9: basename: command not found
/usr/local/bin/quarto: line 12: dirname: command not found
/usr/local/bin/quarto: line 23: basename: command not found
ERROR: Cannot determine the Quarto source path. This script must be run from the bin or common folder.
I tried to execute the mere Quarto, which gave the (exact) same error. Thanks.
Related
I am trying to install tin on a CentOS 7 VM. ./configure runs fine, and then when I run make build, I get...
[user#db3 tin-2.4.5]$ make build
make[1]: Entering directory `/home/user/tin-2.4.5/src'
expect 6 shift/reduce conflicts ...
./parsdate.y
./parsdate.y: line 1: fg: no job control
./parsdate.y: line 2: /bin: Is a directory
./parsdate.y: line 3: active.c: command not found
./parsdate.y: line 4: active.c: command not found
./parsdate.y: line 5: active.c: command not found
./parsdate.y: line 6: active.c: command not found
./parsdate.y: line 7: active.c: command not found
./parsdate.y: line 8: active.c: command not found
./parsdate.y: line 9: syntax error near unexpected token `newline'
./parsdate.y: line 9: ` * Originally written by Steven M. Bellovin <smb#research.att.com>'
make[1]: *** [parsdate.o] Error 2
make[1]: Leaving directory `/home/user/tin-2.4.5/src'
make: [build] Error 2 (ignored)
Can someone tell me what I'm doing wrong?
Thanks.
I ran into the exact same problem, and in the same environment.
From what I can tell, at this point you may just need to:
./configure
make clean
make build
Rerunning ./configure after installing bison and chmod 777'ing parsdate.y is how I fixed the compilation errors but it seems you already did the bison part and chmod part.
So I'm running into some trouble using dual_regression. The problem here is that I'm using the following command and getting the following error:
> macminngh:session_one_and_three sondosayyash$ dual_regression /Users/sondosayyash/Downloads/FIX_sNorm/40_subjects.gica/groupmelodic.ica/melodic_IC.nii.gz 1 -1 5000 dualreg_40subj_output.dr 'cat /Users/sondosayyash/Desktop/Users.txt'
/Users/sondosayyash/abin/fsl/bin/dual_regression: line 126: [: too many arguments
mkdir: dualreg_40subj_output.dr: File exists
mkdir: dualreg_40subj_output.dr/scripts+logs: File exists
creating common mask
/bin/sh: line 1: syntax error near unexpected token `dualreg_40subj_output.dr/scripts+logs/drA'
/bin/sh: line 1: `file (dualreg_40subj_output.dr/scripts+logs/drA) does not exist -T 5 -N drB -l dualreg_40subj_output.dr/scripts+logs dualreg_40subj_output.dr/scripts+logs/drB'
doing the dual regressions
sorting maps and running randomise
/bin/sh: line 1: you: command not found
I don't know where I'm going wrong.
As for the text file listed as 'Users.txt' has many different file directories to filtered_func data.
I have a feeling there is a problem with the text file but I'm not entirely sure.
I have an AEM 6.3 server on Linux(RedHat). It is being getting started from command line without any issues with below command-
java -jar aem-author-4502.jar
But I am not able to start the server from start script and getting below error-
# ./start.bat
./start.bat: line 1: #echo: command not found
./start.bat: line 2: ::: command not found
./start.bat: line 3: $'::\r': command not found
./start.bat: line 4: ::: command not found
./start.bat: line 5: ::: command not found
./start.bat: line 5: $'e.g.,\r': command not found
./start.bat: line 6: $'::\r': command not found
./start.bat: line 7: ::: command not found
: No such file or directoryt.bat
./start.bat: line 8: $'::\r': command not found
./start.bat: line 9: $'setlocal\r': command not found
./start.bat: line 10: $'\r': command not found
./start.bat: line 11: ::*: command not found
./start.bat: line 17: syntax error near unexpected token `('
'/start.bat: line 17: `::* runmode(s)
Also, I am not able to set the AEM as service (linux)..
What could be the reason for this?
One thing that I observed is I don't have cq.pid file in my crx-quickstart/conf folder..
start.bat is a Batch file, one you would run on a Windows OS.
What you need to run is a similar shell script that you should find just next to the one you're trying to execute. It should be present in the <cq_installation_directory>/bin directory.
As per the official documentation, Simply running ./start should do the trick on Linux.
I have a crontab file that is no longer allowing me to edit it. When executing
/usr/bin/crontab -e
I get the following output
/usr/bin/crontab: line 8: 15: command not found
/usr/bin/crontab: line 9: 40: command not found
/usr/bin/crontab: line 10: 45: command not found
/usr/bin/crontab: line 11: 00: command not found
/usr/bin/crontab: line 12: 00: command not found
/usr/bin/crontab: line 13: 00: command not found
/usr/bin/crontab: line 14: 45: command not found
/usr/bin/crontab: line 15: 50: command not found
Is there a way for me to reset this file to a default version. All commands on the crontab fail with the same error so I not able to use
/usr/bin/crontab -r
to remove it. Thanks for your assistance
I am installing hubot on Linux, and followed the instructions, receiving no errors.
However, when I try to actually run my hubot, I encounter problems. First I tried daemonizing hubot according the the instructions at the very end of the linked tutorial. start hubot returned the error start: Unknown job: hubot. So I backed up and tried /opt/hubot/bin/hubot --name Ro\ Bot --adapter campfire and got this series of errors:
/opt/hubot/bin/hubot: line 11: Hubot: command not found
/opt/hubot/bin/hubot: line 12: Fs: command not found
/opt/hubot/bin/hubot: line 13: Path: command not found
/opt/hubot/bin/hubot: line 14: HTTP: command not found
/opt/hubot/bin/hubot: line 15: Creator: command not found
/opt/hubot/bin/hubot: line 16: OptParse: command not found
/opt/hubot/bin/hubot: line 18: Switches: command not found
/opt/hubot/bin/hubot: line 19: [: missing `]'
/opt/hubot/bin/hubot: line 20: [: missing `]'
/opt/hubot/bin/hubot: line 21: [: missing `]'
/opt/hubot/bin/hubot: line 22: [: missing `]'
/opt/hubot/bin/hubot: line 23: [: missing `]'
/opt/hubot/bin/hubot: line 24: [: missing `]'
/opt/hubot/bin/hubot: line 25: [: missing `]'
/opt/hubot/bin/hubot: line 26: [: --version,: binary operator expected
/opt/hubot/bin/hubot: line 27: ]: command not found
/opt/hubot/bin/hubot: line 29: Options: command not found
/opt/hubot/bin/hubot: line 30: adapter:: command not found
/opt/hubot/bin/hubot: line 31: alias:: command not found
/opt/hubot/bin/hubot: line 32: create:: command not found
/opt/hubot/bin/hubot: line 33: enableHttpd:: command not found
/opt/hubot/bin/hubot: line 34: name:: command not found
/opt/hubot/bin/hubot: line 35: path:: command not found
/opt/hubot/bin/hubot: line 37: syntax error near unexpected token `('
/opt/hubot/bin/hubot: line 37: `Parser = new OptParse.OptionParser(Switches)'
Attempting to install from release package instead of cloning in git results in different errors earlier in the process:
root#server:/opt# wget https://github.com/downloads/github/hubot/hubot-2.2.0.tar.gz
root#server:/opt# npm install
npm ERR! Couldn't read dependencies.
npm ERR! Error: ENOENT, no such file or directory '/opt/package.json'
npm ERR! System Linux 2.6.35.4-rscloud
npm ERR! command "node" "/usr/local/bin/npm" "install"
npm ERR! cwd /opt
npm ERR! node -v v0.6.9
npm ERR! npm -v 1.1.0-3
npm ERR! path /opt/package.json
npm ERR! code ENOENT
npm ERR! message ENOENT, no such file or directory '/opt/package.json'
npm ERR! errno {}
npm not ok
I tried npm cache clean but it didn't help.
I don't know what to make of it and I'm not very familiar with Hubot or any of the frameworks it runs on, so any information for how to start troubleshooting this would be helpful.
Try installing from the release package (Instead of installing from git clone), that solved some random issues for me.
I suspect you didn't follow the "Installing dependencies" section of the "Deploying Hubot onto UNIX" link you referenced above. Specifically, it appears that a regular shell such as bash is trying to interpret the script rather than the coffee-script interpreter. If you enter
coffee
at your shell prompt and do not get the
coffee>
prompt, revisit the first part of the install instructions.