From: Fade-ing <Fade-ing@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mesa: update to version 23.1.4.
Date: Fri, 11 Aug 2023 13:22:35 +0200 [thread overview]
Message-ID: <20230811112235.EhSxMesKg7-21yCk09AJLeuc2SFawTYHS6nagJJbm2w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45177@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
New comment by Fade-ing on void-packages repository
https://github.com/void-linux/void-packages/pull/45177#issuecomment-1670756138
Comment:
> Not shure how critical these warnings are but seeing
>
> ```
> Run-time dependency libunwind found: NO (tried pkgconfig and cmake)
> WARNING: OpenMP found but omp.h missing.
> Run-time dependency OpenMP found: NO (tried system)
> ```
>
> adding libunwind-devel and libgomp-devel to makedepends resolves the configure warnings
>
> Edit: 23.1.5 tests ok (x86_64-libc/radeonsi rx570)
Nice catch! This might explains the issue that wine complains about missing libunwind.so.1, which i resolved by installing libunwind package separately
Gonna go rebuild it then
EDIT : Unfortunately it doesn't seems to be related as it still asks for libunwind.so.1, so nevermind
next prev parent reply other threads:[~2023-08-11 11:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 17:33 [PR PATCH] " SpidFightFR
2023-07-23 7:44 ` Fade-ing
2023-07-23 20:30 ` mhmdanas
2023-08-03 23:20 ` HadetTheUndying
2023-08-04 10:23 ` SpidFightFR
2023-08-04 10:53 ` SpidFightFR
2023-08-04 12:36 ` Fade-ing
2023-08-07 10:08 ` biopsin
2023-08-07 10:20 ` biopsin
2023-08-08 18:21 ` HadetTheUndying
2023-08-09 6:37 ` Fade-ing
2023-08-11 11:22 ` Fade-ing
2023-08-11 11:22 ` Fade-ing [this message]
2023-09-08 17:28 ` [PR PATCH] [Closed]: " SpidFightFR
2023-09-08 17:28 ` SpidFightFR
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=20230811112235.EhSxMesKg7-21yCk09AJLeuc2SFawTYHS6nagJJbm2w@z \
--to=fade-ing@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).