From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] sheevaplug_defconfig: bump u-boot to 2018.07 to fix build issue
Date: Fri, 17 Aug 2018 16:51:29 +0200 [thread overview]
Message-ID: <876009caha.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180816201139.19656-1-peter@korsgaard.com> (Peter Korsgaard's message of "Thu, 16 Aug 2018 22:11:37 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> u-boot 2016.05 no longer builds with the default gcc/binutils versions:
> https://gitlab.com/buildroot.org/buildroot/-/jobs/88314946
> LD u-boot
> fs/built-in.o: In function `read_symbol':
> /builds/buildroot.org/buildroot/output/build/uboot-2016.05/fs/jffs2/mini_inflate.c:129: undefined reference to `pull_bit'
> fs/built-in.o: In function `decompress_huffman':
> /builds/buildroot.org/buildroot/output/build/uboot-2016.05/fs/jffs2/mini_inflate.c:159: undefined reference to `pull_bits'
> /builds/buildroot.org/buildroot/output/build/uboot-2016.05/fs/jffs2/mini_inflate.c:170: undefined reference to `pull_bits'
> ..
> /builds/buildroot.org/buildroot/output/host/bin/arm-buildroot-linux-uclibcgnueabi-ld.bfd: BFD (GNU Binutils) 2.29.1 assertion fail elf32-arm.c:9509
> Makefile:1192: recipe for target 'u-boot' failed
> make[1]: *** [u-boot] Error 1
> make[1]: Leaving directory '/builds/buildroot.org/buildroot/output/build/uboot-2016.05'
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed all 3, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2018-08-17 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 20:11 [Buildroot] [PATCH 1/3] sheevaplug_defconfig: bump u-boot to 2018.07 to fix build issue Peter Korsgaard
2018-08-16 20:11 ` [Buildroot] [PATCH 2/3] sheevaplug_defconfig: bump linux to 4.14.63 to include latest fixes Peter Korsgaard
2018-08-16 20:11 ` [Buildroot] [PATCH 3/3] sheevaplug: add a basic readme Peter Korsgaard
2018-08-17 14:51 ` 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=876009caha.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox