all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: Marius Bakke <mbakke@fastmail.com>,
	Ben Woodcroft <donttrustben@gmail.com>,
	guix-devel@gnu.org
Subject: Re: [PATCH] gnu: rustc: Add LIBRARY_PATH search path.
Date: Sat, 28 Jan 2017 09:26:44 +1000	[thread overview]
Message-ID: <37744b8c-255c-28d0-04c1-9385f384d473@uq.edu.au> (raw)
In-Reply-To: <87inp01cfi.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>

Hi Marius,


On 28/01/17 06:21, Marius Bakke wrote:
> Hi Ben,
>
> Ben Woodcroft <donttrustben@gmail.com> writes:
>
>> * gnu/packages/rust.scm (rustc)[native-search-pat hs]: New field.
> [...]
>
>> +    (native-search-paths
>> +     (list (search-path-specification
>> +            (variable "LIBRARY_PATH")
>> +            (files '("lib" "lib64")))))
> This seems odd. This search path is for glibc, no?
>
> Is the problem this addresses not already fixed by
> 5d18d776d269ab9a6c44e049936389df3454ba30?

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.

Thanks, ben.

  parent reply	other threads:[~2017-01-27 23:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-27 12:02 [PATCH] gnu: rustc: Add LIBRARY_PATH search path Ben Woodcroft
2017-01-27 12:02 ` Ben Woodcroft
2017-01-27 20:21   ` Marius Bakke
2017-01-27 23:22     ` Ludovic Courtès
2017-01-27 23:35       ` Ben Woodcroft
2017-01-28 23:34         ` Ludovic Courtès
2017-01-27 23:26     ` Ben Woodcroft [this message]
2017-01-29  1:57       ` Chris Marusich
2017-01-29 11:34         ` Ben Woodcroft

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=37744b8c-255c-28d0-04c1-9385f384d473@uq.edu.au \
    --to=b.woodcroft@uq.edu.au \
    --cc=donttrustben@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.