From: Daniel Schultz <d.schultz@phytec.de>
To: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: GCC 6.3 Linker error
Date: Fri, 5 May 2017 17:11:30 +0200 [thread overview]
Message-ID: <890269e4-1c96-691c-065b-82ad619b3140@phytec.de> (raw)
Hi everyone,
when I build the Barebox with GCC 6.3 and am335x_defconfig, I get the
following error:
| LD commands/built-in.o
| LD drivers/usb/built-in.o
| PBLLD drivers/usb/built-in-pbl.o
| LD fs/built-in.o
| PBLLD fs/built-in-pbl.o
| LD drivers/mtd/ubi/built-in.o
| LD drivers/mtd/built-in.o
| PBLLD drivers/mtd/built-in-pbl.o
| LD drivers/built-in.o
| PBLLD drivers/built-in-pbl.o
| GEN .version
| CHK include/generated/compile.h
| UPD include/generated/compile.h
| CC common/version.o
| LD common/built-in.o
| LD .tmp_barebox1
| arm-phytec-linux-gnueabi-ld: .tmp_barebox1: Not enough room for
program headers, try linking with -N
| arm-phytec-linux-gnueabi-ld: final link failed: Bad value
| make[2]: *** [.tmp_barebox1] Error 1
| make[1]: *** [_all] Error 2
| make: *** [all] Error 2
| ERROR: Function failed: do_compile (log file is located at
/home/schultz/yocto/PD17.2.0/build/tmp/work/phyboard_wega_am335x_2-phytec-linux-gnueabi/barebox/2017.03.0-phy1-r7.0/temp/log.do_compile.23997)
ERROR: Task
(/home/schultz/yocto/PD17.2.0/sources/poky/../meta-phytec/recipes-bsp/barebox/barebox_2017.03.0-phy1.bb:do_compile)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 497 tasks of which 495 didn't need to be
rerun and 1 failed.
NOTE: Writing buildhistory
has somebody else faced with this problem? I figured out that linking
with "-nmagic" fix this problem.
--
Mit freundlichen Grüßen,
With best regards,
Daniel Schultz
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2017-05-05 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 15:11 Daniel Schultz [this message]
2017-05-08 10:57 ` Sascha Hauer
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=890269e4-1c96-691c-065b-82ad619b3140@phytec.de \
--to=d.schultz@phytec.de \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox