public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Sujith H <sujith.h@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Sujith Haridasan <Sujith_Haridasan@mentor.com>,
	Christopher Larson <chris_larson@mentor.com>
Subject: [PATCH] ruby: ensure that .ext/rdoc is gone in compile
Date: Mon, 29 Aug 2016 18:17:04 +0530	[thread overview]
Message-ID: <1472474824-22715-1-git-send-email-sujith.h@gmail.com> (raw)

From: Christopher Larson <chris_larson@mentor.com>

rdoc gets unhappy if this already exists, so remove it before building.

Without this, it's possible to hit this error:

    Directory .ext/rdoc already exists, but it looks like it isn't an RDoc
    directory.

Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Sujith Haridasan <Sujith_Haridasan@mentor.com>
---
 meta/recipes-devtools/ruby/ruby.inc | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/meta/recipes-devtools/ruby/ruby.inc b/meta/recipes-devtools/ruby/ruby.inc
index fde67e9..d8f6882 100644
--- a/meta/recipes-devtools/ruby/ruby.inc
+++ b/meta/recipes-devtools/ruby/ruby.inc
@@ -37,3 +37,7 @@ do_configure_prepend() {
     sed -i "s#%%TARGET_CFLAGS%%#$TARGET_CFLAGS#; s#%%TARGET_LDFLAGS%%#$TARGET_LDFLAGS#" ${S}/common.mk
     rm -rf ${S}/ruby/
 }
+
+do_compile_prepend () {
+    rm -rf .ext/rdoc
+}
-- 
1.9.1



             reply	other threads:[~2016-08-29 12:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-29 12:47 Sujith H [this message]
2016-08-29 12:47 ` [PATCH] ruby: ensure that .ext/rdoc is gone in compile Alexander Kanavin
2016-08-31  7:37   ` sujith h

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=1472474824-22715-1-git-send-email-sujith.h@gmail.com \
    --to=sujith.h@gmail.com \
    --cc=Sujith_Haridasan@mentor.com \
    --cc=chris_larson@mentor.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