From: U.Mutlu <for-gmane@mutluit.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Build error: caused by CONFIG_SPL_LOG_CONSOLE
Date: Sat, 13 Apr 2019 01:01:52 +0200 [thread overview]
Message-ID: <q8r5d2$2l8a$1@blaine.gmane.org> (raw)
If I activate "Enable logging support in SPL" (ie. CONFIG_SPL_LOG_CONSOLE),
ie. the following window in make menuconfig:
Logging --->
[*] Enable logging support
[*] Enable logging support in SPL
[*] Enable logging support in TPL
(5) Maximum log level to record
(3) Maximum log level to record in SPL (NEW)
(3) Maximum log level to record in TPL
(6) Default logging level to display
[*] Allow log output to the console
[*] Allow log output to the console in SPL (NEW)
[*] Allow log output to the console in SPL
[ ] Provide a test for logging
[*] Log all functions which return an error
then the build fails as follows (paths sanitized):
arm-linux-gnueabihf-ld.bfd: common/built-in.o: in function `log_get_cat_name':
/.../u-boot/common/log.c:48: undefined reference to `uclass_get_name'
arm-linux-gnueabihf-ld.bfd: common/built-in.o: in function `_log':
/.../u-boot/common/log.c:212: undefined reference to `vsnprintf'
scripts/Makefile.spl:384: recipe for target 'spl/u-boot-spl' failed
make[1]: *** [spl/u-boot-spl] Error 1
Makefile:1664: recipe for target 'spl/u-boot-spl' failed
make: *** [spl/u-boot-spl] Error 2
Deactivating "Enable logging support in SPL" builds ok.
Version:
U-Boot 2019.04-00077-g48ff1bc4f0
(using stock git source tree w/o any own modifications)
Platform:
CONFIG_ARM=y
CONFIG_SYS_ARCH="arm"
CONFIG_SYS_CPU="armv7"
CONFIG_SYS_SOC="sunxi"
CONFIG_SYS_BOARD="sunxi"
CONFIG_SYS_CONFIG_NAME="sun7i"
CONFIG_DEFAULT_DEVICE_TREE="sun7i-a20-lamobo-r1"
next reply other threads:[~2019-04-12 23:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 23:01 U.Mutlu [this message]
2019-04-24 13:21 ` [U-Boot] Build error: caused by CONFIG_SPL_LOG_CONSOLE 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='q8r5d2$2l8a$1@blaine.gmane.org' \
--to=for-gmane@mutluit.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