From: Mark Hatle <mark.hatle@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: Re: BitBake & ClearCase
Date: Tue, 13 Nov 2012 10:28:03 -0600 [thread overview]
Message-ID: <50A27513.5030302@windriver.com> (raw)
In-Reply-To: <1352816917.24487.130.camel@ted>
On 11/13/12 8:28 AM, Richard Purdie wrote:
> On Tue, 2012-11-13 at 12:35 +0100, news@christianvolk.net wrote:
>> Dear bitbake-developer-community,
>>
>> I just stumbled across a problem and knows of no other advice than to
>> write to you here:
>>
>> In my company we have to use bitbake in combination with ClearCase (CC).
>> Bitbake has some problems with the ClearCase-owned files called
>> ?.copyarea.db?.
>> Unfortunately, CC adds such a file to each directory which is under
>> source-control.
>> The file is read-only and so the task do_unpack fails with the
>> following error message:
>>
>> cp: cannot create regular file
>> `/home/[...]/testability-1.0-r0/./testability_src_gen/.copyarea.db':
>> Permission Denied
>
> I'm a little confused about what the real problem is here. cp should be
> able to cope with a file that is marked as read-only. Is this saying the
> target already exists and can't be written to? Or is it unable to read
> from the source? Is the source locked?
Are you attempting to build inside of a ClearCase location? Or are you copying
from a ClearCase location within a recipe.. If it's the later, this is what
Richard is referring to, if it's the former.. It likely won't work well.
ClearCase has a number of issues with it's virtual filesystem that cause
problems during the build.
What we have recommended to our customers using clearcase, is to define an
alternative location for the 'tmp' directory that is outside of the clearcase
filesystem and somewhere local to the machine.
--Mark
> Worst case you can implement a custom "unpack" function for your
> clearcase fetcher like git does and in there, exclude the problematic
> files.
>
> Cheers,
>
> Richard
>
>
>
> _______________________________________________
> bitbake-devel mailing list
> bitbake-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel
>
prev parent reply other threads:[~2012-11-13 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 11:35 BitBake & ClearCase news
2012-11-13 14:28 ` Richard Purdie
2012-11-13 16:28 ` 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=50A27513.5030302@windriver.com \
--to=mark.hatle@windriver.com \
--cc=bitbake-devel@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.