From: Kevin Du Huanpeng <u74147@gmail.com>
To: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject:
Date: Wed, 8 Oct 2014 13:41:03 +0800 [thread overview]
Message-ID: <CANvTkNYb_zj62mcuzTcY5WOiTU07HnSqkiz851wswY0eN59euw@mail.gmail.com> (raw)
Hi,
I find that most xxx_defconfig stop linking when console support set
to CONSOLE_NONE
compile log like:
http://paste.ubuntu.com/8518456/
- - - -
| Symbol: CONSOLE_NONE [=y] |
| Type : boolean |
| Prompt: none |
| Location: |
| -> General Settings |
| -> console support (<choice> [=y]) |
| Defined at common/Kconfig:522 |
| Depends on: <choice> |
- - - -
most error causes by pr_print undefined.
this macro/function is
defined in:
common/console_common.c
declare in:
include/printk.h
when CONSOLE_NONE is defined,
pr_print is not compiled (rid by #ifndef/#endif) with common/console_common.o
but <printk.h> is included allmost anywhere by including <common.h>
- - - -
#ifndef __COMMON_H_
#define __COMMON_H_ 1
#include <stdio.h>
...
#include <asm/common.h>
#include <printk.h>
- - - -
so using pr_print always can past compile because it is declared by
including <common.h>.
but breaks link.
I am confusing with CONSOLE_NONE, what is it mean?
1. the board don't have a console?
is the board still can have a serial port, but not accepts input?
2. where should the debug messages go?
the serial port is not a console but
when CONSOLE_NONE defined, printf just a nothing but return a 0,
but the pr_print() declared but not defined.
- - - -
FILE: include/stdio.h
static inline int printf(const char *fmt, ...)
{
return 0;
}
- - - -
- - - -
duhuanpeng
(+86)13719074147
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
reply other threads:[~2014-10-08 5:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CANvTkNYb_zj62mcuzTcY5WOiTU07HnSqkiz851wswY0eN59euw@mail.gmail.com \
--to=u74147@gmail.com \
--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