I'm looking to debug configure script created by autoconf to exactly know where it fails to find specific dependency. I see variable ac_status which comes to check after eval command in configure script which redirects output always to &5.
Where could I find information about ac_status - what it means, where can be it defined and by whom and how it works? Thank you.
Sorry, just variable to check ret val. Please, skip this question.
Related
I'm installing Pintos to check if it's installed properly.
pintos -- run alram-multiple
If I type it, it comes out like that.
i dont know os.dsk..
plz help me
Have you activated your sources by running 'source ./activate' command at the very top path of your project?
Did your program compile fine? if not, make sure you defined the functions that you used. but if you did, you probably need to activate a source at the root of the program.
I have been looking for solutions to this problem for a couple of days and have not found a suitable one.
Currently i have two lines of code in my shell script file.
cd /app/jboss/sample_project/bin
./jboss-cli.sh -c --controller=$hostnameVal:$jboss_port_no1 --user=$jboss_id --password=$jboss_pwd --command="deploy --force /sample/uploaded/sample-1.0.war --runtime-name=sample-1.0.war"
I am facing this error:
'--force' is assumed to be a command(s) but the commands to execute have been specified by another argument: [deploy]
I think it has something to do with the spaces between deploy and --force but I can't seem to find a solution to this. Would really appreciate if someone can shed some light. Thank you!
The root cause of the issue was due to the space between the deploy command and the file path, therefore jboss was not be able to find the parameter the properly.
Hence, a work around for this which I have found out is to create a cli file, write the deploy command in the cli file and pass the file as an input in the script that i am writing.
Do you observe the same problem in a terminal?
The google app engine cli commands cannot be found in the python sdk. I've already checked the google_appengine file. The shell commands are there, and I already added the app engine file path to the PATH variable. I echo the PATH variable and the directory to the app_engine file shows up, but still shows not found when I try to use a command that's inside the file. If I reference the command directly by using its whole path, the command works, but otherwise it won't. Is there anything else that needs to be done to reference a command in shell?
More error info please,
If I reference the command directly by using its whole path, the command works
I think your python path maybe wrong, Python 2.6 is not supported.
so are you have mulit-version python?
Thank you for your contributions everyone. It turns out the path I was using was wrong. Instead of /home/Programs/Apps/google_appengine it should have been /home/Programs/google_appengine. I guess the shell doesn't check to see if the path you add to the PATH variable actually exists. Who knew? Not me
Until I run into another problem stack overflow--which may be soon
See ya
This question might not be related to npm specifically, but more about command lines in general.
I have installed Dredd (https://github.com/apiaryio/dredd) and I am trying to execute a command that needs to look like this:
dredd <path to blueprint> <api_endpoint> [OPTIONS]
Do the first two arguments need to be strings (wrapped with quotes)?
If I want to pass an output option with -o (or --output), Dredd specifies it needs to be an array. How do I pass an array in command line?
I have tried running
dredd services/address.md http://example.com -c false
I can see the command running, which tells me that the first two arguments don't necessarily need to be strings (I also tried with strings and it still works...), but the color option that is -c is suppose to disable the colors in the console when set to false, but it doesn't, so I'm probably calling the options wrong. Every option I try has no effect.
Hopefully you can help me!
Handling of CLI arguments is very implementation specific for each npm, so there is no general rule. There are many libraries to help create command-line tools for example commander or optimist. For specific behaviour please refer to these packages.
But in this case it might be a bug. It does not work for me neither. Even if I change default for color output to true directly in the source-code of Dredd package. I filed an issue about that.
This question is related to
Nodejs Child Process with Unix Executable.
However I could not find a good solution and thanks to my reputation points, I am unable to post a comment there.
To explain my problem, I have some of my own executables which I need to execute from node.js. The path for these executables is already set in the PATH variable. Hence, I can run my executables without any path-prefix from Terminal.
Inspite of that, node.js receives process.env.PATH set to following value:
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
I tried appending the path to it before spawning the process:
process.env.PATH = process.env.PATH + ":<path_to_my_executables>"
but the process exits with 127 Shell code which is "command not found" if I correctly remember.
Any ideas?
Thank you in advance!
Okay, I got it work using a shell script. Definitely there must be a better solution to this.
I exported the required paths to my executable (and its dependencies) in the shell script first and then started execution. Hence the shell script structure is something like:
export JAVA_HOME=<java_path>
export EXECUTABLES_HOME=<executables_path>
export PATH="$PATH:$JAVA_HOME/bin:$EXECUTABLES_HOME"
<execute_required_executable> <arguments>
If someone has a better solution, please do let me know!