all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ben Woodcroft <b.woodcroft@uq.edu.au>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: rustc: Add LIBRARY_PATH search path.
Date: Sun, 29 Jan 2017 00:34:52 +0100	[thread overview]
Message-ID: <87poj6zrkz.fsf@gnu.org> (raw)
In-Reply-To: <b315ef00-f5bc-9fd3-36be-c57065238d69@uq.edu.au> (Ben Woodcroft's message of "Sat, 28 Jan 2017 09:35:35 +1000")

Hi Ben,

Ben Woodcroft <b.woodcroft@uq.edu.au> skribis:

> On 28/01/17 09:22, Ludovic Courtès wrote:
>> Marius Bakke <mbakke@fastmail.com> skribis:
>>
>>> Hi Ben,
>>>
>>> Ben Woodcroft <donttrustben@gmail.com> writes:
>>>
>>>> * gnu/packages/rust.scm (rustc)[native-search-paths]: 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?
>> It’s honored by GCC (not to be confused with LD_LIBRARY_PATH.)
>>
>> Does rustc invoke gcc, or does it just happen to use a same-named
>> variable?
> It uses gcc.

In that case, you can copy GCC’s search paths wholesale:

  ;; rustc invokes gcc, so we need to set its search paths accordingly.
  (native-search-paths (package-native-search-paths gcc))

HTH!

Ludo’.

  reply	other threads:[~2017-01-28 23:35 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 [this message]
2017-01-27 23:26     ` Ben Woodcroft
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=87poj6zrkz.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=b.woodcroft@uq.edu.au \
    --cc=guix-devel@gnu.org \
    /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.