On Thu, 2 Jan 2020, wf...@niif.hu wrote:
If Libtool were to depend on non-portable features, [...] then it
could not longer be described as a portability tool.
In my understanding, Libtool is a portability shim, providing a regular
interface for developers across systems with wildly varying
Bob Friesenhahn writes:
> On Thu, 2 Jan 2020, wf...@niif.hu wrote:
>
True, but man ld states in the -rpath-link option description that the
directories specified by -rpath options are used with a very high
priority for locating required shared libraries.
>>>
>>> This is
On Thu, 2 Jan 2020, wf...@niif.hu wrote:
True, but man ld states in the -rpath-link option description that the
directories specified by -rpath options are used with a very high
priority for locating required shared libraries.
This is interesting but I am not seeing any use of -rpath-link in
On Thu, 2 Jan 2020, wf...@niif.hu wrote:
In this case libtool is a slave of Automake and Automake is
controlling the build and installation order. This means that it
should be expected behavior. Installation is serialized and thus
order matters.
But in case of a dependency cycle there's no
