Github messages for voidlinux
 help / color / mirror / Atom feed
From: SpidFightFR <SpidFightFR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Building mesa on arm and aarch64 platforms fail since wrappers/cross-cc modifications
Date: Mon, 16 Oct 2023 14:21:51 +0200	[thread overview]
Message-ID: <20231016122151.8Q_SKX12LACUFYd7ctm00sE5iBv8-QKwpVEblE76Cqo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46674@inbox.vuxu.org>

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

New comment by SpidFightFR on void-packages repository

https://github.com/void-linux/void-packages/issues/46674#issuecomment-1764357981

Comment:
> This failure was to be expected. #46635 only allows to remove some of the sed in the `post_configure` of mesa, the `regenerate` hack I suggested and sed of linking arguments are still needed.

I will try to re-add  your hack, but atm i have a ton of work on my personal side, so i want to apologize for keeping you waiting

  parent reply	other threads:[~2023-10-16 12:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-14  8:02 [ISSUE] " SpidFightFR
2023-10-14  8:04 ` classabbyamp
2023-10-14  8:05 ` SpidFightFR
2023-10-14  8:34 ` sgn
2023-10-14 10:08 ` Johnnynator
2023-10-14 11:27 ` SpidFightFR
2023-10-14 11:27 ` SpidFightFR
2023-10-16 12:21 ` SpidFightFR [this message]
2023-10-16 19:43 ` Building mesa on arm and aarch64 platforms fail SpidFightFR
2023-10-24  2:02 ` zlice
2023-10-26 13:03 ` SpidFightFR
2023-11-03 16:10 ` mhmdanas
2023-11-03 18:59 ` [ISSUE] [CLOSED] " SpidFightFR
2023-11-03 18:59 ` 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=20231016122151.8Q_SKX12LACUFYd7ctm00sE5iBv8-QKwpVEblE76Cqo@z \
    --to=spidfightfr@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).