./configure says "Now type `make' to compile MonoDevelop"
when i issue make command there is the following error occurs:
LANG=C mono ${S}/scripts/configure.exe gen-buildinfo ./build/bin
/usr/bin/git blame version.config
fatal: Not a git repository (or any of the parent directories): .git
That's correct - it is not a git repository, because sources are unpacked from tarball (from github tag).
I don't understood:
1) how previous monodevelop-5.0.1.ebuild works through this
2) why i receive error "Unknown argument --build=x86_64-pc-linux-gnu" error when ebuild calls ./configure
Tarballs should be created via make dist, not via the "extract as a tarball" function from github.
You have some already-generated tarballs of monodevelop here.
Related
I'm trying to compile a cmake project on a RasberryPi with Fedora Arm 36 and in cmake I use pkg-config. It is correctly installed but I get this error:
/usr/bin/pkg-config: line 8: /usr/bin/armv7hnl-redhat-linux-gnueabi-pkg-config: No such file or directory
In the /usr/bin directory there is a file called armv7hl-redhat-linux-gnueabi-pkg-config (missing n in armv7hnl) is this a bug?
What can I do?
Edit
I've reinstalled pkg-config but still the same error.
/usr/bin/pkg-config is just a bash script that calls the appropriate executable and so I hard coded the one previously mentioned, I don't get an error but pkg-config can't find gtkmm-4.0 which is installed.
I am trying to run Puppeteer on my new laptop. However, I am getting this error:
node:8144) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process!
/mnt/c/Users/juliu/repos/kmj-sniper/node_modules/puppeteer/.local-chromium/linux-901912/chrome-linux/chrome: error while loading shared libraries: libatk-1.0.so.0: cannot open shared object file: No such file or directory
What am I missing here?
The error message can either indicate that your operating system is missing the ATK library (libatk), or that this shared library is installed in a location that Puppeteer does not know about, because it is not available from the paths specified in the environment variable LD_LIBRARY_PATH, or has a different name from what is expected.
If the ATK library is missing, what platform your laptop is running will likely determine the answer. If you are running Ubuntu, for example, you could do the following, or similar:
$ sudo apt-get install libatk-bridge2.0-0
On CentOS/RHL, perhaps:
$ sudo yum install atk.x86_64
If the required package is already installed, however, check that LD_LIBRARY_PATH includes the directory where the shared library is installed, and that the filename matches that shown in the error message returned by Puppeteer.
Delete folder node_modules (don't delete the package.json and package-lock.json files) and then run npm i.
It will essentially reinstall all your dependencies.
If that doesn’t work, then try Alex's answer.
While configuring a project that uses aicxx and gitache, I get the following error:
...
[ 11%] Performing update step for 'gitache-populate'
cd /home/carlo/projects/aicxx/linuxviewer/linuxviewer-objdir/_deps/gitache-src && /usr/bin/cmake -P /home/carlo/projects/aicxx/linuxviewer/linuxviewer-objdir/_deps/gitache-subbuild/gitache-populate-prefix/tmp/gitache-populate-gitupdate.cmake
fatal: ambiguous argument 'stable': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
From https://github.com/CarloWood/gitache
bef7d0d..5c68f7b stable -> origin/stable
CMake Error at /home/carlo/projects/aicxx/linuxviewer/linuxviewer-objdir/_deps/gitache-subbuild/gitache-populate-prefix/tmp/gitache-populate-gitupdate.cmake:121 (message):
....
How can I fix this?
The reason for this error is probably that you just pulled a CMakeLists.txt change
that switched from using one gitache branch to another (from master to stable in this case).
The easiest way to recover is to entirely clean the project and configure from scratch.
For example, remove the cmake build directoy:
rm -rf /home/carlo/projects/aicxx/linuxviewer/linuxviewer-objdir
Then rerun ./autogen.sh and configure and build as usual.
Technically running autogen.sh is only necessary after running make maintainer-clean, if the project supports that (normally cmake doesn't, so it would have to be manually added by the project), but it never hurts.
I copied the commands (from these instructions: http://www.shogun-toolbox.org/install#ubuntu) into the terminal and they seem to have worked, but there is no documentation on how to make Octave find the libraries. I have tried modshogun and init_shogun but Octave cannot find them. I do have the libraries in usr/lib, and I have put that directory on PATH. I have even set usr/lib as my working directory in Octave and that did not help. As far as I have found, there is no Shogun documentation on what to do at this point.
I have also tried compiling Shogun from source, but configure couldn't find GCC. Apparently, this is a known problem with newer versions of GCC. I decided to ask for help with the former method because at least I have the libraries with that.
Edit: I am following the instructions here http://www.shogun-toolbox.org/install#manual-basics
When i do cd build and then "cmake -DINTERFACE_OCTAVE=ON" it tells me there is no cmakelists.txt. There is one in in the above folder, but when I go to that directory and do "cmake -DINTERFACE_OCTAVE=ON" again, it tells me "Shogun can only be built with GPL codes if the source files are in /home/derose/shogun/src/shogun/src/gpl. Please download or disable with LICENSE_GPL_SHOGUN=OFF."
However, when I add -LICENSE_GPL_SHOGUN=OFF as an option, i get the error "CMake Error: The source directory "/home/derose/shogun/src/shogun/-LICENSE_GPL_SHOGUN=OFF" does not exist."
You've linked to the Ubuntu install instructions. From there
These currently do contain the C++ library and Python bindings..
No word that this would include the GNU Octave binding. See below on the same page:
The native C++ interface is always included. The cmake options for building interfaces are -DINTERFACE_PYTHON=ON -DINTERFACE_R .. etc. For example, replace the cmake step above by cmake -DINTERFACE_PYTHON=ON...
So you have to grab the source and fire up cmake with something like -DINTERFACE_OCTAVE=ON
Steps to build the bleeding edge of shogun (the github repo) and the Octave interface:
git clone https://github.com/shogun-toolbox/shogun && cd shogun
git submodule update --init
mkdir build && cd build
cmake .. -DINTERFACE_OCTAVE=ON
make -j4
I installed latest Octave on Ubuntu 14.04 machine. However, when I tried to run imread command, it showed the following error message:
octave:12> imread('newfile.png')
error: imread: invalid image file: /usr/lib/x86_64-linux-gnu/octave/3.8.1/oct/x86_64-pc-linux-gnu/__magick_read__.oct: failed to load: /usr/lib/x86_64-linux-gnu/octave/3.8.1/oct/x86_64-pc-linux-gnu/__magick_read__.oct: undefined symbol: _ZN6Magick5ColorC1Ehhh
error: called from:
error: /usr/share/octave/3.8.1/m/image/private/__imread__.m at line 181, column 7
error: /usr/share/octave/3.8.1/m/image/private/imageIO.m at line 66, column 26
error: /usr/share/octave/3.8.1/m/image/imread.m at line 107, column 30
Can someone please suggest how to solve it?
Thanks!
Following these steps worked for me [Author: Christoffer Cronström (hymyly)]:
Install the dev packages needed to build octave.
sudo apt-get build-dep octave
Get the official source package. Do this in a clean directory, because it will get polluted.
cd ~/some/suitable/directory
apt-get source octave
Build it. This took roughly an hour for me.
cd octave-3.8.2
dpkg-buildpackage
Either run it from the build directory:
./run-octave
...or most preferably install it over the official octave:
cd ..
sudo dpkg --install octave_3.8.2-4_amd64.deb
From: https://bugs.launchpad.net/ubuntu/+source/octave/+bug/1372202
How did you instal Octave? The error suggests that you're missing GraphicsMagick C++ interface (package libgraphicsmagick++3) but
if you installed Octave from Ubuntu's package manager you should not have had this problem; * if you compiled it yourself, Octave should have disabled imread completely and you'd have a very different error message.
So my guess is that you build it yourself, either with:
your own build of GraphicsMagick++ which are not being loaded anymore, you may need to add their path to the dynamic linker load path (either on /etc/ld.so.conf.d./graphicsmagick or define LD_LIBRARY_PATH);
the libraries from the package manager which you have since accidentally removed (since you did not install Octave from the repositories, your package manager will not know that libgraphicsmagick++ is installed for a reason).
Either way, the solution is easy. Install Octave from Ubuntu's package manager. One of the main reasons package managers exist is to avoid this type of problems, i.e., missing dependencies.