Github messages for voidlinux
 help / color / mirror / Atom feed
From: SpidFightFR <SpidFightFR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mesa: update to version 23.1.9.
Date: Wed, 11 Oct 2023 20:01:02 +0200	[thread overview]
Message-ID: <20231011180102.741fnqfzADDlkD-Qrh592VqgYiIMht65SDVoa0o8nB0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46172@inbox.vuxu.org>

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

New comment by SpidFightFR on void-packages repository

https://github.com/void-linux/void-packages/pull/46172#issuecomment-1758204182

Comment:
> ```
>  FAILED: src/compiler/clc/liblibclc.a.p/clc.c.o 
> aarch64-linux-gnu-gcc -Isrc/compiler/clc/liblibclc.a.p -Isrc/compiler/clc -I../src/compiler/clc -Iinclude -I../include -Isrc -I../src -Isrc/mapi -I../src/mapi -Isrc/mesa -I../src/mesa -Isrc/compiler -I../src/compiler -Isrc/compiler/spirv -I../src/compiler/spirv -Isrc/compiler/nir -I../src/compiler/nir -I../src/gallium/include -I/usr/aarch64-linux-gnu/usr/include -fdiagnostics-color=always -DNDEBUG -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=c11 '-DPACKAGE_VERSION="23.1.9"' '-DPACKAGE_BUGREPORT="https://gitlab.freedesktop.org/mesa/mesa/-/issues"' -DHAVE_OPENGL=1 -DHAVE_OPENGL_ES_1=1 -DHAVE_OPENGL_ES_2=1 -DHAVE_SWRAST -DHAVE_R300 -DHAVE_R600 -DHAVE_RADEONSI -DHAVE_NOUVEAU -DHAVE_TEGRA -DHAVE_KMSRO -DHAVE_V3D -DHAVE_VC4 -DHAVE_FREEDRENO -DHAVE_ETNAVIV -DHAVE_LIMA -DHAVE_PANFROST -DHAVE_VIRGL -DHAVE_ZINK -DVIDEO_CODEC_VC1DEC=1 -DVIDEO_CODEC_H264DEC=1 -DVIDEO_CODEC_H264ENC=1 -DVIDEO_CODEC_H265DEC=1 -DVIDEO_CODEC_H265ENC=1 -DHAVE_X11_PLATFORM -DHAVE_WAYLAND_PLATFORM -DHAVE_SURFACELESS_PLATFORM -DHAVE_DRM_PLATFORM -DHAVE_XCB_PLATFORM -DHAVE_ST_VDPAU -DENABLE_ST_OMX_BELLAGIO=0 -DENABLE_ST_OMX_TIZONIA=0 -DHAVE_VA_SURFACE_ATTRIB_DRM_FORMAT_MODIFIERS -DGLX_INDIRECT_RENDERING -DGLX_DIRECT_RENDERING -DGLX_USE_DRM -DALLOW_KCMP -DENABLE_SHADER_CACHE -DHAVE___BUILTIN_BSWAP32 -DHAVE___BUILTIN_BSWAP64 -DHAVE___BUILTIN_CLZ -DHAVE___BUILTIN_CLZLL -DHAVE___BUILTIN_CTZ -DHAVE___BUILTIN_EXPECT -DHAVE___BUILTIN_FFS -DHAVE___BUILTIN_FFSLL -DHAVE___BUILTIN_POPCOUNT -DHAVE___BUILTIN_POPCOUNTLL -DHAVE___BUILTIN_UNREACHABLE -DHAVE___BUILTIN_TYPES_COMPATIBLE_P -DHAVE_FUNC_ATTRIBUTE_CONST -DHAVE_FUNC_ATTRIBUTE_FLATTEN -DHAVE_FUNC_ATTRIBUTE_MALLOC -DHAVE_FUNC_ATTRIBUTE_PURE -DHAVE_FUNC_ATTRIBUTE_UNUSED -DHAVE_FUNC_ATTRIBUTE_WARN_UNUSED_RESULT -DHAVE_FUNC_ATTRIBUTE_WEAK -DHAVE_FUNC_ATTRIBUTE_FORMAT -DHAVE_FUNC_ATTRIBUTE_PACKED -DHAVE_FUNC_ATTRIBUTE_RETURNS_NONNULL -DHAVE_FUNC_ATTRIBUTE_ALIAS -DHAVE_FUNC_ATTRIBUTE_NORETURN -DHAVE_FUNC_ATTRIBUTE_VISIBILITY -DHAVE_UINT128 -DHAVE_REALLOCARRAY -DHAVE_FMEMOPEN -DUSE_GCC_ATOMIC_BUILTINS -DUSE_AARCH64_ASM -DMAJOR_IN_SYSMACROS -DHAS_SCHED_H -DHAS_SCHED_GETAFFINITY -DHAVE_LINUX_FUTEX_H -DHAVE_ENDIAN_H -DHAVE_DLFCN_H -DHAVE_SYS_SHM_H -DHAVE_SYS_INOTIFY_H -DHAVE_STRTOF -DHAVE_MKOSTEMP -DHAVE_TIMESPEC_GET -DHAVE_MEMFD_CREATE -DHAVE_RANDOM_R -DHAVE_FLOCK -DHAVE_STRTOK_R -DHAVE_GETRANDOM -DHAVE_POSIX_FALLOCATE -DHAVE_GNU_QSORT_R -DHAVE_STRUCT_TIMESPEC -DHAVE_PROGRAM_INVOCATION_NAME -DHAVE_ISSIGNALING -DHAVE_POSIX_MEMALIGN -DHAVE_DIRENT_D_TYPE -DHAVE_STRTOD_L -DHAVE_DLADDR -DHAVE_DL_ITERATE_PHDR -DHAVE_ZLIB -DHAVE_ZSTD -DHAVE_COMPRESSION -DHAVE_PTHREAD -DHAVE_PTHREAD_SETAFFINITY -DHAVE_LIBDRM -DHAVE_LIBUDEV -DLLVM_AVAILABLE '-DMESA_LLVM_VERSION_STRING="15.0.7"' -DLLVM_IS_SHARED=1 -DDRAW_LLVM_AVAILABLE -DUSE_LIBELF -DUSE_LIBGLVND=1 -DMESA_EXECMEM -DWL_HIDE_DEPRECATED -DHAVE_DRI -DHAVE_DRI2 -DHAVE_DRI3 -DHAVE_DRI3_MODIFIERS -DHAVE_DRISW_KMS -DHAVE_LIBSENSORS=1 -Werror=implicit-function-declaration -Werror=missing-prototypes -Werror=return-type -Werror=empty-body -Werror=incompatible-pointer-types -Werror=int-conversion -Wimplicit-fallthrough -Wmisleading-indentation -Wno-missing-field-initializers -Wno-format-truncation -Wno-nonnull-compare -fno-math-errno -fno-trapping-math -fno-common -Wno-unused-function -Werror=format -Wformat-security -ffunction-sections -fdata-sections -Wno-unused-variable -Wno-unused-but-set-variable -fstack-clash-protection -D_FORTIFY_SOURCE=2 -O2 -pipe -march=armv8-a -ffile-prefix-map=/builddir/mesa-23.1.9/build=. -fPIC -pthread -isystem/usr/include -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -MD -MQ src/compiler/clc/liblibclc.a.p/clc.c.o -MF src/compiler/clc/liblibclc.a.p/clc.c.o.d -o src/compiler/clc/liblibclc.a.p/clc.c.o -c ../src/compiler/clc/clc.c
> In file included from /usr/include/features.h:514,
>                  from /usr/include/bits/libc-header-start.h:33,
>                  from /usr/include/stdlib.h:26,
>                  from ../src/util/hash_table.h:31,
>                  from ../src/compiler/nir/nir.h:31,
>                  from ../src/compiler/clc/clc.c:24:
> /usr/include/gnu/stubs.h:7:11: fatal error: gnu/stubs-32.h: No such file or directory
>     7 | # include <gnu/stubs-32.h>
>       |           ^~~~~~~~~~~~~~~~
> compilation terminated.
> ```
> 
> The problem here, is that it includes non cross header with the cross compiler. Adding more `-devel` deps won't fix this. The specific part that causes the issue is `-isystem/usr/include`, which does get added by `LLVM`. I don't know yet why this happens.

