From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] orangepi_pc_defconfig: bump u-boot to 2018.07 to fix build issue
Date: Fri, 17 Aug 2018 16:52:52 +0200 [thread overview]
Message-ID: <87wospavuj.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180816213151.32178-1-peter@korsgaard.com> (Peter Korsgaard's message of "Thu, 16 Aug 2018 23:31:50 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> u-boot 2018.05 now fails to build with the following error:
> HOSTCC scripts/dtc/flattree.o
> In file included from /builds/buildroot.org/buildroot/output/host/include/libfdt.h:54:0,
> from /builds/buildroot.org/buildroot/output/build/uboot-2018.05/scripts/dtc/libfdt/fdt.c:54:
> /builds/buildroot.org/buildroot/output/host/include/libfdt_env.h:82:24: error: redefinition of 'fdt16_to_cpu'
> static inline uint16_t fdt16_to_cpu(fdt16_t x)
> ^~~~~~~~~~~~
> In file included from /builds/buildroot.org/buildroot/output/build/uboot-2018.05/scripts/dtc/libfdt/fdt.c:51:0:
> /builds/buildroot.org/buildroot/output/build/uboot-2018.05/scripts/dtc/libfdt/libfdt_env.h:81:24: note: previous definition of 'fdt16_to_cpu' was here
> static inline uint16_t fdt16_to_cpu(fdt16_t x)
> ^~~~~~~~~~~~
> https://gitlab.com/buildroot.org/buildroot/-/jobs/88314886
> Fix it by bumping the u-boot version to 2018.07.
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed both, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2018-08-17 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 21:31 [Buildroot] [PATCH 1/2] orangepi_pc_defconfig: bump u-boot to 2018.07 to fix build issue Peter Korsgaard
2018-08-16 21:31 ` [Buildroot] [PATCH 2/2] orangepi_pc_defconfig: bump linux to 4.17.15 to include latest fixes Peter Korsgaard
2018-08-17 14:52 ` Peter Korsgaard [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=87wospavuj.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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.