Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Joe Slater <jslater@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: [meta-networking][PATCH 1/1] iscsi-initiator-utils: do not regenerate prom_lex.c
Date: Thu, 15 Jun 2017 10:22:05 -0700	[thread overview]
Message-ID: <1497547325-11931-1-git-send-email-jslater@windriver.com> (raw)

prom_lex.c is provided in source.  If we try to remake
it from prom_lex.l, we will not find "lex" since it is
not in recipe-sysroot-native.  If we do manage to provide
lex, the new source will not compile.

Signed-off-by: Joe Slater <jslater@windriver.com>
---
 .../iscsi-initiator-utils/iscsi-initiator-utils_2.0.874.bb              | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta-networking/recipes-daemons/iscsi-initiator-utils/iscsi-initiator-utils_2.0.874.bb b/meta-networking/recipes-daemons/iscsi-initiator-utils/iscsi-initiator-utils_2.0.874.bb
index 72a17b0..16ac199 100644
--- a/meta-networking/recipes-daemons/iscsi-initiator-utils/iscsi-initiator-utils_2.0.874.bb
+++ b/meta-networking/recipes-daemons/iscsi-initiator-utils/iscsi-initiator-utils_2.0.874.bb
@@ -58,6 +58,8 @@ do_configure () {
 }
 
 do_compile () {
+    # Make sure we DO NOT regenerate prom_lex.c.
+    mv ${S}/utils/fwparam_ibft/prom_lex.l ${S}/utils/fwparam_ibft/prom_lex.l.unused
     oe_runmake -C ${S} ${EXTRA_OEMAKE} user
 }
 
-- 
2.7.4



             reply	other threads:[~2017-06-15 17:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-15 17:22 Joe Slater [this message]
2017-06-16  6:05 ` [meta-networking][PATCH 1/1] iscsi-initiator-utils: do not regenerate prom_lex.c Khem Raj

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=1497547325-11931-1-git-send-email-jslater@windriver.com \
    --to=jslater@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