From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: FTBFS: mesa for mips* with i686 build environment.
Date: Mon, 03 Aug 2020 20:47:26 +0200 [thread overview]
Message-ID: <20200803184726.bZMbu6z1SitWVDUpsILhk7oMZ61Mpw6dcrPGdvN6gcY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24020@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 445 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/issues/24020#issuecomment-668183294
Comment:
This looks like a glibc -> musl cross issue. Also happens with non mips archs. Looks like a issue with meson (libm is techinically found, but musl only has static archive of `libm` but no `.so` symlink, somwhere in this check the found `libm.so` on the host is found and leaks into the cross setup.
next prev parent reply other threads:[~2020-08-03 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 15:09 [ISSUE] " pullmoll
2020-08-03 18:47 ` Johnnynator [this message]
2021-01-17 16:05 ` [ISSUE] [CLOSED] " pullmoll
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=20200803184726.bZMbu6z1SitWVDUpsILhk7oMZ61Mpw6dcrPGdvN6gcY@z \
--to=johnnynator@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).