From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Russell King <linux@armlinux•org.uk>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Masahiro Yamada <masahiroy@kernel•org>
Subject: Re: linux-next: build failure after merge of the arm tree
Date: Mon, 20 Jan 2020 08:31:35 +1100 [thread overview]
Message-ID: <20200120083135.5d90d410@canb.auug.org.au> (raw)
In-Reply-To: <20200120082447.7fea4d55@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1541 bytes --]
Hi all,
On Mon, 20 Jan 2020 08:24:47 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Hi all,
>
> After merging the arm tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
In file included from scripts/dtc/libfdt/libfdt_env.h:12,
from arch/arm/boot/compressed/fdt_rw.c:6:
/usr/lib/gcc-cross/arm-linux-gnueabi/9/include/stdint.h:9:26: error: no include path in which to search for stdint.h
9 | # include_next <stdint.h>
| ^
In file included from arch/arm/boot/compressed/fdt_rw.c:6:
scripts/dtc/libfdt/libfdt_env.h:13:10: fatal error: stdlib.h: No such file or directory
13 | #include <stdlib.h>
| ^~~~~~~~~~
compilation terminated.
In file included from scripts/dtc/libfdt/libfdt_env.h:12,
from arch/arm/boot/compressed/fdt_ro.c:6:
/usr/lib/gcc-cross/arm-linux-gnueabi/9/include/stdint.h:9:26: error: no include path in which to search for stdint.h
9 | # include_next <stdint.h>
| ^
In file included from arch/arm/boot/compressed/fdt_ro.c:6:
scripts/dtc/libfdt/libfdt_env.h:13:10: fatal error: stdlib.h: No such file or directory
13 | #include <stdlib.h>
| ^~~~~~~~~~
> Caused by commit
>
> e3a0e1427dcb ("ARM: 8953/1: decompressor: simplify libfdt builds")
>
> My arm builds are ppc64le hosted cross compiles using Debian's cross
> gcc package.
>
> I have reverted that commit for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-01-19 21:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 21:24 linux-next: build failure after merge of the arm tree Stephen Rothwell
2020-01-19 21:31 ` Stephen Rothwell [this message]
2020-01-19 22:02 ` Russell King - ARM Linux admin
-- strict thread matches above, loose matches on Subject: below --
2024-11-12 23:46 Stephen Rothwell
2024-11-13 0:25 ` Stephen Rothwell
2024-08-20 23:36 Stephen Rothwell
2024-08-21 3:27 ` liuyuntao (F)
2024-05-03 0:15 Stephen Rothwell
2024-05-03 8:18 ` Russell King (Oracle)
2024-05-03 8:23 ` Russell King (Oracle)
2024-05-03 12:08 ` Stephen Rothwell
2024-05-03 12:29 ` Russell King (Oracle)
2022-08-31 9:10 Stephen Rothwell
2022-08-31 9:14 ` Matija Glavinic Pecotic
2021-10-25 23:25 Stephen Rothwell
2017-04-20 22:40 Stephen Rothwell
2017-04-21 7:58 ` Mason
2017-04-21 8:12 ` Stephen Rothwell
2017-04-21 8:30 ` Mason
2017-04-21 23:43 ` Russell King - ARM Linux
2017-04-22 8:41 ` Mason
2017-04-24 4:20 ` Vinod Koul
2017-06-14 19:23 ` Mason
2017-04-21 11:27 ` Mason
2015-05-29 1:09 Stephen Rothwell
2014-04-10 1:35 Stephen Rothwell
2011-03-02 14:13 Stephen Rothwell
2011-03-02 15:55 ` Nicolas Pitre
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=20200120083135.5d90d410@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux@armlinux$(echo .)org.uk \
--cc=masahiroy@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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