I think you want to things:
1. That the libraries that Julia requires are automatically resolved
to those that were available at build time. The static map you
propose is the right thing for that, as Andreas notes.
2. That any other libraries users may want to load is search for us
Andreas Enge writes:
> On Fri, Mar 06, 2015 at 04:48:59PM +0100, Ricardo Wurmus wrote:
>> Julia's bindings to these libraries use the ccall mechanism; ccall
>> builds a map from library names to paths by parsing the output of
>> "ldconfig -p" at runtime. I worked around this problem by patching
On Fri, Mar 06, 2015 at 04:48:59PM +0100, Ricardo Wurmus wrote:
> Julia's bindings to these libraries use the ccall mechanism; ccall
> builds a map from library names to paths by parsing the output of
> "ldconfig -p" at runtime. I worked around this problem by patching the
> sources to include a s
Hi Guix,
I'm currently packaging up Julia, a programming language for technical
computing. When I configure the build process such that system
libraries are used instead of the bundled copies I run into a problem.
Julia's bindings to these libraries use the ccall mechanism; ccall
builds a map fr
