All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Kashyap Gada <gada.kashyap@gmail.com>,
	 "Burton, Ross" <ross.burton@intel.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Source Command Permission Denied
Date: Tue, 03 Jun 2014 10:14:53 -0700	[thread overview]
Message-ID: <538E028D.2090200@linux.intel.com> (raw)
In-Reply-To: <CANJXcUasi1Pf3T4Zq5Fz7ExKq7Zm9FKCYERRLuaaLODuEZR0Hg@mail.gmail.com>

On 06/03/2014 09:20 AM, Kashyap Gada wrote:
> Thank you Ross.
>
> I actually ran into another problem in bitbaking core-image-sato from the
> getting started guide at the yocto site which led me into changing to a
> setup which doesnot include mounting of any drive to my ubuntu
> distribution. the problem is as follows.
>
> While compiling of e2fsprogs-1.42.9-r0 do_compile (pid 5276)
>
> the details of the error log generated is as follows
>

<SNIP>

> chmod: cannot operate on dangling symlink 'prof_err.h'
> chmod: prof_err.h: new permissions are r-xrwxrwx, not r-xr-xr-x
> chmod: prof_err.c: new permissions are r-xrwxrwx, not r-xr-xr-x

Looks like your still having some sort of permissions issue. Where 
exactly are you doing your build?  What type of filesystem?

Sau!


> make[2]: *** [prof_err.h] Error 1
> make[2]: *** Waiting for unfinished jobs....
> make[2]: Leaving directory
> `/mnt/kashyap/hda/yocto/poky/build/tmp/work/i586-poky-linux/e2fsprogs/1.42.9-r0/build/misc'
> make[1]: *** [all-progs-recursive] Error 1
> make[1]: Leaving directory
> `/mnt/kashyap/hda/yocto/poky/build/tmp/work/i586-poky-linux/e2fsprogs/1.42.9-r0/build'
> make: *** [all] Error 2
> ERROR: oe_runmake failed
> WARNING: exit code 1 from a shell command.
> ERROR: Function failed: do_compile (log file is located at
> /mnt/kashyap/hda/yocto/poky/build/tmp/work/i586-poky-linux/e2fsprogs/1.42.9-r0/temp/log.do_compile.5276)
>
>
>
>
> Sorry for attaching this to this list.
>
>
>
> On Tue, Jun 3, 2014 at 9:20 PM, Burton, Ross <ross.burton@intel.com> wrote:
>
>> So you probably lost every executable mode when you did that.  Make a
>> fresh clone and reapply your changes, that will be easier than finding
>> every file that isn't executable when it should be.
>>
>> Ross
>>
>> On 3 June 2014 16:49, Kashyap Gada <gada.kashyap@gmail.com> wrote:
>>> its copied!
>>>
>>>
>>> On Tue, Jun 3, 2014 at 9:16 PM, Burton, Ross <ross.burton@intel.com>
>> wrote:
>>>>
>>>> On 3 June 2014 16:39, Kashyap Gada <gada.kashyap@gmail.com> wrote:
>>>>> bash: /home/kashyap/yocto/poky/scripts/oe-setup-builddir: Permission
>>>>> denied
>>>>
>>>> The permissions on that file don't involve +x.  Is that a fresh
>>>> checkout of poky or copied from the removable media?
>>>>
>>>> Ross
>>>
>>>
>>
>
>
>


  reply	other threads:[~2014-06-03 17:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-30  4:06 Source Command Permission Denied Kashyap Gada
2014-05-30 11:10 ` Burton, Ross
2014-05-30 12:36   ` Kashyap Gada
2014-06-03 15:39     ` Kashyap Gada
2014-06-03 15:46       ` Burton, Ross
2014-06-03 15:49         ` Kashyap Gada
2014-06-03 15:50           ` Burton, Ross
2014-06-03 16:20             ` Kashyap Gada
2014-06-03 17:14               ` Saul Wold [this message]
2014-06-05  6:30                 ` Kashyap Gada
2014-06-05  6:34                   ` Burton, Ross
2014-06-05  6:39                     ` Kashyap Gada

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=538E028D.2090200@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=gada.kashyap@gmail.com \
    --cc=ross.burton@intel.com \
    --cc=yocto@yoctoproject.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.