From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox <barebox@lists.infradead.org>
Subject: Re: error building sandbox with debug on
Date: Fri, 12 Oct 2012 10:51:33 +0200 [thread overview]
Message-ID: <20121012085133.GP27665@pengutronix.de> (raw)
In-Reply-To: <20121012040621.GA3300@greatfirst.com>
On Fri, Oct 12, 2012 at 12:06:21PM +0800, zzs wrote:
> my src is f9df22b002af99532b66360e08128e
>
> now config it:
> CROSS_COMPILE= ARCH=sandbox make sandbox_defconfig
>
> Then add the the flowwing line in front of include/common.h
>
> #define DEBUG
>
> and run "CROSS_COMPILE= ARCH=sandbox make", this command output
> the flowwing message:
>
> --------------------------------------
> CC common/meminfo.o
> common/meminfo.c: In function 'display_meminfo':
> common/meminfo.c:12:49: error: '_stext' undeclared (first use in this function)
> common/meminfo.c:12:49: note: each undeclared identifier is reported only once for each function it appears in
> common/meminfo.c:12:57: error: '_etext' undeclared (first use in this function)
> common/meminfo.c:13:49: error: '__bss_start' undeclared (first use in this function)
> common/meminfo.c:13:62: error: '__bss_stop' undeclared (first use in this function)
> make[1]: *** [common/meminfo.o] Error 1
> make: *** [common] Error 2
This is because ./arch/sandbox/board/barebox.lds.S is missing these
variables. I don't know how much sense it makes to add these. You could
just try and add them as done in the other linker scripts.
This is a bug in the sense that you should be able to compile with DEBUG
defined, but otherwise you can just comment the lines out and ignore
this. It will have no bad effect on the resulting binary.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-10-12 8:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 4:06 zzs
2012-10-12 8:51 ` Sascha Hauer [this message]
2012-10-12 9:15 ` Jean-Christophe PLAGNIOL-VILLARD
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=20121012085133.GP27665@pengutronix.de \
--to=s.hauer@pengutronix.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