From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Issues building tinyXML
Date: Thu, 06 Sep 2012 16:08:29 +0100 [thread overview]
Message-ID: <5048BC6D.8080904@communistcode.co.uk> (raw)
In-Reply-To: <1346943545.2673.198.camel@phil-desktop>
On 06/09/12 15:59, Phil Blundell wrote:
> On Thu, 2012-09-06 at 15:53 +0100, Jack Mitchell wrote:
>> I'm failing to be able to build tinyXML which it seems is required for
>> XBMC after it was dropped from their internal tree. The package just has
>> a Makefile and all in all seems a bit sketchy at best. Has anyone come
>> across an error like this before:
>>
>> DEBUG: Executing shell function do_compile
>> NOTE: make -j 7 -e MAKEFLAGS=
>> arm-poky-linux-gnueabi-ld
>> --sysroot=/home/jack/Projects/poky-rasp/raspberry/tmp/sysroots/raspberrypi
>> -o xmltest -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed tinyxml.o
>> tinyxmlparser.o xmltest.o tinyxmlerror.o tinystr.o
>> arm-poky-linux-gnueabi-ld: unrecognized option '-Wl,-O1'
>> arm-poky-linux-gnueabi-ld: use the --help option for usage information
>> make: *** [xmltest] Error 1
> It's using ${LD} where it should be using ${CCLD}. This is, admittedly,
> confusing since one would tend to naïvely assume that ${LDFLAGS} is
> intended for consumption by ${LD} but that is not in fact the case.
>
> I'm not actually sure that there are any places where ${LD} is the right
> thing to use. Maybe that variable should be deleted.
>
> p.
So, would the best way to fix it be something like:
do_compile() {
run_oemake LD="${CCLD}"
}
I'm really only just getting into this so please excuse my naivety.
Thanks,
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
next prev parent reply other threads:[~2012-09-06 15:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 14:53 Issues building tinyXML Jack Mitchell
2012-09-06 14:59 ` Phil Blundell
2012-09-06 15:08 ` Jack Mitchell [this message]
2012-09-06 15:09 ` Phil Blundell
2012-09-06 15:15 ` Jack Mitchell
2012-09-06 15:16 ` Phil Blundell
2012-09-06 15:19 ` Jack Mitchell
2012-09-06 15:57 ` Jack Mitchell
2012-09-06 16:08 ` Phil Blundell
2012-09-06 16:15 ` Jack Mitchell
2012-09-06 16:19 ` Jack Mitchell
2012-09-06 16:19 ` Phil Blundell
2012-09-06 16:36 ` Jack Mitchell
2012-09-06 16:42 ` Koen Kooi
2012-09-06 16:44 ` Phil Blundell
2012-09-06 19:47 ` Burton, Ross
2012-09-06 16:46 ` Phil Blundell
2012-09-07 8:16 ` Jack Mitchell
2012-09-13 18:01 ` Andrei Gherzan
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=5048BC6D.8080904@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-devel@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