public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: glibc emerge error
Date: Sat, 13 Jan 2018 00:14:44 +0200	[thread overview]
Message-ID: <p3bbs8$l6d$1@blaine.gmane.org> (raw)
In-Reply-To: <cd27ac41-9add-dc3f-6c8c-60a150059490@charter.net>

On 12/01/18 18:31, Corbin Bird wrote:
> On 01/11/2018 08:29 AM, Nikos Chantziaras wrote:
>> On 11/01/18 15:28, Corbin Bird wrote:
>>>> Why are you setting LD_LIBRARY_PATH system-wide to begin with? Don't
>>>> do that.
>>>
>>> Unfortunately, I had to ( and didn't realize the implications. )
>>> In .bashrc :
>>>> export LD_LIBRARY_PATH=$VULKAN_SDK/lib:$LD_LIBRARY_PATH
>>>
>>> Required by the Vulkan Loader ( Mesa && Chromium ).
>>
>> I think this is what the /etc/ld.so.conf.d/ directory is there for.
>> Have you tried something like this instead:
>>
>>    echo "$VULKAN_SDK/lib" > /etc/ld.so.conf.d/vulkan-loader.conf
>>    env-update
>>
> 
> Will try this method and see what happens.
> 
> Checked a file already there. In the "05gcc-x86_64-pc-linux-gnu.conf"
> there were no $PATH variables.
> Put explicit paths in instead.
> 
> This will be interesting.

Yes, you do add explicit paths in it. This:

   echo "$VULKAN_SDK/lib" > /etc/ld.so.conf.d/vulkan-loader.conf

will write an explicit path (the variable is expanded by the shell.)



  reply	other threads:[~2018-01-12 22:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 17:55 [gentoo-user] glibc emerge error Corbin Bird
2018-01-10 18:22 ` Matthias Hanft
2018-01-11 13:24   ` Corbin Bird
2018-01-10 19:53 ` [gentoo-user] " Nikos Chantziaras
2018-01-11 13:28   ` Corbin Bird
2018-01-11 14:29     ` Nikos Chantziaras
2018-01-12 16:31       ` Corbin Bird
2018-01-12 22:14         ` Nikos Chantziaras [this message]
2018-01-13  0:11           ` Corbin Bird
2018-01-11 17:01     ` Ian Zimmerman

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='p3bbs8$l6d$1@blaine.gmane.org' \
    --to=realnc@gmail.com \
    --cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox