All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: Openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] populate_sdk_base.bbclass: Improve debugging capabilities for SDK installer
Date: Fri, 25 Jan 2013 11:34:04 +0200	[thread overview]
Message-ID: <5102518C.7000201@intel.com> (raw)
In-Reply-To: <1359074326-12029-2-git-send-email-jason.wessel@windriver.com>



On 01/25/2013 02:38 AM, Jason Wessel wrote:
>  executable_files=$($SUDO_EXEC find $native_sysroot -type f -perm +111)
> -$SUDO_EXEC ${env_setup_script%/*}/relocate_sdk.py $target_sdk_dir $dl_path $executable_files
> -if [ $? -ne 0 ]; then
> -	echo "SDK could not be set up. Relocate script failed. Abort!"
> -	exit 1


> +echo "#!/bin/bash" > ${env_setup_script%/*}/relocate_sdk.sh
> +echo exec $SUDO_EXEC ${env_setup_script%/*}/relocate_sdk.py $target_sdk_dir $dl_path $executable_files >> ${env_setup_script%/*}/relocate_sdk.sh
> +chmod 755 ${env_setup_script%/*}/relocate_sdk.sh
The last 3 lines will certainly fail if installation takes place in a
location you don't have rights... So, you'll end up with no
relocate_sdk.sh script.

Thanks,
Laurentiu
> +if [ $relocate = 1 ] ; then
> +	${env_setup_script%/*}/relocate_sdk.sh
> +	if [ $? -ne 0 ]; then
> +		echo "SDK could not be set up. Relocate script failed. Abort!"
> +		exit 1
> +	fi
>  fi



  reply	other threads:[~2013-01-25  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-25  0:38 [PATCH 1/2] relocate_sdk.py: Fix corruption of sdk binaries Jason Wessel
2013-01-25  0:38 ` [PATCH 2/2] populate_sdk_base.bbclass: Improve debugging capabilities for SDK installer Jason Wessel
2013-01-25  9:34   ` Laurentiu Palcu [this message]
2013-01-25  9:29 ` [PATCH 1/2] relocate_sdk.py: Fix corruption of sdk binaries Laurentiu Palcu
2013-01-25 13:06 ` Jason Wessel

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=5102518C.7000201@intel.com \
    --to=laurentiu.palcu@intel.com \
    --cc=Openembedded-core@lists.openembedded.org \
    --cc=jason.wessel@windriver.com \
    /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.