I am trying to build openWRT on CentOS7(64bits) by using command like make, but its giving error like
svn: /home/shwetha/openwrt/trunk/staging_dir/host/lib/liblzma.so.5: no version information available (required by /lib64/libselinux.so.1)
I tried changing some configurations but its giving same error:
/home/shwetha/openwrt/trunk/staging_dir/host/lib/liblzma.so.5: no version information available (required by /lib64/libselinux.so.1)
/lib64/libselinux.so.1: undefined reference to 'lzma_code#XZ_5.0'
/lib64/libselinux.so.1: undefined reference to 'lzma_stream_decoder#XZ_5.0'
/lib64/libselinux.so.1: undefined reference to 'lzma_end#XZ_5.0'
This has been fixed about two week ago in OpenWrt trunk and CC, see this:
https://dev.openwrt.org/changeset/46603
You have to update to a more recent trunk or CC version, or manually update xz in the tools directory to version 5.2.1, for example by cherry-picking the commit I mentioned.
Related
I tried to augment my rust project with a dependency on jni="0.12.3" and my next cargo build failed with the following error:
error: unable to get packages from source
Caused by:
failed to parse manifest at `/home/thoth/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.32/Cargo.toml`
Caused by:
editions are unstable
Caused by:
feature `edition` is required
consider adding `cargo-features = ["edition"]` to the manifest
I'm running cargo built from gentoo's dev-util/cargo-0.30.0 ebuild.
Since rust is a quickly-evolving language, the latest crates seem to use new features that my older version of cargo did not support. And since rust/cargo did not have something like portage's EAPI marker, the old cargo did not have a way to figure that out, so the error message was a bit indirect.
I have a theory that the Cargo.lock could be tweaked to use an older version of the backtrace crate, but I was not able to figure out a procedure to do this.
Upgrading to the rust-1.34.2 ebuild, and (don't forget this step:) then using eselect rust set 1 activated the new version of cargo, and it was able to build the package without malfunctioning.
Trying to install ImageMagick 7.0.1-3 on Redhat 6.7 :
$sudo rpm -ivh ImageMagick-7.0.1-3.x86_64.rpm
error: Failed dependencies:
ImageMagick-libs = 7.0.1-3 is needed by ImageMagick-7.0.1-3.x86_64
libMagickCore-7.Q16HDRI.so.0()(64bit) is needed by ImageMagick-7.0.1-3.x86_64
libMagickWand-7.Q16HDRI.so.0()(64bit) is needed by ImageMagick-7.0.1-3.x86_64
libMagickWand-7.Q16HDRI.so.0(VERS_1.0)(64bit) is needed by ImageMagick-7.0.1-3.x86_64
liblzma.so.5()(64bit) is needed by ImageMagick-7.0.1-3.x86_64
i was able to install ImageMagick using the tar.gz distribution for the same release.
Now since i would like to have a binary, so i can install it on production servers, but when trying to create an rpm , i get:
rpmbuild -ba ImageMagick.spec
error: Failed build dependencies:
jbigkit-devel is needed by ImageMagick-7.0.1-3.x86_64
Where to get jbgkit-devel ?? and the rest of the dependencies ?
Is there an alternate way to install ImageMagick ?
jbigkit does not mention jbigkit-devel
Also, using the ImageMagick.spec provided in the tar.gz distribution i tried to make an rpm, but i get error:
# rpmbuild -ba ImageMagick.spec
error: Failed build dependencies:
jbigkit-devel is needed by ImageMagick-7.0.1-3.x86_64
Which is back to square one, i tried to copy jbigkit-2.1.tar.gz in SOURCES, but i get the same error for jbigkit-devel is needed
If you go to the ImageMagick binary releases,
the second link is the libs. Do that first and then the first link.
It worked for me and I got here looking to solve the error you entered.
I am trying to install clang from source following the instructions as given in http://clang.llvm.org/get_started.html ( Steps 1-4 and 7) in Ubuntu 14.04
Inside the build directory , I ran make which succeeded. I wasn't sure what to do after that , so I ran make install inside the build directory, following which I got this cmake error:
There is no executable named clang in /build/bin folder anyway, but I can find others like clang-check, clang-query, etc. What's going wrong?
PS: My main requirment is to experiment with alpha security checkers of clang analyzer and also write my own checker later.
I am trying to run Latex on Solaris 10/x86. I have successfully installed the tetex3.0 from sunfree. When I run Latex I get the following error:
ld.so.1: pdfetex: fatal: libstdc++.so.5: open failed: No such file or directory
and ldd pdfetex shows:
libstdc++.so.5 => (file not found)
I have the latest version (libstdc++.so.6) and tried to link libstdc++.so.5 to .6 however, the libstdc++.so.5 is not even installed in my machine. Is there a way to change the dependency from version 5 to 6? Or any other way around this problem? Thanks.
I think you missed their note stating that
[..] that you have the /usr/local/lib/libstdc++.so.5 and /usr/local/lib/libgcc_s.so.1 related files either from the gcc-3.3.2 or libgcc-3.3 or higher packages
Did you install [lib]gcc as well?
I'm trying to build Firefox from source and I'm getting hung up on some of the requirements.
I'm trying to build libIDL, which requires glib. I got glib built and installed to /usr/local, but when I try and configure libIDL, I get a failure at:
checking for LIBIDL... configure: error: Package requirements (glib-2.0 >= 2.4.0) were not met:
No package 'glib-2.0' found
I used the very latest version of glib that I can find, ftp://ftp.gtk.org/pub/glib/2.20/glib-2.20.3.tar.gz
However, I've also been searching around and am seeing references to libglib-2.0 such as at http://packages.debian.org/search?keywords=libglib2.0-dev
Are there 2 divergent branches of Glib, like a v1 and v2?
You need to install glib-devel in order to have the glib headers exist on your system. Without the headers, autoconf will mark the library as missing.
You installed glib from source which should have worked. The actual problem was most likely with the paths you chose to install into. The autoconf script may not be looking for glib where you installed it, or it may be looking into another directory first and finding an old version.