On 5/14/2018 08:30, Michael Neumann wrote:
On Mon, May 14, 2018 at 08:24:06AM -0500, John Marino wrote:
On 5/14/2018 08:17, Michael Neumann wrote:
Hi,
While trying to port "rust" to Ravenports, I noticed that Ravenports
uses libexecinfo.so.2 (from "ravenports"), whereas the base DragonFly
system uses libexecinfo.so.1 from /usr/src. Because of that, the
bootstrapped rust compiler failed to run under Ravenports :(
My solution was to add a -fPIC to the Makefiles of /usr/src/lib/libelf
and /usr/src/lib/libexecinfo, and statically link the dependent shared
object against it.
My question is, can we ship with something like libexecinfo_pic.a?
Regards,
Michael
we could always add libexecinfo.so.2 to the dragonfly build environment.
That shouldn't disrupt anything.
libexecinfo.so.2 is already in the Ravenports build environment,
installed by some dependent port required to build rust (I think
llvm60). What is missing is libexecinfo.so.1, as the bootstrap rust
compiler needs that for execution.
I mispoke. I mean add libexecinfo.so.1 from dragonfly to the dragonfly
build environment as a system library.
