From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: meta-freescale@yoctoproject.org
Subject: [meta-fsl-arm-extra] GCC 5 errors while building boundary kernel 3.10.53
Date: Tue, 29 Sep 2015 19:43:18 +0200 [thread overview]
Message-ID: <560ACDB6.2040201@pseudoterminal.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 527 bytes --]
Hello,
I tried to build the boundary kernel 3.10.53 with the latest Yocto
master version, which has moved to GCC 5. But this fails, because it
can't find a gcc5 specific header:
tmp/work-shared/nitrogen6x/kernel-source/include/linux/compiler-gcc.h:103:30:
fatal error: linux/compiler-gcc5.h: No such file or directory
I attached the full Yocto compilation log.
Given that 3.10 is becoming rather old, it would perhaps make sense to
move to a newer version, instead of just fixing this one issue.
Carlos
[-- Attachment #2: yocto-master-linux-boundary-compile-error.log --]
[-- Type: text/x-log, Size: 6872 bytes --]
DEBUG: Executing shell function do_compile
NOTE: make -j 4 uImage CC=arm-poky-linux-gnueabi-gcc -mno-thumb-interwork -marm -fuse-ld=bfd LD=arm-poky-linux-gnueabi-ld.bfd LOADADDR=0x10008000
GEN /home/build/BuildSetups/yocto-master/poky/build/tmp/work/nitrogen6x-poky-linux-gnueabi/linux-boundary/3.10.53-r0/build/Makefile
scripts/kconfig/conf --silentoldconfig Kconfig
GEN /home/build/BuildSetups/yocto-master/poky/build/tmp/work/nitrogen6x-poky-linux-gnueabi/linux-boundary/3.10.53-r0/build/Makefile
WRAP arch/arm/include/generated/asm/auxvec.h
WRAP arch/arm/include/generated/asm/bitsperlong.h
WRAP arch/arm/include/generated/asm/cputime.h
WRAP arch/arm/include/generated/asm/current.h
CHK include/generated/uapi/linux/version.h
WRAP arch/arm/include/generated/asm/emergency-restart.h
UPD include/generated/uapi/linux/version.h
WRAP arch/arm/include/generated/asm/errno.h
WRAP arch/arm/include/generated/asm/exec.h
WRAP arch/arm/include/generated/asm/ioctl.h
WRAP arch/arm/include/generated/asm/ipcbuf.h
WRAP arch/arm/include/generated/asm/irq_regs.h
WRAP arch/arm/include/generated/asm/kdebug.h
WRAP arch/arm/include/generated/asm/local.h
WRAP arch/arm/include/generated/asm/local64.h
WRAP arch/arm/include/generated/asm/msgbuf.h
WRAP arch/arm/include/generated/asm/param.h
WRAP arch/arm/include/generated/asm/parport.h
WRAP arch/arm/include/generated/asm/poll.h
WRAP arch/arm/include/generated/asm/resource.h
WRAP arch/arm/include/generated/asm/sections.h
WRAP arch/arm/include/generated/asm/segment.h
WRAP arch/arm/include/generated/asm/sembuf.h
WRAP arch/arm/include/generated/asm/serial.h
WRAP arch/arm/include/generated/asm/shmbuf.h
WRAP arch/arm/include/generated/asm/siginfo.h
WRAP arch/arm/include/generated/asm/sizes.h
WRAP arch/arm/include/generated/asm/socket.h
WRAP arch/arm/include/generated/asm/sockios.h
WRAP arch/arm/include/generated/asm/termbits.h
WRAP arch/arm/include/generated/asm/termios.h
WRAP arch/arm/include/generated/asm/timex.h
WRAP arch/arm/include/generated/asm/trace_clock.h
WRAP arch/arm/include/generated/asm/types.h
WRAP arch/arm/include/generated/asm/unaligned.h
Using /home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source as source for kernel
CHK include/generated/utsrelease.h
UPD include/generated/utsrelease.h
HOSTCC scripts/genksyms/genksyms.o
HOSTCC scripts/dtc/checks.o
CC scripts/mod/empty.o
HOSTCC scripts/mod/mk_elfconfig
CC scripts/mod/devicetable-offsets.s
In file included from /home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/include/linux/compiler.h:54:0,
from /home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/include/uapi/linux/stddef.h:1,
from /home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/include/linux/stddef.h:4,
from /home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/include/uapi/linux/posix_types.h:4,
from /home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/include/uapi/linux/types.h:13,
from /home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/include/linux/types.h:5,
from /home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/include/linux/mod_devicetable.h:11,
from /home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/scripts/mod/devicetable-offsets.c:2:
/home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/include/linux/compiler-gcc.h:103:30: fatal error: linux/compiler-gcc5.h: No such file or directory
compilation terminated.
make[4]: *** [scripts/mod/devicetable-offsets.s] Error 1
make[3]: *** [scripts/mod] Error 2
make[3]: *** Waiting for unfinished jobs....
HOSTCC scripts/dtc/data.o
SHIPPED scripts/genksyms/lex.lex.c
SHIPPED scripts/dtc/dtc-lexer.lex.c
SHIPPED scripts/genksyms/keywords.hash.c
SHIPPED scripts/dtc/dtc-parser.tab.h
SHIPPED scripts/genksyms/parse.tab.h
SHIPPED scripts/dtc/dtc-parser.tab.c
HOSTCC scripts/dtc/dtc.o
SHIPPED scripts/genksyms/parse.tab.c
HOSTCC scripts/genksyms/lex.lex.o
HOSTCC scripts/dtc/flattree.o
HOSTCC scripts/dtc/fstree.o
HOSTCC scripts/dtc/livetree.o
Generating include/generated/mach-types.h
CC kernel/bounds.s
In file included from /home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/include/linux/compiler.h:54:0,
from /home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/include/uapi/linux/stddef.h:1,
from /home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/include/linux/stddef.h:4,
from /home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/include/uapi/linux/posix_types.h:4,
from /home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/include/uapi/linux/types.h:13,
from /home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/include/linux/types.h:5,
from /home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/include/linux/page-flags.h:8,
from /home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/kernel/bounds.c:9:
/home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/include/linux/compiler-gcc.h:103:30: fatal error: linux/compiler-gcc5.h: No such file or directory
compilation terminated.
make[3]: *** [kernel/bounds.s] Error 1
make[2]: *** [prepare0] Error 2
make[2]: *** Waiting for unfinished jobs....
HOSTCC scripts/genksyms/parse.tab.o
HOSTCC scripts/dtc/srcpos.o
HOSTCC scripts/dtc/treesource.o
HOSTCC scripts/dtc/util.o
HOSTCC scripts/dtc/dtc-lexer.lex.o
HOSTLD scripts/genksyms/genksyms
HOSTCC scripts/dtc/dtc-parser.tab.o
HOSTLD scripts/dtc/dtc
make[2]: *** [scripts] Error 2
make[1]: *** [sub-make] Error 2
make: *** [all] Error 2
WARNING: exit code 1 from a shell command.
ERROR: oe_runmake failed
ERROR: Function failed: do_compile (log file is located at /home/build/BuildSetups/yocto-master/poky/build/tmp/work/nitrogen6x-poky-linux-gnueabi/linux-boundary/3.10.53-r0/temp/log.do_compile.11165)
next reply other threads:[~2015-09-29 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 17:43 Carlos Rafael Giani [this message]
2015-09-29 17:58 ` [meta-fsl-arm-extra] GCC 5 errors while building boundary kernel 3.10.53 Otavio Salvador
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=560ACDB6.2040201@pseudoterminal.org \
--to=dv@pseudoterminal.org \
--cc=meta-freescale@yoctoproject.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 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.