search

arvidn / libtorrent

an efficient feature complete C++ bittorrent implementation
http://libtorrent.org
Other
5.26k stars 996 forks source link

"make install" is made but no pkg-config information found #2265

Closed lovewangbo closed 4 years ago

lovewangbo commented 7 years ago

Hi, I have compiled and installed libtorrent many times succesfully before on some servers with Ubuntu 16.04 LTs. But this time it fails that no pkg-config information found after installing. The commands I used are listed below. Normally, the following pkg-config command shows the libtorrent installed. $ pkg-config --list-all | grep libtorrent libtorrent-rasterbar libtorrent-rasterbar - Bittorrent library.

libtorrent version (or branch): RC_1_0;

platform/architecture: Ubuntu 16.04 LTS

compiler and compiler version:

please describe what symptom you see, what you would expect to see instead and how to reproduce it.

   29  git clone https://github.com/arvidn/libtorrent.git
   30  cd libtorrent/
   31  git checkout RC_1_0;
   32  ./autotool.sh;
   33  ./configure --disable-debug --enable-encryption --prefix=/usr/libtorrent --with-
libgeoip=system

The result ends with Type 'make' to compile libtorrent-rasterbar 1.0.11 or type 'make V=1' for verbose compiling and then 'make install' to install it into /usr

  34  make clean && make -j4

The result ends with make[1]: Leaving directory '/home/yellow/ipv6-dhclient-script/tmp/libtorrent/src' Making all in examples make[1]: Entering directory '/home/yellow/ipv6-dhclient-script/tmp/libtorrent/examples' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/yellow/ipv6-dhclient-script/tmp/libtorrent/examples' Making all in test make[1]: Entering directory '/home/yellow/ipv6-dhclient-script/tmp/libtorrent/test' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/yellow/ipv6-dhclient-script/tmp/libtorrent/test' Making all in bindings make[1]: Entering directory '/home/yellow/ipv6-dhclient-script/tmp/libtorrent/bindings' Making all in python make[2]: Entering directory '/home/yellow/ipv6-dhclient-script/tmp/libtorrent/bindings/python' make[2]: Nothing to be done for 'all'. make[2]: Leaving directory '/home/yellow/ipv6-dhclient-script/tmp/libtorrent/bindings/python' make[2]: Entering directory '/home/yellow/ipv6-dhclient-script/tmp/libtorrent/bindings' make[2]: Nothing to be done for 'all-am'. make[2]: Leaving directory '/home/yellow/ipv6-dhclient-script/tmp/libtorrent/bindings' make[1]: Leaving directory '/home/yellow/ipv6-dhclient-script/tmp/libtorrent/bindings' Making all in tools make[1]: Entering directory '/home/yellow/ipv6-dhclient-script/tmp/libtorrent/tools' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/yellow/ipv6-dhclient-script/tmp/libtorrent/tools' make[1]: Entering directory '/home/yellow/ipv6-dhclient-script/tmp/libtorrent' make[1]: Nothing to be done for 'all-am'. make[1]: Leaving directory '/home/yellow/ipv6-dhclient-script/tmp/libtorrent'

   35  make install

The result ends with: Libraries have been installed in: /usr/libtorrent/lib

If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the '-LLIBDIR' flag during linking and do at least one of the following:

See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages.

make[2]: Nothing to be done for 'install-data-am'. make[2]: Leaving directory '/home/yellow/tmp/libtorrent/src' make[1]: Leaving directory '/home/yellow/tmp/libtorrent/src' Making install in examples make[1]: Entering directory '/home/yellow/tmp/libtorrent/examples' make[2]: Entering directory '/home/yellow/tmp/libtorrent/examples' make[2]: Nothing to be done for 'install-data-am'. make[2]: Leaving directory '/home/yellow/tmp/libtorrent/examples' make[1]: Leaving directory '/home/yellow/tmp/libtorrent/examples' Making install in test make[1]: Entering directory '/home/yellow/tmp/libtorrent/test' make[2]: Entering directory '/home/yellow/tmp/libtorrent/test' make[2]: Nothing to be done for 'install-exec-am'. make[2]: Nothing to be done for 'install-data-am'. make[2]: Leaving directory '/home/yellow/tmp/libtorrent/test' make[1]: Leaving directory '/home/yellow/tmp/libtorrent/test' Making install in bindings make[1]: Entering directory '/home/yellow/tmp/libtorrent/bindings' Making install in python make[2]: Entering directory '/home/yellow/tmp/libtorrent/bindings/python' make[3]: Entering directory '/home/yellow/tmp/libtorrent/bindings/python' make[3]: Nothing to be done for 'install-exec-am'. make[3]: Nothing to be done for 'install-data-am'. make[3]: Leaving directory '/home/yellow/tmp/libtorrent/bindings/python' make[2]: Leaving directory '/home/yellow/tmp/libtorrent/bindings/python' make[2]: Entering directory '/home/yellow/tmp/libtorrent/bindings' make[3]: Entering directory '/home/yellow/tmp/libtorrent/bindings' make[3]: Nothing to be done for 'install-exec-am'. make[3]: Nothing to be done for 'install-data-am'. make[3]: Leaving directory '/home/yellow/tmp/libtorrent/bindings' make[2]: Leaving directory '/home/yellow/tmp/libtorrent/bindings' make[1]: Leaving directory '/home/yellow/tmp/libtorrent/bindings' Making install in tools make[1]: Entering directory '/home/yellow/tmp/libtorrent/tools' make[2]: Entering directory '/home/yellow/tmp/libtorrent/tools' make[2]: Nothing to be done for 'install-data-am'. make[2]: Leaving directory '/home/yellow/tmp/libtorrent/tools' make[1]: Leaving directory '/home/yellow/tmp/libtorrent/tools' make[1]: Entering directory '/home/yellow/tmp/libtorrent' make[2]: Entering directory '/home/yellow/tmp/libtorrent' make[2]: Nothing to be done for 'install-exec-am'. /bin/mkdir -p '/usr/libtorrent/lib/pkgconfig' /usr/bin/install -c -m 644 libtorrent-rasterbar.pc '/usr/libtorrent/lib/pkgconfig' make[2]: Leaving directory '/home/yellow/tmp/libtorrent' make[1]: Leaving directory '/home/yellow/tmp/libtorrent'

   36  pkg-config --list-all | grep libtorrent

no result found

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.