On 10/04/2013 04:35 PM, Richard Tollerton wrote:
Suppose the following:
1) foo.do_configure/do_build runs in parallel with
sed-native.do_configure;
2) foo.do_configure/do_build makes use of sed (i.e. inherits autotools);
3) A previously built sed-native already exists in the native sysroot,
Suppose the following:
1) foo.do_configure/do_build runs in parallel with
sed-native.do_configure;
2) foo.do_configure/do_build makes use of sed (i.e. inherits autotools);
3) A previously built sed-native already exists in the native sysroot,
and in the sstate cache.
Then sed-native may be d
Hi Denys,
On Friday 04 October 2013 14:41:16 Denys Dmytriyenko wrote:
> Ping. Is Dylan still alive?
It is yes. I pushed a paule/dylan-next poky-contrib branch the other day
including this fix but haven't had a chance to run it through the autobuilder
yet (been busy with 1.5 work). Will try to g
The uboot-config class uses the UBOOT_CONFIG environment setting to
choose which U-Boot option is intended to build. It is convenient to
allow it to be set from the shell, as supported for MACHINE.
This allow, for example, to trigger a build as:
,
| MACHINE=imx28evk UBOOT_CONFIG=nand bitbake
On 13-10-04 06:46 AM, Richard Purdie wrote:
On Thu, 2013-10-03 at 22:15 -0400, Randy MacLeod wrote:
If I drop x11 from the DF list things are even worse.
I tried to sprinkle these recipes with:
REQUIRED_DISTRO_FEATURES = "opengl"
but just as I thought, that didn't work either.
Did you a
Bruce
Besides the sstate problem RP mentioned your patch worked fine.
On Fri, Oct 4, 2013 at 5:42 AM, Bruce Ashfield
wrote:
> On 13-10-04 03:46 AM, Richard Purdie wrote:
>>
>> On Thu, 2013-10-03 at 20:02 -0400, Bruce Ashfield wrote:
>>>
>>> When building against the sysroot, out of tree modules
Ping. Is Dylan still alive?
On Tue, Sep 24, 2013 at 12:58:20PM -0500, Franklin S. Cooper Jr wrote:
> From: Darren Hart
>
> Fixes [YOCTO #4991]
>
> The kernel image is installed as part of the kernel-image package, but
> the symlink creation/removal via alternatives is being done in
> pkg_post(
On Fri, Oct 4, 2013 at 11:48 AM, Mark Hatle wrote:
> The postinst files were being generated using purely the name of the package,
> this unfortunately meant the run order would be based on the name of the
> package and not the order in which it was installed on the filesystem.
>
> If package A re
D'oh! I checked master for changes to .sh generation but not the .py itself. My
bad.
Change 175f20e2 (relocate_sdk.py: make it work also with python 3) appears to
work fine.
---
Richard Tollerton (512)683-6346
-Richard Purdie wrote: -
To: Richard Tollerton
From: Richard Purdie
Dat
The postinst files were being generated using purely the name of the package,
this unfortunately meant the run order would be based on the name of the
package and not the order in which it was installed on the filesystem.
If package A requires package Z to be fully installed, this causes a problem
When starting a new server we don't want bitbake to connect to an existing
server so ensure BBSERVER is unset.
Signed-off-by: Richard Purdie
---
diff --git a/oe-init-build-env-memres b/oe-init-build-env-memres
index dca819b..79b91b7 100755
--- a/oe-init-build-env-memres
+++ b/oe-init-build-env-me
If BBSERVER is set, we should unset it before proceeding. Its assumed the
user will have unloaded the server from memory should they have wished
to do so.
Signed-off-by: Richard Purdie
---
diff --git a/oe-init-build-env b/oe-init-build-env
index 68af7b5..de9692f 100755
--- a/oe-init-build-env
+++
On 13-10-04 03:46 AM, Richard Purdie wrote:
On Thu, 2013-10-03 at 20:02 -0400, Bruce Ashfield wrote:
When building against the sysroot, out of tree modules can require modpost
and other utilities normally found in the kernel's scripts directory. For
the kernel source in the staging dir, these sc
In case of QEMU machines, a global public DNS is provisioned,
as the network is not configured via DHCP.
Google's public global DNS server 8.8.8.8 is used.
Partial fix for [YOCTO #4587] (qemu machines case).
Signed-off-by: Cristian Iorga
---
meta/recipes-connectivity/connman/connman-conf/qemual
The following changes since commit e7a20238dc73bb449f15feaf0dead51daf796184:
maintainers: Add some maintainers (2013-10-03 10:22:30 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib ciorga/YB4587
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=
On Wed, 2013-10-02 at 18:18 -0500, Richard Tollerton wrote:
> relocate_sdk.py is #!/usr/bin/env python, but is not python3-compatible.
> The PEP 394 alias `python2` is sadly not universally supported, so
> instead of modifying relocate_sdk.py directly, change the `exec` in
> relocate_sdk.sh to use
When these functions change, the package should rebuild but currently it
does not. We need to add the dependencies manually as the dependency
code can't track dynamically created variables.
Signed-off-by: Richard Purdie
---
diff --git a/meta/classes/update-rc.d.bbclass b/meta/classes/update-rc.d.
When these functions change, the package should rebuild but currently it
does not. We need to add the dependencies manually as the dependency
code can't track dynamically created variables.
Signed-off-by: Richard Purdie
---
diff --git a/meta/classes/systemd.bbclass b/meta/classes/systemd.bbclass
The cross-canadian compilers are now build once per architecture but were being
installed into tune specific locations which is incorrect. This adjusts things
so they are make TARGET_ARCH specific. We gain the tune specific parts from the
target sysroot which remains tune specific, the compiler and
MACHINE=X bitbake nativesdk-pixman; MACHINE=Y bitbake nativesdk-pixman
where X is an armv7a machine and Y is not results in pixman rebuilding
due to the neon option. This is incorrect. The ultimate fix will be
not to apply target system overrides in the nativesdk case. Until
we do that we can at l
We only care about the end result in this case, not the specific inputs
that went into determining the gcc option. This change updates the code
to reflect that.
Signed-off-by: Richard Purdie
---
diff --git a/meta/recipes-devtools/gcc/gcc-common.inc
b/meta/recipes-devtools/gcc/gcc-common.inc
inde
If you build nativesdk for machine A, then change to B you will see sstate
manifest warnings for the packagedata files. The stamps are machine
specific and should not be, ditto for native.
This patch copies the populate-sysroot extra stamp entries to avoid
these warnings.
Signed-off-by: Richard P
On Thu, 2013-10-03 at 22:15 -0400, Randy MacLeod wrote:
> If I drop x11 from the DF list things are even worse.
>
> I tried to sprinkle these recipes with:
> REQUIRED_DISTRO_FEATURES = "opengl"
> but just as I thought, that didn't work either.
Did you also inherit the class that implements t
On Fri, Oct 04, 2013 at 09:02:50AM +0100, Burton, Ross wrote:
> On 4 October 2013 03:15, Randy MacLeod wrote:
> > ERROR: Nothing PROVIDES 'virtual/libgl' (but
> > /home/rmacleod/src/distro/oe/oe-core.git/meta/recipes-graphics/clutter/clutter-1.0_1.14.4.bb,
> > /home/rmacleod/src/distro/oe/oe-core.
On 4 October 2013 03:15, Randy MacLeod wrote:
> ERROR: Nothing PROVIDES 'virtual/libgl' (but
> /home/rmacleod/src/distro/oe/oe-core.git/meta/recipes-graphics/clutter/clutter-1.0_1.14.4.bb,
> /home/rmacleod/src/distro/oe/oe-core.git/meta/recipes-graphics/mesa/mesa-demos_8.1.0.bb,
> /home/rmacleod/s
On Thu, 2013-10-03 at 20:02 -0400, Bruce Ashfield wrote:
> When building against the sysroot, out of tree modules can require modpost
> and other utilities normally found in the kernel's scripts directory. For
> the kernel source in the staging dir, these scripts have been removed to
> avoid mixing
26 matches
Mail list logo
