From: Venkatesh <venkateshv377@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] u-boot: update to version 2014.07
Date: Sun, 10 Jul 2016 16:49:56 +0000 (UTC) [thread overview]
Message-ID: <loom.20160710T184732-108@post.gmane.org> (raw)
In-Reply-To: 20141107223001.GG9512@denix.org
Denys Dmytriyenko <denis@...> writes:
>
> On Fri, Nov 07, 2014 at 03:54:45PM -0500, Denys Dmytriyenko wrote:
> > On Fri, Nov 07, 2014 at 08:43:38PM +0000, Burton, Ross wrote:
> > > On 7 November 2014 19:41, Denys Dmytriyenko <denis@...> wrote:
> > >
> > > > > | scripts/basic/fixdep: 1: scripts/basic/fixdep: Syntax error: word
> > > > > unexpected (expecting ")")
> > > > >
> > > > > I suspect the real problem is:
> > > > >
> > > > > $ file fixdep
> > > > > fixdep: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically
> > > > > linked (uses shared libs), for GNU/Linux 2.6.32,
> > > > > BuildID[sha1]=0xb4ea84a189f10b4f3e08fb10f8e490135e2b920c, not stripped
> > > > >
> > > > > It appears to have been built using the target compiler, not the host.
> > > >
> > > > Ross,
> > > >
> > > > I'm a bit lost here - as you said above, this is a target build and
yet you
> > > > say it shouldn't use the target compiler. Can you please explain
what you
> > > > mean?
> > >
> > >
> > > Yes, it's building a binary (fixdep) and then executing it. That binary
> > > needs to be built with the host compiler (BUILD_CC).
> > >
> > > Easily replicated for me with "MACHINE=qemuarm bitbake u-boot-mkimage".
> >
> > Ah, got it. Didn't realize, as I build -native version. Give me a sec to
fix
> > it. BTW, 2014.10 is out and I've been using it for a bit now - planning on
> > sending the update soon...
>
> Ross,
>
> I've just sent an RFC patch to allow building mkimage for the target. I'd
like
> to collect feedback for it first, but feel free to squash it with the
previous
> patch, if it's accepted (or commit separately - your choice). The update to
> 2014.10 will follow shortly, I just want this version to get through
first, as
> it has been in limbo for a few months...
>
I am encountering this problem while compiling my driver code for beagle
bone black.
scripts/basic/fixdep: 1: scripts/basic/fixdep: Syntax error: word unexpected
(expecting ")")
make[2]: *** [/home/venkyvenkatesh/Driver_Compiler/driver_code.o] Error 2
make[1]: *** [_module_/home/venkyvenkatesh/Driver_Compiler] Error 2
make[1]: Leaving directory
`/home/venkyvenkatesh/Driver_Compiler/usr/src/linux-3.14.4.1-bone-armhf.com'
make: *** [all] Error 2
next prev parent reply other threads:[~2016-07-10 17:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-14 3:34 [PATCH] u-boot: update to version 2014.07 Denys Dmytriyenko
2014-09-14 21:40 ` Burton, Ross
2014-09-15 13:33 ` Otavio Salvador
2014-09-15 13:33 ` Otavio Salvador
2014-09-15 14:21 ` Burton, Ross
2014-09-15 14:33 ` Otavio Salvador
2014-09-15 14:36 ` Burton, Ross
2014-09-15 14:41 ` Otavio Salvador
2014-09-16 23:23 ` Denys Dmytriyenko
2014-11-05 14:56 ` Burton, Ross
2014-11-05 15:09 ` Burton, Ross
2014-11-07 19:43 ` Denys Dmytriyenko
2014-11-07 19:41 ` Denys Dmytriyenko
2014-11-07 20:43 ` Burton, Ross
2014-11-07 20:52 ` Otavio Salvador
2014-11-07 20:54 ` Denys Dmytriyenko
2014-11-07 22:30 ` Denys Dmytriyenko
2014-11-09 22:57 ` Burton, Ross
2016-07-10 16:49 ` Venkatesh [this message]
2016-07-10 21:28 ` Denys Dmytriyenko
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=loom.20160710T184732-108@post.gmane.org \
--to=venkateshv377@gmail.com \
--cc=openembedded-core@lists.openembedded.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