Tag Info

New answers tagged

2

Compilers can be configured to generate extra information with the executable and/or libraries that aid debugging. With this extra information, your debugger can show the original source code and variable names amongst other things. Unfortunately, this debugging information take up a lot of space on the system. Considering that they are hardly ever used ...


1

Stuff in /usr/local usually supersedes stuff in /usr, so I'm a bit confused as to why you would install libraries there to have a "a nice custom distro", but then not want to compile against them. Those are the libraries the system will use actually use. Anyway, man pkg-config claims the base search path: is libdir/pkgconfig:datadir/pkgconfig where ...


2

It seems I haven't removed the older version of GDAL. How should I do that? Attempting make uninstall is a reasonable option, if you have kept the sources, which is good practice if you are doing local installs. A simple alternative is to remove all files relating to this library, both old and new and then reinstall the new one. However, I have to ...


2

The file libgdal.a will only be used when you link ogrinfo against it without the use of shared libraries. If ogrinfo was linked that way (not using shared libraries), you would not get the error, as the library (version 1.11) would be part of the executable. What you should try is run sudo ldconfig after compiling and installing the new version of gdal, ...


0

You could simply copy the headers provided in your /usr/include path. No? Obviously don't forget to link the library when you compile your sources. I tried and it works like a charm!


1

In general, ./configure && make && make install without any parameters sticks everything under /usr/local, which would place foo.pc in /usr/local/lib/pkgconfig/foo.pc To make use of this, you'd need to do basically PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:${PKG_CONFIG_PATH} pkg-config --cflags foo, or, compile in this manner: ./configure ...


2

You need to verify $PATH and $LD_LIBRARY_PATH environment variables. make sure they are point to correct version of ffmpeg and does not include older version if LD_LIBRARY_PATH is not already setup then try this : LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib ffmpeg


2

You can refer to the official page: https://www.kernel.org/pub/linux/libs/uclibc/Glibc_vs_uClibc_Differences.txt


0

lib fun are compiler supported while syscall are OS supported Libcall are specific while syscall are generic, like getc a lib fun can access only one char at a time not string or word by word, but open a syscall can used to open text file ,binary file and many more types of files.


2

What exact command do you use to build executable of your program? You need to tell g++ about additional directories with project-specific headers and libraries. If you have libcurlcpp.a copied into $proj_home/lib and libcurlcpp.h copied into $proj_home/hdr this will be something like: $ g++ your_program.cpp -Ihdr -Llib -lcurlcpp -static -o ...



Top 50 recent answers are included