From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ci skip] tiff: update to 4.5.0.
Date: Sun, 16 Apr 2023 22:03:37 +0200 [thread overview]
Message-ID: <20230416200337.vb_gbMlGq0dafoWDZuAAs5b5a1wf-PlXEkXHTCyBlFY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43455@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/43455#issuecomment-1510473891
Comment:
I've built everything natively (`x86_64*` and `i686`) with a couple of workaround but noticed some issues on cross that are probably unrelated to this PR. Builds will resume for the remaining architectures this evening. When I have a complete set of builds, I'll push a few fixups here.
The cross issue is that one package seems to pull in `libgomp-devel`, which conflicts with `libgomp` bits in `cross-*-libc` packages. When that package finishes building, `libgomp-devel` gets removed and takes some files that are still expected to be there as part of the `cross-*-libc` packages. When `gthumb` tries to build, it sees the `libgomp` library but not `libgomp.spec` because it doesn't declare a `libgomp-devel` dependency. For now, just adding `libgomp-devel` to `makedepends` should be sufficient, but long terms we should decide how to completely remove the conflicts.
next prev parent reply other threads:[~2023-04-16 20:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 21:18 [PR PATCH] " mhmdanas
2023-04-14 21:18 ` [PR PATCH] [Updated] [ci skip] " mhmdanas
2023-04-16 20:03 ` ahesford [this message]
2023-04-17 13:37 ` ahesford
2023-04-17 13:39 ` ahesford
2023-04-17 13:42 ` ahesford
2023-04-17 15:10 ` [PR PATCH] [Updated] " ahesford
2023-04-17 16:53 ` mhmdanas
2023-04-17 17:12 ` [PR PATCH] [Merged]: " ahesford
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=20230416200337.vb_gbMlGq0dafoWDZuAAs5b5a1wf-PlXEkXHTCyBlFY@z \
--to=ahesford@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).