If image contains dbus and ptest is in DISTRO_FEATURES, dbus-ptest package
is installed, regardless of whether ptest-pkgs is in IMAGE_FEATURES. This
issue will increase size for most small images.
This patch fixes this problem.
[YOCTO #5702]
Signed-off-by: Chong Lu chong...@windriver.com
---
The following changes since commit a01af0202558e6ed9d16590b3a8d1dd1b95c0374:
recipes: bump PRs (2014-03-05 17:36:37 +)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib chonglu/dbus
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=chonglu/dbus
Chong Lu
On 6 March 2014 00:06, Saul Wold s...@linux.intel.com wrote:
[YOCTO #5905]
[YOCTO #5906]
[YOCTO #5907]
[YOCTO #5908]
[YOCTO #5909]
[YOCTO #5910]
[YOCTO #5911]
Signed-off-by: Saul Wold s...@linux.intel.com
---
meta/classes/gconf.bbclass | 1 -
1 file changed, 1 deletion(-)
diff --git
On 6 March 2014 08:06, Chong Lu chong...@windriver.com wrote:
+PACKAGES += dbus-ptest
+ALLOW_EMPTY_${PN}-ptest = 1
+RDEPENDS_${PN}-ptest = ${@base_contains('IMAGE_FEATURES', 'ptest-pkgs',
'dbus-test-ptest', 'dbus-test', d)}
Nice idea, but wouldn't a more correct solution be to have
Backport of the master fix that just went in.
The following change since commit 2d6d738d52fa93de4514b65140b1e68cfae7434a:
gnutls: Fixed bug that prevented the rejection of v1 intermediate CA
certificates. (2014-03-05 12:38:29 +)
is available in the git repository at:
Add a Debian patch to fix a load of errors building the documentation
within do_compile e.g.:
| ./x509-api.texi:15: misplaced {
| ./x509-api.texi:15: misplaced }
(From OE-Core master rev: b09a9a5f298596795f17243e5ffcf7dab295a8e6)
Signed-off-by: Paul Eggleton paul.eggle...@linux.intel.com
Add a Debian patch to fix a load of errors building the documentation
within do_compile e.g.:
| ./x509-api.texi:15: misplaced {
| ./x509-api.texi:15: misplaced }
(From OE-Core master rev: b09a9a5f298596795f17243e5ffcf7dab295a8e6)
Signed-off-by: Paul Eggleton paul.eggle...@linux.intel.com
Backport of the master fix that just went in.
The following change since commit 74bcafd4949b3505bff4c38de6e68ad62f0fe5f6:
gnutls: Fixed bug that prevented the rejection of v1 intermediate CA
certificates. (2014-03-05 12:38:40 +)
is available in the git repository at:
Hi Martin,
On Thursday 06 March 2014 02:31:31 Martin Jansa wrote:
can you be more specific about django-nvd3 version required by
error-report-web?
http://git.yoctoproject.org/cgit/cgit.cgi/error-report-web/tree/README
with 0.6.* it was complaining about missing kw_args param in load_chart
The aclocal copy is done as a prefunc so we need to ensure configure.ac
is available before those functions run. The easiest way is inserting
an extra task.
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
diff --git a/meta/recipes-support/js/js_1.7.0+1.8.0rc1.bb
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
diff --git a/meta/recipes-multimedia/gstreamer/gstreamer_0.10.36.bb
b/meta/recipes-multimedia/gstreamer/gstreamer_0.10.36.bb
index 4282f07..99eee81 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer_0.10.36.bb
+++
On Wed, 05 Mar, at 12:02:27PM, Bruce Ashfield wrote:
Please cc' me directly on any kernel-yocto changes, I only noticed this
by chance.
Noted.
On Wed, Mar 5, 2014 at 11:49 AM, Matt Fleming m...@console-pimps.org wrote:
Furthermore, the output of 'git branch' is subject to change and
From: Matt Fleming matt.flem...@intel.com
'git branch' may use ANSI escape codes in its output (to provide colour)
which doesn't play well with commands expecting pure plain text, e.g.
fatal: '^[[31mmaster^[[m' is not a valid branch name.
Use the --no-color option to ensure all branch names
Hi Martin,
I should have been more specific about the versions, sorry.
I've updated the README, it needs django-nvd3 0.1.11 and python-nvd3 0.6.0.
I usually install those on my Ubuntu host using pip.
Regards,
Andreea
-Original Message-
From: Martin Jansa
Currently, opkg/dpkg have their own postinstalls that create a
run-postinsts script which is run at first boot.
This commit prepares the run-postinsts recipe/script to be used by
opkg/dpkg when DISTRO_FEATURES includes package-management.
[YOCTO #5666]
Signed-off-by: Laurentiu Palcu
Just use the run-postinsts recipe for running first boot postinstalls.
[YOCTO #5666]
Signed-off-by: Laurentiu Palcu laurentiu.pa...@intel.com
---
meta/recipes-devtools/dpkg/dpkg.inc | 24 +---
meta/recipes-devtools/opkg/opkg.inc | 28 +---
2 files
This patchset removes the opkg/dpkg postinstalls that were creating their own
run-postinsts script which, sometimes, confused people... Instead, use the
already available run-postinsts recipe in order to create the run-postinsts
init script. It will be used for both 'package-management'/no
On Thu, Mar 06, 2014 at 11:44:54AM +, Proca, Andreea B wrote:
Hi Martin,
I should have been more specific about the versions, sorry.
I've updated the README, it needs django-nvd3 0.1.11 and python-nvd3 0.6.0.
I usually install those on my Ubuntu host using pip.
Thank you, I didn't
On Thu, Mar 6, 2014 at 6:04 AM, Matt Fleming m...@console-pimps.org wrote:
From: Matt Fleming matt.flem...@intel.com
'git branch' may use ANSI escape codes in its output (to provide colour)
which doesn't play well with commands expecting pure plain text, e.g.
fatal: '^[[31mmaster^[[m' is
On Thu, Mar 6, 2014 at 6:02 AM, Matt Fleming m...@console-pimps.org wrote:
On Wed, 05 Mar, at 12:02:27PM, Bruce Ashfield wrote:
Please cc' me directly on any kernel-yocto changes, I only noticed this
by chance.
Noted.
On Wed, Mar 5, 2014 at 11:49 AM, Matt Fleming m...@console-pimps.org
1) Some of the checks made when creating new directories are unnecessary
beacause
the test will fail anyway if os.mkdir() fails, with the appropriate error
message.
Removing this code.
2) Moved the adding to tracked paths for deletion of temporary build directories
and sstate-cache directories
1) Some values should have default values in order for tests like sstate
relocation to be relevant
- SSTATE_DIR needs to have default value
- SSTATE_MIRRORS need to be unset (we need the sstate files to be created)
- TMPDIR needs to be in default location
2) Added conf/auto.conf to list
The following changes since commit c6825ec6e92e20bb64a051d1576f363c16e98d68:
recipes: bump PRs (2014-03-05 17:26:24 +)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/cleanup5
Despite the fact that it's currently specific to the Sharp Zaurus, we
kept this in OE-Core up to now as a potential basis for better handling
of device-specific customisations for a wider range of devices. Whilst
moving device-specific customisations to a more central point is still
a laudable
This is a very old version of Mozilla's Javascript engine, isn't
actually used by anything in OE-Core now that web is gone, and in public
layers outside of OE-Core is apparently only used by mediatomb within
meta-baryon.
Signed-off-by: Paul Eggleton paul.eggle...@linux.intel.com
---
The following changes since commit c6825ec6e92e20bb64a051d1576f363c16e98d68:
recipes: bump PRs (2014-03-05 17:26:24 +)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/features
This more accurately represents what this image and packagegroup are
intended to provide (a more complete command-line environment similar
to what you would find on a traditional Linux system), and avoids
confusion with the similarly named core-image-base and
packagegroup-base.
Fixes [YOCTO
Since tasks were renamed to packagegroups some time ago, this variable
name implies that its usage is necessarily related to them which is not
the case. Rename the variable to more closely represent what it does
(whilst still providing backwards-compatibility with a warning for
PACKAGE_GROUP).
Previously the package-management feature was only fully supported
when inheriting core-image.bbclass, which is not really ideal given that
this is the standard way of adding runtime packaging to an image in
OE-Core.
Part of the fix for [YOCTO #5424].
Signed-off-by: Paul Eggleton
These haven't been used for some time (and DESTDIR was never a BitBake
variable at all).
Signed-off-by: Paul Eggleton paul.eggle...@linux.intel.com
---
meta/conf/documentation.conf | 7 ---
1 file changed, 7 deletions(-)
diff --git a/meta/conf/documentation.conf
From: Belen Barros Pena belen.barros.p...@intel.com
Make sure variables listed in the Glossary section of the reference
manual are listed here. There are still some listed here that aren't in
the manual; this should be fixed in the manual.
Signed-off-by: Belen Barros Pena
From: Tom Zanussi tom.zanu...@intel.com
This updates lttng-ust to 2.4.0, codenamed Époque Opaque, needed
for interoperability with lttng-modules and the 3.14 (dev) kernel.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
meta/recipes-kernel/lttng/lttng-ust_2.4.0.bb | 31
From: Tom Zanussi tom.zanu...@intel.com
The mainline 3.14 commit 'block: Astract out bvec iterator' broke the
lttng-modules tracepoints. Fix them here.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
.../lttng/lttng-modules/bio-bvec-iter.patch| 156 +
This adds lttng 2.4.0, which addresses build failures with
linux-yocto-dev, but still works with 3.10.
Tested with qemux86 and both linux-yocto and linux-yocto-dev.
Note that this disables lttng for arm, due to a problem with
lttng-modules and gcc-4.8.x (this is also a problem for lttng 2.3.x).
From: Tom Zanussi tom.zanu...@intel.com
lttng-modules and gcc-4.8 don't mix, according to the lttng ML
'current_thread_info() not respecting program order with gcc 4.8.x',
so remove it from arm builds.
Without lttng-modules, lttng-tools etc don't make sense either so
exclude them as well.
Don't build the doc examples - we don't need them and in fact they
never successfully built in previous iterations of the lttng-ust
recipe anyway.
Signed-off-by: Tom Zanussi tom.zanu...@linux.intel.com
---
.../lttng-ust/lttng-ust-doc-examples-disable.patch | 18 ++
From: Tom Zanussi tom.zanu...@intel.com
This updates lttng-modules to 2.4.0, codenamed Époque Opaque, needed
for interoperability with the 3.14 (dev) kernel.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
meta/recipes-kernel/lttng/lttng-modules_2.4.0.bb | 34
1
From: Tom Zanussi tom.zanu...@intel.com
This updates lttng-tools to 2.4.0, codenamed Époque Opaque, needed
for interoperability with lttng-modules and the 3.14 (dev) kernel.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
.../lttng/lttng-tools/runtest-2.4.0.patch | 27 ++
Hi,
On Wed, Mar 5, 2014 at 7:11 AM, Andrey Belous abel...@broadcom.com wrote:
Yes I overwriting more , but other variable already with ?= and allow to
override them
I think I am okay with the patch proposed here. i don't see why the
late assignment is missing just for this specific variable
On Thu, 2014-03-06 at 11:09 -0600, Tom Zanussi wrote:
Without lttng-modules, lttng-tools etc don't make sense either so
exclude them as well.
This isn't entirely true; one can quite happily use the ust tracers
without the modules. I've no idea why ust is disabled on aarch64
either.
p.
On Thu, 2014-03-06 at 11:09 -0600, Tom Zanussi wrote:
+# lttng currently blacklists arm with gcc-4.8
+COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips).*-linux'
If the issue at hand here is GCC PR 58854 (which the lttng mailing list
thread seems to suggest it is), can't we just apply the
The bbclass did the following:
do_diffconfig[depends] += virtual/kernel:do_kernel_configme
This clearly introduces a cross-kernel task dependency if the recipe
inheriting this class isn't the preferred provider of virtual/kernel, which is
obviously wrong, but further, will break the build if
Abstract away some names so one can select using EFI_PROVIDER a different
class than grub-efi for populating live images, basically allowing the use
of a different bootloader than grub-efi.
Signed-off-by: Stefan Stanacar stefanx.stana...@intel.com
---
meta/classes/boot-directdisk.bbclass | 7
Hello,
This series adds recipes for gummiboot and a class allowing it to be used
as the boot loader for live/hddimg images.
Without changing EFI_PROVIDER, we have the same behaviour for EFI machines.
Using EFI_PROVIDER = gummiboot an installed image will use gummiboot instead
of grub-efi as it's
Adds a gummiboot class similar to grub-efi class and makes the necessary
changes so it can be used for live/hddimg images as well.
One can set EFI_PROVIDER = gummiboot in local.conf to use gummiboot instead
of grub-efi.
Gummiboot requires some kernel options that are not enabled by default, so
On Thu, 2014-03-06 at 17:56 +, Phil Blundell wrote:
On Thu, 2014-03-06 at 11:09 -0600, Tom Zanussi wrote:
Without lttng-modules, lttng-tools etc don't make sense either so
exclude them as well.
This isn't entirely true; one can quite happily use the ust tracers
without the modules.
On Thu, Mar 6, 2014 at 1:10 PM, Christopher Larson kerg...@gmail.com wrote:
The bbclass did the following:
do_diffconfig[depends] += virtual/kernel:do_kernel_configme
This clearly introduces a cross-kernel task dependency if the recipe
inheriting this class isn't the preferred provider
On Thu, Mar 6, 2014 at 11:40 AM, Bruce Ashfield bruce.ashfi...@gmail.comwrote:
On Thu, Mar 6, 2014 at 1:10 PM, Christopher Larson kerg...@gmail.com
wrote:
+addtask kernel_configme after do_patch
+
linux-yocto.inc already has:
addtask kernel_configme before do_configure after do_patch
On Thu, 2014-03-06 at 18:04 +, Phil Blundell wrote:
On Thu, 2014-03-06 at 11:09 -0600, Tom Zanussi wrote:
+# lttng currently blacklists arm with gcc-4.8
+COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips).*-linux'
If the issue at hand here is GCC PR 58854 (which the lttng mailing
On Thu, Mar 6, 2014 at 1:45 PM, Chris Larson kerg...@gmail.com wrote:
On Thu, Mar 6, 2014 at 11:40 AM, Bruce Ashfield bruce.ashfi...@gmail.com
wrote:
On Thu, Mar 6, 2014 at 1:10 PM, Christopher Larson kerg...@gmail.com
wrote:
+addtask kernel_configme after do_patch
+
linux-yocto.inc
On Wed, 2014-03-05 at 14:39 +0200, Laurentiu Palcu wrote:
Call the new python routines.
[YOCTO #5904]
Signed-off-by: Laurentiu Palcu laurentiu.pa...@intel.com
---
meta/classes/buildhistory.bbclass |9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git
On 3/6/14, 10:15, Stefan Stanacar stefanx.stana...@intel.com wrote:
Abstract away some names so one can select using EFI_PROVIDER a different
class than grub-efi for populating live images, basically allowing the use
of a different bootloader than grub-efi.
Signed-off-by: Stefan Stanacar
On 3/6/14, 10:15, Stefan Stanacar stefanx.stana...@intel.com wrote:
Adds a gummiboot class similar to grub-efi class and makes the necessary
changes so it can be used for live/hddimg images as well.
One can set EFI_PROVIDER = gummiboot in local.conf to use gummiboot
instead of grub-efi.
On 3/6/14, 10:15, Stefan Stanacar stefanx.stana...@intel.com wrote:
gummiboot is is a simple UEFI boot manager (not a boot loader ;-) )
These recipes are imported from meta-intel with these changes:
- drop PR and update configure options
- gummiboot was upgraded to latest version
A couple of
On Tue, Mar 4, 2014 at 1:55 PM, Andrey Belous abel...@broadcom.com wrote:
Hi Phil,
I have prebuild uclibc library that I would like to use, without that change
I cannot force to use my prebuild library
OK so write a uclibc recipe for it and let it provide virtual/libc
and, we can very well
This is my first attempt at doing anything ptest related so probably needs a
detailed check.
About 6 out of 350+ test suites fail, compared to 2 or 3 failing on my desktop.
I doubt we'll be able to get a perfect run out of python3 with all tests passing
but I'm not sure where or how to document
A run-ptest script written in python is added which defines a new TestRunner
subclass which prints test results in the required ptest format and then
executes python's built-in testsuite using this new TestRunner subclass.
The built-in testsuite is included in the python standard library and we
The latest commit in opkg-utils allows packages created by opkg-build to be read
by dpkg-deb again.
Signed-off-by: Paul Barker p...@paulbarker.me.uk
---
meta/recipes-devtools/opkg-utils/opkg-utils_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 5 March 2014 13:45, Paul Barker p...@paulbarker.me.uk wrote:
On 5 March 2014 12:49, Paul Barker p...@paulbarker.me.uk wrote:
On 5 March 2014 09:58, Lu Chong chong...@windriver.com wrote:
In flex 2.5.38, libfl.so was built by libtool.
ipsec-tools shows this problem.
When link libipsec.so
On 03/06/2014 06:04 PM, Burton, Ross wrote:
On 6 March 2014 08:06, Chong Lu chong...@windriver.com wrote:
+PACKAGES += dbus-ptest
+ALLOW_EMPTY_${PN}-ptest = 1
+RDEPENDS_${PN}-ptest = ${@base_contains('IMAGE_FEATURES', 'ptest-pkgs',
'dbus-test-ptest', 'dbus-test', d)}
Nice idea, but wouldn't
This adds lttng 2.4.0, which addresses build failures with
linux-yocto-dev, but still works with 3.10.
Tested with qemux86 and both linux-yocto and linux-yocto-dev.
Note that this disables lttng for arm, due to a problem with
lttng-modules and gcc-4.8.x (this is also a problem for lttng 2.3.x).
From: Tom Zanussi tom.zanu...@intel.com
This updates lttng-modules to 2.4.0, codenamed Époque Opaque, needed
for interoperability with the 3.14 (dev) kernel.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
meta/recipes-kernel/lttng/lttng-modules_2.4.0.bb | 34
1
From: Tom Zanussi tom.zanu...@intel.com
This updates lttng-ust to 2.4.0, codenamed Époque Opaque, needed
for interoperability with lttng-modules and the 3.14 (dev) kernel.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
meta/recipes-kernel/lttng/lttng-ust_2.4.0.bb | 31
From: Tom Zanussi tom.zanu...@intel.com
lttng-modules and gcc-4.8 don't mix, according to the lttng ML
'current_thread_info() not respecting program order with gcc 4.8.x',
so remove it from arm builds.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
Don't build the doc examples - we don't need them and in fact they
never successfully built in previous iterations of the lttng-ust
recipe anyway.
Signed-off-by: Tom Zanussi tom.zanu...@linux.intel.com
---
.../lttng-ust/lttng-ust-doc-examples-disable.patch | 18 ++
From: Tom Zanussi tom.zanu...@intel.com
This updates lttng-tools to 2.4.0, codenamed Époque Opaque, needed
for interoperability with lttng-modules and the 3.14 (dev) kernel.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
.../lttng/lttng-tools/runtest-2.4.0.patch | 27 ++
From: Tom Zanussi tom.zanu...@intel.com
The mainline 3.14 commit 'block: Astract out bvec iterator' broke the
lttng-modules tracepoints. Fix them here.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
.../lttng/lttng-modules/bio-bvec-iter.patch| 156 +
Fix for internal compiler error hit when building lttng-tools_4.2.0:
kernel-consumer.c:324:1: internal compiler error: in gen_movsi, at
config/arm/arm.md:5539
Signed-off-by: Tom Zanussi tom.zanu...@linux.intel.com
---
meta/recipes-devtools/gcc/gcc-4.8.inc | 3 +-
On Thu, Mar 06, 2014 at 09:55:38PM +, Richard Purdie wrote:
On Wed, 2014-03-05 at 14:39 +0200, Laurentiu Palcu wrote:
Call the new python routines.
[YOCTO #5904]
Signed-off-by: Laurentiu Palcu laurentiu.pa...@intel.com
---
meta/classes/buildhistory.bbclass |9 -
From: Sébastien Mennetrier s.mennetr...@innotis.org
gst-omx element can not load due to a missing symbol.
Missing symbol RM_Deinit.
(From OE-Core master rev: 56301698a55bcbab4272b273fd98ce4de84cbfac)
Signed-off-by: Sébastien Mennetrier s.mennetr...@innotis.org
Signed-off-by: Richard Purdie
From: Chen Qi qi.c...@windriver.com
If we build a minimal image with iproute2 installed, the following
error will appear during rootfs.
error: Can't install iproute2-3.10.0-r0.0@i586: no package provides /bin/bash
The problem is that iproute2 has an implicit dependency on 'bash'.
This
From: Ming Liu ming@windriver.com
liblzma5 is really requiring by grub, setting RDEPENDS to xz would pull
unneeded xz binaries into rootfs.
(From OE-Core master rev: 78526905999fa38047ae8f3491127cc03de3e3f6)
Signed-off-by: Ming Liu ming@windriver.com
Signed-off-by: Richard Purdie
The following changes since commit 18f34944696a8098daf33a94bc2f532deb217d0a:
gnutls: fix failure during do_compile (2014-03-06 10:31:57 +)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib robert/dora-next
Benefits:
* The mke2fs -d is more faster than populate-extfs.sh, it will save about 25
seconds for a core-image-sato rootfs from my testing.
* Will fix these bugs:
5901: Error at rootfs time if 'ptest-pkgs' is in IMAGE_FEATURES
5797: populate-extfs.sh: problem with large images
5712:
We will add a -d option which will be used for adding the files from a
given directory to the filesystem, it is similiar to genext2fs, but
genext2fs doesn't fully support ext4.
* We already have the basic operations in debugfs:
- Copy regular file
- Create directory
- Create symlink
-
The do_mknod_internal() is used for creating special file which is
block, character and fifo, most of the code are from debugfs/debugfs.c,
the debugfs/debugfs.c will be modified to use this function.
[YOCTO #4083]
Signed-off-by: Robert Yang liezhi.y...@windriver.com
Reviewed-by: Darren Hart
The do_symlink_internal() is used for creating symlinks, most of the
code are from debugfs/debugfs.c, the debugfs/debugfs.c will be modified
to use this function.
[YOCTO #4083]
Signed-off-by: Robert Yang liezhi.y...@windriver.com
Reviewed-by: Darren Hart dvh...@linux.intel.com
---
Use opendir() and readdir() to read the native directory, then use
lstat() to identify the file type and call the corresponding function to
add the file to the filesystem, call the populate_fs() recursively if it
is a directory.
NOTE: the libext2fs can't create the socket file.
[YOCTO #4083]
Create the inode and save the native inode number when we meet the hard
link (st_nlink 1) at the first time, use ext2fs_link() to link the
name to the target inode number when we meet the same native inode
number again.
This algorithm is referred from the genext2fs.
[YOCTO #4083]
This option is used for adding the files from a given directory (the
root-directory) to the filesystem, it is similiar to genext2fs, but
genext2fs doesn't fully support ext4.
[YOCTO #4083]
Signed-off-by: Robert Yang liezhi.y...@windriver.com
Reviewed-by: Darren Hart dvh...@linux.intel.com
---
Update the manual for the -d option
[YOCTO #4083]
Signed-off-by: Robert Yang liezhi.y...@windriver.com
Reviewed-by: Darren Hart dvh...@linux.intel.com
---
...s.8.in-update-the-manual-for-the-d-option.patch | 43
1 file changed, 43 insertions(+)
create mode 100644
We used populate-extfs.sh which invoked the debugfs to create the image,
now the mke2fs' option -d root-directory can do the same thing, and
which is more faster, for example, the core-imag-sato:
* In the past:
$ time mke2fs -t ext4 rootfs.ext4
real0m0.249s
user0m0.036s
sys 0m0.132s
$
* Use the functions in misc/create_inode.c, and remove the duplicated
code.
* The CREATE_INODE_DEPS in the debugfs/Makefile.in is used for recording
create_inode.o's depends which is from misc/Makefile.in, we have to
recompile create_inode.o because we need it to print more messages when
The do_write_internal() is used for copying file from native fs to
target, most of the code are from debugfs/debugfs.c, the
debugfs/debugfs.c will be modified to use this function.
[YOCTO #4083]
Signed-off-by: Robert Yang liezhi.y...@windriver.com
Reviewed-by: Darren Hart dvh...@linux.intel.com
These patches should be enabled at the same time, so enable them in a
single commit, and thus we can disable it easily.
[YOCTO #4083]
Signed-off-by: Robert Yang liezhi.y...@windriver.com
---
meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.9.bb | 11 +++
1 file changed, 11 insertions(+)
The do_mkdir_internal() is used for making dir on the target fs, most of
the code are from debugfs/debugfs.c, the debugfs/debugfs.c will be
modified to use this function.
[YOCTO #4083]
Signed-off-by: Robert Yang liezhi.y...@windriver.com
Reviewed-by: Darren Hart dvh...@linux.intel.com
---
Set the uid, gid, mode and time for inode.
[YOCTO #4083]
Signed-off-by: Robert Yang liezhi.y...@windriver.com
Reviewed-by: Darren Hart dvh...@linux.intel.com
---
..._inode.c-set-owner-mode-time-for-the-inod.patch | 81
1 file changed, 81 insertions(+)
create mode 100644
Remove it since we don't need it anymore, and there is one inside the
e2fsprogs.
[YOCTO #4083]
Signed-off-by: Robert Yang liezhi.y...@windriver.com
---
.../e2fsprogs/e2fsprogs/populate-extfs.sh | 96
.../recipes-devtools/e2fsprogs/e2fsprogs_1.42.9.bb |2 -
2
On 03/07/2014 03:26 PM, Richard Purdie wrote:
On Wed, 2014-03-05 at 18:08 +0800, Ming Liu wrote:
For multilib builds that rpm is the first package backend, it would be
often desireable to express that a package of compatible architecture
is needed to satisfy a dependency. In most of the cases
89 matches
Mail list logo
