From: Masahiro Yamada <yamada.m@jp.panasonic.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/2] Allow empty board dir and fix build error of arcangel4 boards
Date: Mon, 3 Mar 2014 19:03:16 +0900 [thread overview]
Message-ID: <1393840998-27018-1-git-send-email-yamada.m@jp.panasonic.com> (raw)
Currently arcangel4 and arcangel4-be boards are broken.
$ make CROSS_COMPILE=arc-buildroot-linux-uclibc- arcangel4_config all
Configuring for arcangel4 board...
GEN include/autoconf.mk.dep
GEN include/autoconf.mk
CHK include/config/uboot.release
[snip]
LDS u-boot.lds
LD u-boot
arc-buildroot-linux-uclibc-ld.bfd: cannot find board/synopsys/arcangel4/built-in.o: No such file or directory
make[1]: *** [u-boot] Error 1
make: *** [build-one-by-one] Error 2
The cause of the build error is that neither "obj-y" nor "obj-"
is defined in board/synopsys/arcangel4/Makefile.
In kbuild, empty makefiles are not allowed.
The same sort of build errors have happened before this.
Commit 2aa43f70 resolved the build error by adding
"obj- := __dummy__.o",
but it was not the best solution.
If there are no source files to compile under the board directory,
it is better to not descend into that directory.
Masahiro Yamada (2):
kbuild: allow empty board directories
arc: arcangel4: set board entry <none> to fix a build error
Makefile | 2 +-
board/synopsys/arcangel4/Makefile | 11 -----------
boards.cfg | 4 ++--
config.mk | 2 ++
mkconfig | 6 ++++--
5 files changed, 9 insertions(+), 16 deletions(-)
delete mode 100644 board/synopsys/arcangel4/Makefile
--
1.8.3.2
next reply other threads:[~2014-03-03 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 10:03 Masahiro Yamada [this message]
2014-03-03 10:03 ` [U-Boot] [PATCH 1/2] kbuild: allow empty board directories Masahiro Yamada
2014-03-04 19:19 ` [U-Boot] [U-Boot,1/2] " Tom Rini
2014-03-03 10:03 ` [U-Boot] [PATCH 2/2] arc: arcangel4: set board entry <none> to fix a build error Masahiro Yamada
2014-03-04 19:19 ` [U-Boot] [U-Boot, " Tom Rini
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=1393840998-27018-1-git-send-email-yamada.m@jp.panasonic.com \
--to=yamada.m@jp.panasonic.com \
--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