From: "David Nyström" <david.c.nystrom@gmail.com>
To: "Laurentiu Palcu" <laurentiu.palcu@intel.com>,
"David Nyström" <david.nystrom@enea.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v5 00/53] Rootfs/image generation refactoring (cover letter only)
Date: Tue, 11 Feb 2014 09:56:33 +0100 [thread overview]
Message-ID: <52F9E5C1.3050906@gmail.com> (raw)
In-Reply-To: <20140211085037.GE10078@lpalcu-linux>
On 2014-02-11 09:50, Laurentiu Palcu wrote:
> Hi David,
>
> On Tue, Feb 11, 2014 at 09:42:49AM +0100, David Nyström wrote:
>> File: '/media/sdb5/poky-contrib/meta/lib/oe/image.py', lineno: 158,
>> function: _write_script
>> 0154: self.d.setVarFlag('img_creation_func', 'func', 1)
>> 0155: self.d.setVarFlag('img_creation_func', 'fakeroot', 1)
>> 0156:
>> 0157: with open(script_name, "w+") as script:
>> *** 0158: script.write("%s" % bb.build.shell_trap_code())
>> 0159: script.write("export ROOTFS_SIZE=%d\n" %
>> self._get_rootfs_size())
>> 0160: bb.data.emit_func('img_creation_func', script,
>> self.d)
>> 0161: script.write("img_creation_func\n")
>> 0162:
>> Exception: AttributeError: 'module' object has no attribute
>> 'shell_trap_code'
> I guess you're missing this commit:
>
> bitbake: build.py: create separate function for shell trap creation code
>
> which is already in master.
Thanks,
David
> laurentiu
>
>
>>
>> ERROR: Function failed: do_rootfs
>> ERROR: Logfile of failure stored in: /media/sdb5/bld/tmp/work/qemuppc-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.9994
>> ERROR: Task 6 (/media/sdb5/poky-contrib/meta/recipes-core/images/core-image-minimal.bb,
>> do_rootfs) failed with exit code '1'
>>
>>
>>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2014-02-11 8:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 11:38 [PATCH 00/49] Rootfs/image generation refactoring (cover letter only) Laurentiu Palcu
2014-02-03 11:54 ` Laurentiu Palcu
2014-02-03 14:32 ` David Nyström
2014-02-03 16:47 ` Laurentiu Palcu
2014-02-04 14:08 ` David Nyström
2014-02-04 14:49 ` David Nyström
2014-02-04 15:34 ` Laurentiu Palcu
2014-02-04 15:40 ` David Nyström
2014-02-05 10:07 ` [PATCH v2 00/50] " Laurentiu Palcu
2014-02-05 10:58 ` David Nystrom
2014-02-05 12:09 ` David Nyström
2014-02-05 14:43 ` Laurentiu Palcu
2014-02-05 18:00 ` David Nystrom
2014-02-05 15:05 ` [PATCH v3 00/51] " Laurentiu Palcu
2014-02-10 7:53 ` [PATCH v4 00/52] " Laurentiu Palcu
2014-02-10 12:15 ` [PATCH v5 00/53] " Laurentiu Palcu
2014-02-11 8:42 ` David Nyström
2014-02-11 8:50 ` Laurentiu Palcu
2014-02-11 8:56 ` David Nyström [this message]
2014-02-11 9:36 ` David Nyström
2014-02-11 14:33 ` David Nyström
2014-02-11 14:50 ` David Nyström
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=52F9E5C1.3050906@gmail.com \
--to=david.c.nystrom@gmail.com \
--cc=david.nystrom@enea.com \
--cc=laurentiu.palcu@intel.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