From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2019-01-18
Date: Sun, 20 Jan 2019 22:00:37 +0200 [thread overview]
Message-ID: <871s57nlp6.fsf@tarshish> (raw)
In-Reply-To: <20190120195338.GA10424@itchy>
Hi Eric,
On Sun, Jan 20 2019, Eric Le Bihan wrote:
> On 2019-01-19 08:00, Thomas Petazzoni wrote:
>> Hello,
>>
>> Build statistics for 2019-01-18
>> ===============================
>>
>> branch | OK | NOK | TIM | TOT |
>> 2018.02.x | 22 | 0 | 0 | 22 |
>> 2018.11.x | 27 | 0 | 1 | 28 |
>> master | 200 | 50 | 2 | 252 |
>>
> [...]
>> riscv32 | skalibs-2.6.4.0 | NOK | http://autobuild.buildroot.net/results/6c5ee3b8a94c7c2434a3aad303d6c7844b566b72 |
>
> This one may require deep digging... The build fails because mcontext_t
> is not defined.
>
> Looking at sysdeps/unix/sysv/linux/riscv/sys/ucontext.h, this may happen
> if __USE_MISC is not defined, which means that, according to
> include/features.h, _DEFAULT_SOURCE would not be defined...
>
> Should marking skalibs as "depends on !BR2_riscv" be acceptable as a
> temporary fix?
A number of packages are affected. Mark promised[1] to take a look soon.
baruch
[1] http://lists.busybox.net/pipermail/buildroot/2019-January/240690.html
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
prev parent reply other threads:[~2019-01-20 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2019-01-18 Thomas Petazzoni
2019-01-20 19:53 ` Eric Le Bihan
2019-01-20 20:00 ` Baruch Siach [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=871s57nlp6.fsf@tarshish \
--to=baruch@tkos.co.il \
--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.