On Thu, 2011-12-15 at 09:24 +0100, Ralf Corsepius wrote:
On 12/15/2011 09:06 AM, Jonathan Ryshpan wrote:
A build is failing with the error cannot findlibrary for libraries
that are, in fact present on the system.
I made a very simple test bed, consisting of the empty file conftest.c,
On Sun, Jan 22, 2012 at 23:48, Jonathan Ryshpan jonr...@pacbell.net wrote:
Is there any convenient way to
install all the *-devel packages matching libraries on the system, or do
I just have to install them one by one as links fail?
If you are simply building a newer version of a package
A build is failing with the error cannot find library for libraries
that are, in fact present on the system.
I made a very simple test bed, consisting of the empty file conftest.c,
which I attempt to compile and link with various libraries. All the
libraries are in /usr/lib64. Sometimes the
On 12/15/2011 09:06 AM, Jonathan Ryshpan wrote:
A build is failing with the error cannot findlibrary for libraries
that are, in fact present on the system.
I made a very simple test bed, consisting of the empty file conftest.c,
which I attempt to compile and link with various libraries. All
A build is failing with the error cannot find library for libraries
that are, in fact present on the system.
I made a very simple test bed, consisting of the empty file conftest.c,
which I attempt to compile and link with various libraries. All the
libraries are in /usr/lib64. Sometimes the
On Thu, 15 Dec 2011 00:31:26 -0800, JR (Jonathan) wrote:
A build is failing with the error cannot find library for libraries
that are, in fact present on the system.
They aren't. The test bed is invalid. Linker option -lwhatever needs
expects to find a libwhatever.so file or symlink. Those
