From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: meta-networking rp-pppoe
Date: Thu, 9 May 2013 14:38:29 -0500 [thread overview]
Message-ID: <518BFB35.5070202@windriver.com> (raw)
I'm having a couple of problems with rp-pppoe.
The first issue is simple. '${P}' is used in the SRC_URI, so if I am configured
to use multilibs I get failures. The following fixes it:
-SRC_URI = "http://www.roaringpenguin.com/files/download/${P}.tar.gz \
+SRC_URI = "http://www.roaringpenguin.com/files/download/${BP}.tar.gz \
The second issue however, is something I haven't been able to figure out. When
running the do_configure task, I get a failure:
checking packing order of bit fields... no defaults for cross-compiling
configure: error: ./configure failed for src
Looking into this, there is a patch that appears to be expecting something to
pass in "rpppoe_cv_pack_bitfields" with a value of 'normal' or 'rev'. But I
don't see anything in the recipe that actually sets that value.
Is this is a bug in the integration, or am I missing something?
reply other threads:[~2013-05-09 19:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=518BFB35.5070202@windriver.com \
--to=mark.hatle@windriver.com \
--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