From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot ts4800_defconfig no longer builds
Date: Sat, 10 Aug 2019 10:54:11 +0200 [thread overview]
Message-ID: <20190810105411.42aa7518@windsurf.home> (raw)
Hello Patrick,
The ts4800_defconfig you have contributed to Buildroot no longer builds:
https://gitlab.com/buildroot.org/buildroot/-/jobs/269139300
The error is not visible directly in the Gitlab CI output, but
inspecting the full build log reveals this:
/tmp/cceWXtEN.s: Assembler messages:
/tmp/cceWXtEN.s:869: Error: .err encountered
/tmp/cceWXtEN.s:908: Error: .err encountered
/tmp/cceWXtEN.s:964: Error: .err encountered
/tmp/cceWXtEN.s:1114: Error: .err encountered
/tmp/cceWXtEN.s:1294: Error: .err encountered
CC fs/ext4/namei.o
/tmp/cceWXtEN.s:3832: Error: .err encountered
CC fs/ext2/xattr.o
LD fs/debugfs/debugfs.o
CC fs/jffs2/compr.o
LD fs/debugfs/built-in.o
CC fs/kernfs/mount.o
CC fs/lockd/clntlock.o
CC fs/ext2/xattr_user.o
CC fs/jbd2/commit.o
CC fs/nfs/client.o
CC fs/jbd2/recovery.o
scripts/Makefile.build:291: recipe for target 'fs/fat/dir.o' failed
make[3]: *** [fs/fat/dir.o] Error 1
make[3]: *** Waiting for unfinished jobs....
This happens because we updated our default gcc version to gcc 8.x, and
the kernel you're using is too old and doesn't have fixes to work with
gcc 8.x. Could you update to a newer kernel version ?
Also, could you send a patch adding yourself as a maintainer for this
defconfig in our DEVELOPERS file ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next reply other threads:[~2019-08-10 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-10 8:54 Thomas Petazzoni [this message]
2019-08-18 19:48 ` [Buildroot] Buildroot ts4800_defconfig no longer builds Thomas Petazzoni
2019-09-19 16:38 ` Vivien Didelot
2019-09-19 19:15 ` Thomas Petazzoni
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=20190810105411.42aa7518@windsurf.home \
--to=thomas.petazzoni@bootlin.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.