Re: [PATCH] gnu: rustc: Add LIBRARY_PATH search path.

[Ben Woodcroft]

On 29/01/17 11:57, Chris Marusich wrote:
> Ben Woodcroft <address@hidden> writes:
>
> > I didn't have any problem compiling and linking pure rust programs -
> > that commit fixed that issue, but when trying to link rust programs to
> > non-rust libraries such as zlib the linker did not look in the lib of
> > the profile (unless gcc was also in the profile, I guess). I was
> > specifically looking to include rust-htslib in a crate I am building,
> > to be concrete.
> I'm not too familiar with rust, but isn't the linker supposed to look in
> the store, not in your user profiler?  My understanding is that we
> usually don't want to compose components dynamically like that, since it
> causes problems (e.g., incomplete deployment due to "missing" stuff in
> the user's profile).

I'm not too familiar either, but I think of it like this.

Imagine we had a hypothetical rust-no-gcc-build-system for building rust 
packages which did not inherit from gnu-build-system so did not have gcc 
as an input. Then, building rust packages which linked to libraries such 
as zlib would not work, even if zlib were specified as an input, because 
LIBRARY_PATH is not set. In that case, the compilation/linking with rust 
is much like compilation/linking with gcc - it requires LIBRARY_PATH.

Does that make sense?
Thanks, ben.