From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/ltp-testsuite: proper fix for missing __kernel_fsid_t
Date: Fri, 15 Nov 2019 21:19:09 +0100 [thread overview]
Message-ID: <20191115201909.GA24188@x230> (raw)
In-Reply-To: <20191115193118.GA19966@x230>
Hi Yann,
> Musl config which works:
> * /home/pevik/br-test-pkg/br-x86-64-musl/.config
> BR2_DEFCONFIG="$(CONFIG_DIR)/defconfig"
> BR2_TOOLCHAIN_USES_MUSL=y
> BR2_TOOLCHAIN_EXTERNAL_MUSL=y
> BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.org/toolchains/tarballs/br-x86-64-musl-2019.05.1.tar.bz2"
> BR2_TOOLCHAIN_EXTERNAL_CUSTOM_MUSL=y
> BR2_PACKAGE_MUSL_COMPAT_HEADERS=y
> BR2_PACKAGE_MUSL_FTS=y
> # BR2_TOOLCHAIN_EXTERNAL_MUSL_CROSS is not set
> Broken one (
> * pc_x86_64_bios_defconfig, libc changed to musl
> BR2_DEFCONFIG="/home/pevik/install/src/buildroot.git/configs/pc_x86_64_bios_defconfig"
> BR2_TOOLCHAIN_USES_MUSL=y
> BR2_TOOLCHAIN_BUILDROOT_MUSL=y
> BR2_TOOLCHAIN_BUILDROOT_LIBC="musl"
> BR2_PACKAGE_MUSL=y
> BR2_PACKAGE_MUSL_COMPAT_HEADERS=y
> BR2_PACKAGE_MUSL_FTS=y
> # BR2_TOOLCHAIN_EXTERNAL_MUSL_CROSS is not set
> There are more differences in these 2 configs, but I bet this
> BR2_TOOLCHAIN_BUILDROOT_MUSL=y vs. BR2_TOOLCHAIN_EXTERNAL_MUSL=y can be
> the difference.
OK, external toolchain has older MUSL, it's without
f67b3c17 ("sys/fanotify.h: update for linux v5.1")
from v1.1.23. => need to fix autoconf in LTP for latest musl release.
I didn't realized that there could be more MUSL versions,
next time, I'll check with utils/test-pkg
support/config-fragments/autobuild/*musl*
and also for internal toolchain (somehow wasn't able to use
support/config-fragments/autobuild/*internal-*musl* with utils/test-pkg).
Kind regards,
Petr
next prev parent reply other threads:[~2019-11-15 20:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 20:02 [Buildroot] [PATCH v2 1/1] package/ltp-testsuite: proper fix for missing __kernel_fsid_t Petr Vorel
2019-11-14 20:20 ` Petr Vorel
2019-11-14 21:30 ` Yann E. MORIN
2019-11-15 7:07 ` Petr Vorel
2019-11-15 19:31 ` Petr Vorel
2019-11-15 20:19 ` Petr Vorel [this message]
2019-11-15 20:54 ` Yann E. MORIN
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=20191115201909.GA24188@x230 \
--to=petr.vorel@gmail.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.