New answers tagged libraries
If you want to compile it then you need glib2-devel package.
If you need it for a build, then you need the #include headers as well. These, and the pkgconfig files, are not in the normal packages because they don't serve any purpose outside of compiling. Instead, they are included in seperate -dev packages which you can install if you want to build something which must be compiled against whatever library. It looks ...
You don't need libdlo for this. libdlo is experimental and for demonstration only. There are some efforts to support displaylink chips directly in the kernel. According to my research (I spent about 2 weeks on this problem), desktop expansion has not yet been achieved. However, you can run a separate X11 server on the display, supported natively by the ...
So, the problem was caused from me having compiled another version of glib in /usr/local/. Because I did not remember the exact version I had compiled, I went to /usr/local/lib/pkgconfig/ and looked at the libglib2.0-0.pc file, which reported the 2.16 version. Because I did not have the source files, I re-downloaded them from ...
NOTE: I'm going to assume that your machine has a memory mapping unit (MMU). There is a Linux version (µClinux) that doesn't require an MMU, and this answer doesn't apply there. What is an MMU? It's hardware—part of the processor and/or memory controller. Understanding shared library linking doesn't require you to understand exactly how an MMU works, just ...
There is a Synergy bug filed about this issue. http://synergy-foss.org/spit/issues/details/3919/#
If you run rpm -q --provides libcurl you can see what your libcurl package provides. If you run rpm -qp --requires synergy-1.4.16-r1969-Linux-x86_64.rpm you can see what your synergy rpm requires. The problem appears to be synergy was built against a libcurl package that provides libcurl.so.4(CURL_OPENSSL_3)(64bit) which the normal libcurl that comes with ...
Oh no, some files of curl are in openssl or gnutls package, those doens't related to curl package. please innstall openssl or gnutls.
Assuming the package has already been installed you can see the contents of it using dpkg -L, for list. Example $ dpkg -L lzma-dev /. /usr /usr/include /usr/include/lzma /usr/include/lzma/LzHash.h /usr/include/lzma/Types.h /usr/include/lzma/LzmaEnc.h /usr/include/lzma/LzFind.c /usr/include/lzma/LzmaEnc.c /usr/include/lzma/LzFind.h ...
dpkg -L lzma-dev list all the files installed with apt-get for lzma-dev
It will depend on where the file is, in my case it works like this: :~$ locate gcc_s /lib/x86_64-linux-gnu/libgcc_s.so.1 /usr/lib/gcc/x86_64-linux-gnu/4.6/libgcc_s.so /usr/lib/gcc/x86_64-linux-gnu/4.7/libgcc_s.so And you have to make sure that path is present in one of the ld.so.conf files like: :~$ cat /etc/ld.so.conf.d/x86_64-linux-gnu.conf # Multiarch ...
Assuming you are installing mpich 3 from source, you need to provide --enable-shared option while configuring in order to create an so, which is shared library. See section 2.6 of the guide you linked. An example from my config.log: ./configure --prefix=/home/kcm92/mpich3-install --enable-shared make && make install
Top 50 recent answers are included