Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Christopher Larson <clarson@kergoth.com>,
	Fang Jia <fang.jia@windriver.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] toolchain-scripts.bbclass: unset command_not_found_handle
Date: Tue, 1 Dec 2015 12:04:11 +0800	[thread overview]
Message-ID: <565D1C3B.8030201@windriver.com> (raw)
In-Reply-To: <CABcZAN=zqR_W8S=eUNAZ4R95QsCsv7eB+ym4hanSHfeBXZHgJg@mail.gmail.com>



On 12/01/2015 11:48 AM, Christopher Larson wrote:
> On Mon, Nov 30, 2015 at 3:50 AM, Fang Jia <fang.jia@windriver.com
> <mailto:fang.jia@windriver.com>> wrote:
>
>     On Ubuntu-system, When sourcing the env.sh from an exported sdk, and
>     running a bogus linux command (for example "asd"), a core dump of
>     python is usually generated.
>
>     Unset the command_not_found_handle to fix it.
>
>     Signed-off-by: Fang Jia <fang.jia@windriver.com <mailto:fang.jia@windriver.com>>
>
>
> Will this syntax be valid for non-bash environments? What about dash and zsh?

unset is part of posix shell, I think it's fine to use it here.

// Robert

> You have to be careful to use portable constructs in a script which is sourced
> like this.
> --
> Christopher Larson
> clarson at kergoth dot com
> Founder - BitBake, OpenEmbedded, OpenZaurus
> Maintainer - Tslib
> Senior Software Engineer, Mentor Graphics
>
>


  reply	other threads:[~2015-12-01  4:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30  8:50 [PATCH] toolchain-scripts.bbclass: unset command_not_found_handle Fang Jia
2015-12-01  3:48 ` Christopher Larson
2015-12-01  4:04   ` Robert Yang [this message]
2015-12-01  4:08     ` Christopher Larson

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=565D1C3B.8030201@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=clarson@kergoth.com \
    --cc=fang.jia@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox