public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "kernelci.org bot" <bot@kernelci.org>
Cc: linux-next@vger.kernel.org
Subject: Re: next/pending-fixes build: 212 builds: 1 failed, 211 passed, 808 errors, 367 warnings (v5.10-rc3-420-g5364e201065c)
Date: Fri, 13 Nov 2020 10:58:19 +1100	[thread overview]
Message-ID: <20201113105819.09e2f416@canb.auug.org.au> (raw)
In-Reply-To: <5fadc9f9.1c69fb81.e93e.d857@mx.google.com>

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

Hi kernelci.org,

On Thu, 12 Nov 2020 15:49:13 -0800 (PST) "kernelci.org bot" <bot@kernelci.org> wrote:
>
> Errors summary:
> 
>     126  /usr/include/features.h:424:12: fatal error: sys/cdefs.h: No such file or directory
>     56   /usr/include/stdio.h:27:10: fatal error: bits/libc-header-start.h: No such file or directory
>     15   arc-elf32-gcc: error: unrecognized command line option ‘-pthread’
>     14   /bin/sh: 3: llc: not found
>     14   /bin/sh: 1: llc: not found
>     14   /bin/sh: 1: clang: not found
>     12   ionmap_test.c:14:10: fatal error: drm/drm.h: No such file or directory
>     8    udmabuf.c:13:10: fatal error: linux/udmabuf.h: No such file or directory
>     8    reuseport_bpf_numa.c:24:10: fatal error: numa.h: No such file or directory
>     8    proc-fsconfig-hidepid.c:20:10: fatal error: linux/mount.h: No such file or directory
>     8    pm_nl_ctl.c:19:10: fatal error: linux/mptcp.h: No such file or directory
>     8    pidfd_wait.c:97:4: error: ‘struct clone_args’ has no member named ‘exit_signal’
>     8    pidfd_wait.c:96:4: error: ‘struct clone_args’ has no member named ‘flags’
>     8    pidfd_wait.c:95:4: error: ‘struct clone_args’ has no member named ‘pidfd’
>     8    pidfd_wait.c:94:4: error: ‘struct clone_args’ has no member named ‘parent_tid’

...

Is this going to get fixed up, please ... it makes these reports not very useful :-(

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2020-11-12 23:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-12 23:49 next/pending-fixes build: 212 builds: 1 failed, 211 passed, 808 errors, 367 warnings (v5.10-rc3-420-g5364e201065c) kernelci.org bot
2020-11-12 23:58 ` Stephen Rothwell [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=20201113105819.09e2f416@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=bot@kernelci.org \
    --cc=linux-next@vger.kernel.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