From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] ruby: ensure that .ext/rdoc is gone in compile
Date: Mon, 29 Aug 2016 15:47:45 +0300 [thread overview]
Message-ID: <c7e422d5-1d5e-1376-df7f-21c84ca362e5@linux.intel.com> (raw)
In-Reply-To: <1472474824-22715-1-git-send-email-sujith.h@gmail.com>
On 08/29/2016 03:47 PM, Sujith H wrote:
> 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.
> +
> +do_compile_prepend () {
> + rm -rf .ext/rdoc
> +}
>
The fix may be fixing the symptom and masking a different issue, have
you checked when and how the error occurs?
Alex
next prev parent reply other threads:[~2016-08-29 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 12:47 [PATCH] ruby: ensure that .ext/rdoc is gone in compile Sujith H
2016-08-29 12:47 ` Alexander Kanavin [this message]
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=c7e422d5-1d5e-1376-df7f-21c84ca362e5@linux.intel.com \
--to=alexander.kanavin@linux.intel.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