From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] arc: axs103 compile broken ?
Date: Tue, 14 Jun 2016 07:07:54 +0200 [thread overview]
Message-ID: <575F912A.7070506@denx.de> (raw)
Hello Sjoerd,
as I just write a tbot testcase, which checks patches, which moves
a config option to Kconfig, I tested also to compile arc boards, and
the first try immediately failed with:
pollux:u-boot-dxr2 hs [master] $ make axs103_defconfig
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/zconf.lex.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
#
# configuration written to .config
#
pollux:u-boot-dxr2 hs [master] $ make -s -j8 all
In file included from drivers/net/designware.c:21:0:
drivers/net/designware.h:11:22: fatal error: asm/gpio.h: Datei oder Verzeichnis nicht gefunden
#include <asm/gpio.h>
^
compilation terminated.
scripts/Makefile.build:280: recipe for target 'drivers/net/designware.o' failed
make[1]: *** [drivers/net/designware.o] Error 1
Makefile:1208: recipe for target 'drivers/net' failed
make: *** [drivers/net] Error 2
make: *** Warte auf noch nicht beendete Prozesse...
pollux:u-boot-dxr2 hs [master] $
looking into the git history of drivers/net/designware.c it seems
to me, that the commit:
commit 90b7fc924adf "net: designware: support phy reset device-tree bindings"
added the missing include.
$ find arch/arc/include/asm/ -name gpio.h
$
I used the toolchain from:
https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases/tag/arc-2015.12
Some ideas? May I did something wrong?
bye,
Heiko
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next reply other threads:[~2016-06-14 5:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 5:07 Heiko Schocher [this message]
2016-06-14 7:15 ` [U-Boot] arc: axs103 compile broken ? Alexey Brodkin
2016-06-16 0:39 ` Simon Glass
2016-06-16 6:36 ` Alexey Brodkin
2016-06-17 3:52 ` Simon Glass
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=575F912A.7070506@denx.de \
--to=hs@denx.de \
--cc=u-boot@lists.denx.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