Arch Linux

krork

Member

Registered: 2013-06-08

Posts: 29

letting gcc link against newer libraries, good or bad?

Hi,
I basically solved this issue I had, and I did some research, but I would love to hear some general thoughts on this, as I'm rather inexperienced with this topic.

I'm writing small programs in C++ with the freeling linguistic library. When I compile, libfreeling.so wants gcc to link against several old libraries of the form libboost_***_.so.1.57.0, but of which I have the versions 1.58.0.

Now, isn't one of the points of having dynamic libraries to not have this issue, especially since there are some without the version number present, which I think might point to the newest versions present?

So why isn't libfreeling.so just asking gcc to link to the newest versions?

I solved this for the moment by creating symlinks named **1.57.0 to the newer versions, but I feel this is a bad solution.

What is the best approach when one has libraries asking for older versions of other libraries?

I looked at the libfreeling headers, also at the libboost headers, and the version numbers there are correct. Is this a bug in one of the libraries, or a typical issue?

Greetings!

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,359

Re: letting gcc link against newer libraries, good or bad?

If libfreeling is built against the old version of boost, rebuild it.

krork

Member

Registered: 2013-06-08

Posts: 29

Re: letting gcc link against newer libraries, good or bad?

Sounded smart, and it was. It worked Thanks!