From: Norman-Normandy <Norman-Normandy@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: vulkan-loader missing symbolic links inside /usr/lib
Date: Thu, 30 May 2024 16:57:43 +0200 [thread overview]
Message-ID: <20240530145743.AC8512911E@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50607@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
New comment by Norman-Normandy on void-packages repository
https://github.com/void-linux/void-packages/issues/50607#issuecomment-2139814421
Comment:
No pre-built binaries using the vulkan loader break. But my existing build pipelines for building them did because the gnu linker complains it can't find -lvulkan. Which was originally inside as /usr/lib/libvulkan.so and now suddenly it isn't, but instead part of the vulkan-loader-devel package. A package that I never installed before.
I understand development packages usually contain files for building projects where as the non-devel packages are for running existing binaries.
But was this **change** to remove "libvulkan.so" from the normal "vulkan-loader" into "vulkan-loader-devel" intentional?
Other distros I've used don't separate the library symbolic links. Including FreeBSD.
next prev parent reply other threads:[~2024-05-30 14:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 11:47 [ISSUE] " Norman-Normandy
2024-05-30 11:56 ` Norman-Normandy
2024-05-30 13:41 ` ahesford
2024-05-30 14:57 ` Norman-Normandy [this message]
2024-05-30 15:02 ` [ISSUE] [CLOSED] " ahesford
2024-05-30 15:02 ` ahesford
2024-05-30 17:03 ` classabbyamp
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=20240530145743.AC8512911E@inbox.vuxu.org \
--to=norman-normandy@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).