alright... the thing that troubles me a bit is that i don't understand why it happens... So if something similar had to happen in the future, i don't know how to find a workaround like you did in your next message... :sweat: 

  parent reply	other threads:[~2023-10-11 18:01 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-21 20:02 [PR PATCH] mesa: update to version 23.1.8 SpidFightFR
2023-09-21 20:03 ` [PR PATCH] [Updated] " SpidFightFR
2023-09-21 20:05 ` SpidFightFR
2023-09-21 20:14 ` SpidFightFR
2023-09-21 20:29 ` mhmdanas
2023-09-21 20:29 ` mhmdanas
2023-09-22  4:03 ` SpidFightFR
2023-09-26 13:02 ` SpidFightFR
2023-09-26 13:03 ` SpidFightFR
2023-09-30 12:14 ` [PR PATCH] [Updated] " SpidFightFR
2023-09-30 12:15 ` mesa: update to version 23.2.1 SpidFightFR
2023-09-30 12:36 ` SpidFightFR
2023-10-02  9:45 ` SpidFightFR
2023-10-07  7:21 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-07  7:44 ` SpidFightFR
2023-10-07 13:46 ` mesa: update to version 23.1.9 mhmdanas
2023-10-07 13:47 ` mhmdanas
2023-10-07 13:58 ` SpidFightFR
2023-10-07 13:58 ` SpidFightFR
2023-10-10  7:10 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-10  7:28 ` SpidFightFR
2023-10-10  7:28 ` SpidFightFR
2023-10-10  7:28 ` SpidFightFR
2023-10-10  7:33 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-10  7:40 ` SpidFightFR
2023-10-11 17:15 ` SpidFightFR
2023-10-11 17:36 ` Johnnynator
2023-10-11 17:46 ` Johnnynator
2023-10-11 17:57 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-11 17:58 ` SpidFightFR
2023-10-11 17:59 ` SpidFightFR
2023-10-11 18:01 ` SpidFightFR [this message]
2023-10-11 18:02 ` SpidFightFR
2023-10-12  2:13 ` sgn
2023-10-12 12:45 ` sgn
2023-10-12 19:07 ` SpidFightFR
2023-10-14  7:29 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-16 17:30 ` SpidFightFR
2023-10-16 17:34 ` SpidFightFR
2023-10-16 17:35 ` mesa: update to version 23.2.1 SpidFightFR
2023-10-16 17:38 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-16 17:48 ` Anachron
2023-10-16 18:01 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-16 18:03 ` SpidFightFR
2023-10-16 18:20 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-16 18:20 ` SpidFightFR
2023-11-01  3:39 ` rationalize-zz
2023-11-01 10:20 ` [PR PATCH] [Updated] " SpidFightFR
2023-11-01 10:20 ` SpidFightFR
2023-11-01 10:42 ` SpidFightFR
2023-11-01 16:13 ` [PR REVIEW] " Johnnynator
2023-11-01 16:22 ` SpidFightFR
2023-11-01 16:26 ` [PR PATCH] [Updated] " SpidFightFR
2023-11-01 17:09 ` [PR REVIEW] " SpidFightFR
2023-11-02  9:12 ` [PR PATCH] [Merged]: " Johnnynator
2023-11-02  9:13 ` Johnnynator
2023-11-02 17:37 ` 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=20231011180102.741fnqfzADDlkD-Qrh592VqgYiIMht65SDVoa0o8nB0@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).