From: Denys Dmytriyenko <denys@ti.com>
To: Craig McQueen <craig.mcqueen@innerrange.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: Error when recompiling linux-ti-staging kernel
Date: Fri, 1 May 2015 16:02:42 -0400 [thread overview]
Message-ID: <20150501200241.GE29290@edge> (raw)
In-Reply-To: <5500469A22567C4BAF673A6E86AFA3A402227F4FAA84@IR-CENTRAL.corp.innerrange.com>
On Thu, Apr 30, 2015 at 10:50:12AM +1000, Craig McQueen wrote:
> I'm using meta-ti with Poky dizzy to build linux-ti-staging 3.14.x for a
> BeagleBone Black based system.
>
> When I do a rebuild of linux-ti-staging, it does most of the compile but
> then fails with an error:
>
> | touch: cannot touch '/home/craigm/yocto/poky/<boardname>/tmp/work/<boardname>-poky-linux-gnueabi/linux-ti-staging/3.14.39-r22b+gitrAUTOINC+ba552b4bc7/image/lib/modules/3.14.39/build': Permission denied
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_compileconfigs (log file is located at /home/craigm/yocto/poky/<boardname>/tmp/work/<boardname>-poky-linux-gnueabi/linux-ti-staging/3.14.39-r22b+gitrAUTOINC+ba552b4bc7/temp/log.do_compileconfigs.4657)
>
> Checking that file, I find that it's a symlink that points to
> /usr/src/kernel, which doesn't exist.
>
> My current work-around is to do "bitbake linux-ti-staging -c clean" then
> rebuild my image. It works fine as long as it's a fresh build. But that
> slows down the development cycle.
>
> Why might this be happening?
Hmm, interesting. Which branch of meta-ti do you use for dizzy?
--
Denys
next prev parent reply other threads:[~2015-05-01 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 0:50 Error when recompiling linux-ti-staging kernel Craig McQueen
2015-05-01 20:02 ` Denys Dmytriyenko [this message]
2015-05-05 0:16 ` Craig McQueen
2015-08-04 6:46 ` Craig McQueen
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=20150501200241.GE29290@edge \
--to=denys@ti.com \
--cc=craig.mcqueen@innerrange.com \
--cc=meta-ti@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.