You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Hans van den Bogert <ha...@gmail.com> on 2015/12/14 17:13:08 UTC
Option to not include RPATHs in executables.
Hi,
My environment:
- GCC 4.9 is installed in a non-standard way. (can’t change this) and uses the LD_LIBRARY_PATH to run/compile correctly
Mesos executables have the /usr/lib64 path in their RPATHs.
The problem is that the default libstdc++ (in /usr/lib64) is now used instead of the libstdc++ with which Mesos was compiled. Multiple errors happen, like:
/somepath/sbin/mesos-slave: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.14' not found (required by /somepath/sbin/mesos-slave)
Does Mesos have an option during configure to disable RPATHs attached to executables? In my environment RPATHs are not helping and I’ve already seen that removing the RPATHs (using chrpath) after installing remedies my situation.
Or,
is there a way to change the RPATH settings such that the LD_LIBRARY_PATH paths are incorporated inside the RPATHs of executables, in front of the default /usr/lib64/ — frankly, why is libtool adding this standard location anyway?
Regards,
Hans
Re: Option to not include RPATHs in executables.
Posted by James DeFelice <ja...@gmail.com>.
You might get a faster response by emailing mesos dev list.
On Mon, Dec 14, 2015 at 11:13 AM, Hans van den Bogert <ha...@gmail.com>
wrote:
> Hi,
>
> My environment:
> - GCC 4.9 is installed in a non-standard way. (can’t change this) and uses
> the LD_LIBRARY_PATH to run/compile correctly
>
> Mesos executables have the /usr/lib64 path in their RPATHs.
> The problem is that the default libstdc++ (in /usr/lib64) is now used
> instead of the libstdc++ with which Mesos was compiled. Multiple errors
> happen, like:
> /somepath/sbin/mesos-slave: /usr/lib64/libstdc++.so.6: version
> `GLIBCXX_3.4.14' not found (required by /somepath/sbin/mesos-slave)
>
> Does Mesos have an option during configure to disable RPATHs attached to
> executables? In my environment RPATHs are not helping and I’ve already
> seen that removing the RPATHs (using chrpath) after installing remedies my
> situation.
> Or,
> is there a way to change the RPATH settings such that the LD_LIBRARY_PATH
> paths are incorporated inside the RPATHs of executables, in front of the
> default /usr/lib64/ — frankly, why is libtool adding this standard location
> anyway?
>
> Regards,
>
> Hans
>
>
>
>
--
James DeFelice
585.241.9488 (voice)
650.649.6071 (fax)