From: Yann E. MORIN <yann.morin.1998@free.fr>
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:54:55 +0100 [thread overview]
Message-ID: <20191115205455.GA32494@scaer> (raw)
In-Reply-To: <20191115201909.GA24188@x230>
Petr, All,
On 2019-11-15 21:19 +0100, Petr Vorel spake thusly:
[--SNIP--]
> 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.
Thank you for the very good investigations! :-)
> I didn't realized that there could be more MUSL versions,
> next time, I'll check with utils/test-pkg
I noticed the build failure by just building the config file from the
autobuild referenced in your commit log. I did not even try to build it
with 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).
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2019-11-15 20:54 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
2019-11-15 20:54 ` Yann E. MORIN [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=20191115205455.GA32494@scaer \
--to=yann.morin.1998@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox