Closed cvgaviao closed 6 years ago
I had the exact same issue. Also, whenever I tried to run a simulation it would complain about not being able to find 'qucsator'. Not sure if that's related to this build error though. In the end I was able to fix it by making a hardlink from /qucs/bin/qucsator to /qucs/qucs-core/qucsator. Simply moving the binary failed as it couldn't find some shared libraries it depends on.
ln ./qucs-core/qucsator ./qucs/bin/qucsator
in general, building the docs can be skipped by passing --disable-doc
to configure
. All the documentation is also available already in pdf
format on Sourceforge.
@leon-vv did you make install
also? Running Qucs from the build directory does not work.
did you make install also?
Yes, I tried without success. I retried running the following commands:
./bootstrap
./configure --disable-doc
make
sudo make install
I still get the same error in the dialog titled 'Qucs Simulation Messages':
ERROR: Cannot start /usr/local/bin/qucsator (No such file or directory)
Running Qucs from the build directory does not work.
Well, doing the following is actually the only way I got the simulation to work:
If qucs is not meant to be ran from the build directory it is helpful if you put this into the Readme. I (and probably other people) always run programs I compile myself from the build directories. This way I don't have to run code with root privileges and I don't pollute my file system.
If qucs is not meant to be ran from the build directory
that bug has been fixed 1.5 years ago. see #660.
have to run code with root privileges and I don't pollute my file system.
exactly. read the discussion... e.g. #374
that bug has been fixed 1.5 years ago. see #660.
Then please tell me what I've done wrong while following the build instructions in the Readme.
exactly. read the discussion... e.g. #374
Why do I have to read a long discussion about technical stuff I'm not familiar with? I'm simply contributing a bug report.
Then please tell me what I've done wrong
you did nothing wrong (the fix has not been merged.)
I'm simply contributing a bug report.
thanks for that, i totally see your point. however, if you want to improve qucs, then a bug report is not sufficient. unfortunately, you need to argue that what you found is really a bug. sometimes that takes a week. sometimes a year. sometimes more.
maybe you can test or upvote the fix i wrote?
you did nothing wrong
Good to know. It's a pity though that the build instructions listed in the Readme don't work for me (even after running sudo make install
). This way other people are probably unable to use this (amazing!) software. But of course this is not your fault.
(the fix has not been merged.)
Sorry, failed to notice. I have upvoted the pull request. Hopefully it's merged soon.
Should be fixed with the merge of #660.
I'm trying to build from source using ubuntu xenial. The installed octave is default 4.0.0-3ubuntu9.1.
Then I'm having this error:
I have tried to open some of those Qucs's .m files using the octave desktop and it crashed.
I was able to build qucs and qucs-core without problem, so the issues is only in qucs-doc.