From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: barebox@lists.infradead.org
Subject: Re: debug in PBL
Date: Tue, 5 Mar 2013 21:29:50 +0100 [thread overview]
Message-ID: <20130305202950.GP23022@game.jcrosoft.org> (raw)
In-Reply-To: <1362510919.493936441@f30.mail.ru>
On 23:15 Tue 05 Mar , Alexander Shiyan wrote:
> > On Tue, Mar 05, 2013 at 07:52:28PM +0400, Alexander Shiyan wrote:
> > > Hello All.
> > >
> > > I tried to compile latest bb.
> > > pcm038 + pbl + debug level 7
> > >
> > > Compilation failed with following error:
> > > LD arch/arm/pbl/zbarebox
> > > arch/arm/mach-imx/built-in-pbl.o: In function `imx_nand_load_image':
> > > /home/git/bb-mar05/arch/arm/mach-imx/external-nand-boot.c:232: undefined reference to `printf'
> > >
> > > How we should handle debug messages in PBL in this case?
> >
> > Until recently the debug macro was defined empty, now it expands to
> > printf and only compiled away when the debug level is lower. It seems
> > we have to either drop the debug() calls in the pbl or add an empty
> > printf implementation.
>
> As far i understand "__PBL__" condition should be used for this?
yes __PBL__ indicate you are compiled for the pbl target
Best Regards,
J.
>
> ---
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2013-03-05 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 15:52 Alexander Shiyan
2013-03-05 16:32 ` Jean-Christophe PLAGNIOL-VILLARD
2013-03-05 19:00 ` Sascha Hauer
2013-03-05 19:15 ` Re[2]: " Alexander Shiyan
2013-03-05 20:29 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
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=20130305202950.GP23022@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=shc_work@mail.ru \
/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