Github messages for voidlinux
 help / color / mirror / Atom feed
From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Cross building packages with `libgomp-devel` in makedepends breaks the masterdir
Date: Tue, 28 Dec 2021 04:54:22 +0100	[thread overview]
Message-ID: <20211228035422.n2w6bpdAL4tXr98ZJgLg16Tlwqmtvydu_qsSoVqOHRc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31055@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 706 bytes --]

New comment by tornaria on void-packages repository

https://github.com/void-linux/void-packages/issues/31055#issuecomment-1001855016

Comment:
What would happen if we add `libgomp-devel` as a dependency to `cross-vpkg-dummy` (and maybe to `base-chroot`, while we are at it).

In this way, `libgomp-devel` is always available, just like gcc or glibc.  Are there any downsides of that?

In #34469 it seems I can "fix" the issue when building `siril` by just adding `libgomp-devel` to `makedepends` (unconditionally) which I think would be implicit in what I suggested above.

What I don't understand is why `siril` needs `libgomp.spec` when building cross but it doesn't need it when building native.

  reply	other threads:[~2021-12-28  3:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21 18:36 [ISSUE] " ericonr
2021-12-28  3:54 ` tornaria [this message]
2021-12-28  3:58 ` tornaria
2022-01-04  8:18 ` ericonr
2022-01-10 14:38 ` tornaria
2022-01-13 19:37 ` Chocimier
2022-05-20  2:12 ` github-actions
2024-02-05 10:43 ` oreo639
2024-02-05 10:43 ` oreo639

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=20211228035422.n2w6bpdAL4tXr98ZJgLg16Tlwqmtvydu_qsSoVqOHRc@z \
    --to=tornaria@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).