I'm following a tutorial to install a program on an RHEL environment and I've overcome some errors up until this point. I'm at the end of the installation process, attempting to confirm the validity through "make test", which returns the following error:
[user#localhost verilator-4.018]$ make test
Can't open perl script "/bin/verilator": No such file or directory
...
[Makefile:228: smoke-test] Error 10
I first checked to see if there was a verilator-4.018/bin/verilator file, which there was.
I then tried researching the error online and got a single result, where a user stated the issue could be solved by "Setting VERILATOR_ROOT to the root of your checkout", but I'm not too sure how to interpret this since I'm a beginner.
I tried setting as root:
[root#localhost verilator-4.018]# make test
But got the same error messages.
Also, please let me know how I can rephrase the title to make it more specific. I thought it was difficult to be specific about a question where I need interpretation help.
There is no /bin/verilator ... there is bin/verilator. But it's more tricky than that : The tests are done with test_regress/driver.pl, so "bin/verilator" is one level up.
Edit test_regress/driver.pl, line 782 to
my #cmdargs = ("perl", "$ENV{VERILATOR_ROOT}../bin/verilator",
... and the firsts tests can be run.
More bugs : "smoke-test" fails : Will use a file from the install destination. Please do # make install ... and the next tests can also be run.
Test result → make-test__result.txt https://www.dropbox.com/s/tebcqj7bl5dkzx8/make-test__result.txt?dl=0
Please notice the SYSTEMC settings. verilator was built with $ export SYSTEMC_INCLUDE=/usr/local/include/ && export SYSTEMC_LIBDIR=/usr/local/lib-linux64 && ./configure && make
SYSTEMC is required for the tests to pass. See verilator/README
Related
I am getting this error when running "behave -f" command, I have init.py file in steps,feature folder. Please let me know if there is any solution.
I tried running the feature for generating reports.
this question is not clearly formuled, there are details missing here. You must add something like a capture or similar to show us the directory tree you have in your project or so.
The init.py file doesn't matter to run behave. I'll show you an Hello-World project that works with the proper output of running the command behave in the command line.
If you need some other help, please, add more information about your question.
I'm working on the sources of an application an have the release version of the application installed on the system.
How can i test the modified (and possibly buggy) application without conflicting with the version installed ?
What I want is basically virtual env but for generic applications.
I tried Docker but this has several issues :
I can't get the X11 redirection working. I tried commands like docker run -ti --net=host -e DISPLAY=:0.0 test-docker-geany or docker run -ti -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix test-docker-geany according to some forum threads.
The docker build involves copying the whole codebase to the image as well as installing all the tools and libraries needed to compile which some are not stored in cache and installed each time. So the script takes several minutes each time you want to compile and run.
So my questions are :
Is docker the best solution for such task ? I'm sure this is a problem a lot open source contributors faces but I couldn't find other cases on the net.
If it is not the best solution what are the alternatives ?
Detailed error :
I ran the commands xhost + and the first one I gave in my first issue and I got :
The program 'geany' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 173 error_code 2 request_code 130 minor_code 3)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
The Dockerfile : https://pastebin.com/p03vaWbU
The warning was finally the cause : i just had to install gtk2-engines-pixbuf according to this thread
EDIT : I misunderstood the success. I get it to work that time because I ran an other GUI program in the docker before. In fact, I finally discovered that trying geany a second time just works although the first try give the error.
Description
Trying to install pilfs (the LFS for raspberry) on my raspberry pi 3. I'm following the guide as posted here: http://www.intestinate.com/pilfs/guide.html
I'm currently following their "chapter 8"
8 Building Chapter 5 [5.4. Binutils - Pass 1]
Alright, this is the moment of truth. Will you make your way through
chapter 5 slow and steady, or just execute the build script and go do
something else for 30 hours? This is for you to decide ... I've done
both :)
Also, here is where you might want to start a tmux or screen session.
Because if you break your ssh connection or your router has a hickup,
your build will just stop.
So you've made up your mind? Okey, script runners, start your engines:
cd $LFS/sources
chmod +x
ch5-build.sh
./ch5-build.sh
The script will report your SBU time after the first binutils build has finished, mine
is usually around 1 hour.
For those brave souls who are working through the chapter by hand,
check out the about page and read the build scripts to figure out
what's going on.
Error
When I do ./ch5-build.sh, it's causing the following mesage:
Not running as user lfs, you should be!
Question:
What step did I miss for this to happen? How do I run myself as a "lfs user"?
You need to enter su - lfs in the command line and then enter your password. This is assuming you have created the lfs user earlier in the book. From there, you can run the shell script.
I was installing this program: THERMUS, that, as i know should install fine. I/m installing this program through ubuntu console. But when i run make all i got this message:
make: ***No rule to make target '/main/TTMParticle.h', needed by 'BQConstrainQ.o'. Stop.
I know that it could be caused by the fact that file TTMParticle.h doesn't exist in /main/, but i checked - it's there.
Your environment variable THERMUS is not properly set. The build instructions mention:
3 . Set an environment variable `THERMUS' to point at the top-level
directory containing the THERMUS code
It does not mention that you have to do export THERMUS to make that variable available to other processes, like make, so you might have forgotten that -- or not have set THERMUS at all. Without actually having tried it, I think the fastest way to get rid of this message is to run make as follows:
THERMUS=.. make all
To track down the issue, check out the file functions/makefile where you problem occurs. It mentions:
SEP_CLASSESH = $(THERMUS)/main/TTMParticle.h \
and later contains the dependency
$(FNCSO): $(FNCSS) $(SEP_CLASSESH)
which is the line that causes the actual error, because
FNCSO = BQConstrainQ.o \
All of a sudden, scheduled tasks that update the Cognos Cubes are getting failed. When I try to run it manually from the CMD it is getting executed successfully. But, when I try to create a bat file and run the below script nothing is happening. Could someone look into this and let me know if anything is wrong.
#echo on
C:
cd "C:\Program Files (x86)\ibm\cognos\c10\bin"
Cogtr.exe -n2 -m "C:\Cognos\cube models\test.mdl"
Guess your formatting got awry when posting to the forum, but in general it looks ok.
When you say “nothing happens” — there might be a cogtr process in background you don't see.
You're running with n2 command line syntax, making Transformer run “background”
http://pic.dhe.ibm.com/infocenter/cbi/v10r1m0/index.jsp?topic=%2Fcom.ibm.swg.im.cognos.ug_cogtr.10.1.0.doc%2Fug_cogtr_id13215n_option.html
Check Task Manager to see if that's the case. You can change the line to just -n to see a bit more action )