mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Christoph G. Baumann" <chris@sgoc.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Issue compiling Linux 4.6 for ARM64
Date: Wed, 15 Jun 2016 12:53:41 +0200 (CEST)	[thread overview]
Message-ID: <1581329493.39539.e687c1bd-0087-4d75-be9a-3f2dad18d66b.open-xchange@email.1und1.de> (raw)
In-Reply-To: <20160614075606.GJ9575@pengutronix.de>

Hello,

> Michael Olbrich <m.olbrich@pengutronix.de> hat am 14. Juni 2016 um 09:56
> geschrieben:
> 
> 
> Hmm, most extra options are blacklisted for the kernel. Try running PTXdist
> with '-v'. With this option enabled, the wrapper will print the full
> compiler command line. Then you can compare it with a kernel build outside
> PTXdist.

the example output for a compiler call looks like this:

aarch64-v8a-linux-gnu-gcc -Wp,-MD,drivers/usb/storage/.usual-tables.o.d
 -nostdinc -isystem
/opt/OSELAS.Toolchain-2014.12.2/aarch64-v8a-linux-gnu/gcc-4.9.2-glibc-2.20-binutils-2.24-kernel-4.3-sanitized/lib/gcc/aarch64-v8a-linux-gnu/4.9.2/include
-I./arch/arm64/include -Iarch/arm64/include/generated/uapi
-Iarch/arm64/include/generated  -Iinclude -I./arch/arm64/include/uapi
-Iarch/arm64/include/generated/uapi -I./include/uapi -Iinclude/generated/uapi
-include ./include/linux/kconfig.h -D__KERNEL__ -mlittle-endian -Wall -Wundef
-Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common
-Werror-implicit-function-declaration -Wno-format-security -std=gnu89
-mgeneral-regs-only -fno-asynchronous-unwind-tables
-fno-delete-null-pointer-checks -O2 --param=allow-store-data-races=0
-Wframe-larger-than=2048 -fno-stack-protector -Wno-unused-but-set-variable
-fno-omit-frame-pointer -fno-optimize-sibling-calls
-fno-var-tracking-assignments -g -Wdeclaration-after-statement -Wno-pointer-sign
-fno-strict-overflow -fconserve-stack -Werror=implicit-int
-Werror=strict-prototypes -Werror=date-time -DCC_HAVE_ASM_GOTO -Idrivers/scsi
   -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(usual_tables)"
 -D"KBUILD_MODNAME=KBUILD_STR(usb_storage)" -c -o
drivers/usb/storage/.tmp_usual-tables.o drivers/usb/storage/usual-tables.c


The output just before the error:

+ aarch64-v8a-linux-gnu-ld -EL -p --no-undefined -X --build-id -o .tmp_vmlinux1
-T ./arch/arm64/kernel/vmlinux.lds arch/arm64/kernel/head.o init/built-in.o
--start-group usr/built-in.o arch/arm64/kernel/built-in.o
arch/arm64/mm/built-in.o arch/arm64/net/built-in.o arch/arm64/crypto/built-in.o
./drivers/firmware/efi/libstub/lib.a kernel/built-in.o certs/built-in.o
mm/built-in.o fs/built-in.o ipc/built-in.o security/built-in.o crypto/built-in.o
block/built-in.o arch/arm64/lib/lib.a lib/lib.a arch/arm64/lib/built-in.o
lib/built-in.o drivers/built-in.o sound/built-in.o firmware/built-in.o
net/built-in.o virt/built-in.o --end-group
+ kallsyms .tmp_vmlinux1 .tmp_kallsyms1.o
+ info KSYM .tmp_kallsyms1.o
+ '[' '' '!=' silent_ ']'
+ printf '  %-7s %s\n' KSYM .tmp_kallsyms1.o
+ local kallsymopt
+ '[' -n '' ']'
+ '[' -n y ']'
+ kallsymopt=' --all-symbols'
+ '[' -n '' ']'
+ '[' -n '' ']'
+ '[' -n y ']'
+ kallsymopt=' --all-symbols --base-relative'
+ local 'aflags=-D__ASSEMBLY__  -Wa,-gdwarf-2 -DCC_HAVE_ASM_GOTO
                   		       -nostdinc -isystem
/opt/OSELAS.Toolchain-2014.12.2/aarch64-v8a-linux-gnu/gcc-4.9.2-glibc-2.20-binutils-2.24-kernel-4.3-sanitized/lib/gcc/aarch64-v8a-linux-gnu/4.9.2/include
-I./arch/arm64/include -Iarch/arm64/include/generated/uapi
-Iarch/arm64/include/generated  -Iinclude -I./arch/arm64/include/uapi
-Iarch/arm64/include/generated/uapi -I./include/uapi -Iinclude/generated/uapi
-include ./include/linux/kconfig.h -D__KERNEL__ -mlittle-endian  '
  KSYM    .tmp_kallsyms1.o
++ basename .tmp_kallsyms1.o .o
+ local afile=.tmp_kallsyms1.S
+ aarch64-v8a-linux-gnu-nm -n .tmp_vmlinux1
+ scripts/kallsyms --all-symbols --base-relative
kallsyms failure: relative symbol value 0xffffff8008080000 out of range in
relative mode
+ on_exit
+ '[' 1 -ne 0 ']'
+ cleanup
+ rm -f .old_version
+ rm -f .tmp_System.map
+ rm -f .tmp_kallsyms1.S
+ rm -f .tmp_version
+ rm -f .tmp_vmlinux1
+ rm -f System.map
+ rm -f vmlinux
+ rm -f vmlinux.o
make[1]: *** [vmlinux] Error 1
make[1]: Leaving directory
`/work/Sourcecode/ptxdist/platform-testH3/build-target/linux-4.6'



Regards,
Christoph

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2016-06-15 10:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 20:53 Christoph G. Baumann
2016-06-14  7:56 ` Michael Olbrich
2016-06-15 10:53   ` Christoph G. Baumann [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=1581329493.39539.e687c1bd-0087-4d75-be9a-3f2dad18d66b.open-xchange@email.1und1.de \
    --to=chris@sgoc.de \
    --cc=ptxdist@pengutronix.de \
    /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