From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] FTBFS: mesa for mips* with i686 build environment.
Date: Sun, 17 Jan 2021 17:05:18 +0100 [thread overview]
Message-ID: <20210117160518.-J1VvwTaGREgefNwfgg2Q12XkWDH-3XNbsbPjjlXIR0@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: 3164 bytes --]
Closed issue by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/24020
Description:
Trying to build `mesa` for our `mips*` targets, which are `musl` only, results in an error about missing `libm-2.30.so`.
This happens only if the build environment is `i686`.
Using an `i686-musl` ~~or `x86_64`~~ build environment works fine, ~~where the latter has differing word size which may cause other problems~~. Correcting myself: `x86_64` yields the same error.
It seems that a host dependency makes its way into the target dependencies.
Here's the relevant output if that helps.
```
…
WARNING: Library target 'OSMesa' has 'name_prefix' set. Compilers may not find it from its '-lOSMesa' linker flag in the 'osmesa.pc' pkg-config file.
WARNING: Library target 'OSMesa' has 'name_prefix' set. Compilers may not find it from its '-lOSMesa' linker flag in the 'osmesa-uninstalled.pc' pkg-config file.
Message: Configuration summary:
prefix: /usr
libdir: lib
includedir: include
OpenGL: yes (ES1: yes ES2: yes)
OSMesa: libOSMesa(Gallium)
DRI platform: drm
DRI drivers: no
DRI driver dir: /usr/lib/dri
GLX: DRI-based
EGL: yes
EGL drivers: builtin:egl_dri2 builtin:egl_dri3
GBM: yes
EGL/Vulkan/VL platforms: x11 drm wayland surfaceless
Vulkan drivers: no
llvm: yes
llvm-version: 10.0.0
Gallium drivers: swrast
Gallium st: mesa
HUD lmsensors: yes
Shared-glapi: yes
Build targets in project: 113
WARNING: Project specifies a minimum meson_version '>= 0.46' but uses features which were added in newer versions:
* 0.51.0: {'dep.get_variable'}
* 0.52.0: {'version arg in find_program'}
Option buildtype is: plain [default: debugoptimized]
Option b_ndebug is: true [default: if-release]
Option cpp_std is: gnu++14 [default: c++14]
Found ninja-1.10.0 at /usr/bin/ninja
WARNING: custom_target 'glcpp-parse.[ch]' has more than one output! Using the first one.
WARNING: custom_target 'glsl_parser' has more than one output! Using the first one.
WARNING: custom_target 'program_parse_tab.[ch]' has more than one output! Using the first one.
=> mesa-20.1.4_2: running post_configure ...
=> mesa-20.1.4_2: running pre-build hook: 02-script-wrapper ...
=> mesa-20.1.4_2: running do_build ...
ninja: Entering directory `build'
ninja: error: '/usr/mips-linux-musl/usr/lib/libm-2.30.so', needed by 'src/gallium/targets/dri/libgallium_dri.so', missing and no known rule to make it
=> ERROR: mesa-20.1.4_2: do_build: '${make_cmd} -C ${meson_builddir} ${makejobs} ${make_build_args} ${make_build_target}' exited with 1
=> ERROR: in do_build() at common/build-style/meson.sh:122
```
This would be a problem for people trying to cross build mips on their own.
Myself I can work around it as I have `i686-musl` also.
prev parent reply other threads:[~2021-01-17 16:05 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
2021-01-17 16:05 ` pullmoll [this message]
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=20210117160518.-J1VvwTaGREgefNwfgg2Q12XkWDH-3XNbsbPjjlXIR0@z \
--to=pullmoll@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).