From: Ira W. Snyder <iws@ovro.caltech.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot] A Problem of u-boot on TI PandaBoard porting
Date: Fri, 6 Jan 2012 08:21:17 -0800 [thread overview]
Message-ID: <20120106162116.GA10470@ovro.caltech.edu> (raw)
In-Reply-To: <4F068820.5060301@logicpd.com>
On Fri, Jan 06, 2012 at 12:35:28AM -0500, Peter Barada wrote:
> On 01/06/2012 12:21 AM, Qiao.HelloWorld at gmail.com wrote:
> > 2012/1/6 John Rigby<john.rigby@linaro.org>
> >
> >>> *u-boot/spl/u-boot-spl.lds:1: syntax error
> >>> make[1]: *** [/home/qian/Desktop/u-boot/spl/u-boot-spl] Error 1
> >>> make[1]: Leaving directory `/home/qian/Desktop/u-boot/spl'
> >>> make: *** [spl/u-boot-spl.bin] Error 2*
> >>>
> >>> I?ve check the file ?spl/u-boot-spl.lds?, the first line is a comment as
> >>> below:
> >>> *// add PandaTest Configuration*
> >>>
> >> Change that comment to a C style one like /* ..... */ and I think the
> >> problem will go away.
> >
> > But it doesn't work...because the 'spl/u-boot-spl.lds' is automatically
> > generated while building. Even if I modify this file, it will be replaced
> > again when I rebuild.
> >
> > However, thanks for your reply.
> Then dig through the build log to find where the file is generated from
> and modify that file...
>
I've run into a problem similar to this before. You probably have a C++
style comment inside your board configuration file. Change it to a C
style comment instead, and the problem goes away.
Ira
next prev parent reply other threads:[~2012-01-06 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 2:02 [U-Boot] A Problem of u-boot on TI PandaBoard porting Qiao.HelloWorld at gmail.com
2012-01-06 4:12 ` John Rigby
2012-01-06 5:21 ` Qiao.HelloWorld at gmail.com
2012-01-06 5:35 ` Peter Barada
2012-01-06 16:21 ` Ira W. Snyder [this message]
2012-01-09 3:27 ` Qiao.HelloWorld at gmail.com
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=20120106162116.GA10470@ovro.caltech.edu \
--to=iws@ovro.caltech.edu \
--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