All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Carlson <JoelsonCarl@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2020-08-23
Date: Tue, 25 Aug 2020 22:46:02 -0600	[thread overview]
Message-ID: <CA+1k=2Z4spkyAiZcVz4WWOm0fVi2ENCeJao-poC1QPTv-EzuFA@mail.gmail.com> (raw)
In-Reply-To: <5f43739e.1c69fb81.d68ae.c851SMTPIN_ADDED_MISSING@mx.google.com>

On Mon, Aug 24, 2020 at 2:00 AM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> Hello,
>
> Autobuilder failures
> ====================
>
> Below is a list of build failures reported by the Buildroot
> autobuilders in relation to packages or CPU
> architectures you are in charge of. Please help us
> improving the quality of Buildroot by investigating
> those build failures and sending patches to fix
> them.Thanks!
>
> Results for the 'next' branch
> -----------------------------
>
> Build failures related to your packages:
>
>     arch     |             reason             |                                       url
> -------------+--------------------------------+---------------------------------------------------------------------------------
>   riscv64    |        capnproto-0.8.0         | http://autobuild.buildroot.net/results/4016581368b5016ad11f9be355ec96590cd5b093
>
>
> --
> http://autobuild.buildroot.net

It appears that the build errors are an issue where the code is calling:
getcontext(ucontext_t *)

The man page for getcontext says it should be:
getcontext(ucontext_t *)

But the riscv64 musl toolchain is defining getcontext:
getcontext(struct __ucontext *)
which after a define for __ucontext becomes:
getcontext(struct ucontext *)

The toolchain defines both "struct ucontext" (in ucontext.h) and
"struct ucontext_t" (in signal.h) that are very similar, but not
exactly the same.

I'm not sure exactly on what the best way to fix this would be.
Delving into toolchain and header differences isn't really my strong
suit, so I figured I'd ask the mailing list for feedback/advice.

Thanks.
-Joel

           reply	other threads:[~2020-08-26  4:46 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <5f43739e.1c69fb81.d68ae.c851SMTPIN_ADDED_MISSING@mx.google.com>]

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='CA+1k=2Z4spkyAiZcVz4WWOm0fVi2ENCeJao-poC1QPTv-EzuFA@mail.gmail.com' \
    --to=joelsoncarl@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.