All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V3] linuxdoc-tools-native: Makedoc.sh uses /tmp and fails w/ noexec mount
Date: Mon, 6 Oct 2014 09:51:36 -0500	[thread overview]
Message-ID: <5432AC78.9020004@windriver.com> (raw)
In-Reply-To: <1412607012-84068-1-git-send-email-mark.hatle@windriver.com>

V3 - Only difference to V2 is the summary line of the commit message.  After 
sending it I realized it wasn't in the right OE format.

V2 - Only difference is adding back in the missing DESTDIR=

On 10/6/14, 9:50 AM, Mark Hatle wrote:
> From: Konrad Scherer <Konrad.Scherer@windriver.com>
>
> The Makedoc.sh script uses the following line to set TMPDIR
>
> export TMPDIR=`mktemp -d ${TMPDIR:-/tmp}/ldt.XXXXXXXXXX`;
>
> and then later in the script:
>
> chmod u+x $TMPDIR/linuxdoc
>
> Since TMPDIR is not set the script will default to /tmp and if /tmp
> is set to noexec (which is becoming more common), the chmod call fails.
>
> Signed-off-by: Konrad Scherer <Konrad.Scherer@windriver.com>
> Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
> ---
>   meta/recipes-devtools/linuxdoc-tools/linuxdoc-tools-native_0.9.69.bb | 4 ++++
>   1 file changed, 4 insertions(+)
>
> diff --git a/meta/recipes-devtools/linuxdoc-tools/linuxdoc-tools-native_0.9.69.bb b/meta/recipes-devtools/linuxdoc-tools/linuxdoc-tools-native_0.9.69.bb
> index ed6ab73..a8a90fc 100644
> --- a/meta/recipes-devtools/linuxdoc-tools/linuxdoc-tools-native_0.9.69.bb
> +++ b/meta/recipes-devtools/linuxdoc-tools/linuxdoc-tools-native_0.9.69.bb
> @@ -19,3 +19,7 @@ inherit autotools-brokensep native
>   do_configure () {
>   	oe_runconf
>   }
> +
> +do_install() {
> +	oe_runmake 'DESTDIR=${D}' 'TMPDIR=${T}' install
> +}
>



      reply	other threads:[~2014-10-06 14:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-06 14:50 [PATCH V3] linuxdoc-tools-native: Makedoc.sh uses /tmp and fails w/ noexec mount Mark Hatle
2014-10-06 14:51 ` Mark Hatle [this message]

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=5432AC78.9020004@windriver.com \
    --to=mark.hatle@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.