[OE-core] [PATCH 0/2] bitbake.conf: gracefully work with ccache environment variables

2012-05-14 Thread Jason Wessel
The end user of oe-core should be free to turn off ccache, or use an external ccache without impacting the sstate sums. Example of using a different ccache directory via local.conf CCACHE_DIR = /tmp/ccache Example of turning off ccache: export CCACHE_DISABLE = 1 BB_HASHBASE_WHITELIST +=

[OE-core] [PATCH 1/2] bitbake.conf: Move default hash policy initialization before conf file inclusion

2012-05-14 Thread Jason Wessel
result of the binaries produced is always the same. Signed-off-by: Jason Wessel jason.wes...@windriver.com --- meta/conf/bitbake.conf | 10 +- 1 files changed, 5 insertions(+), 5 deletions(-) diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf index dc68690..12bca0e 100644

Re: [OE-core] [PATCH 0/2] bitbake.conf: gracefully work with ccache environment variables

2012-05-14 Thread Jason Wessel
On 05/14/2012 11:09 AM, Jason Wessel wrote: The end user of oe-core should be free to turn off ccache, or use an external ccache without impacting the sstate sums. Example of using a different ccache directory via local.conf CCACHE_DIR = /tmp/ccache Example of turning off ccache

Re: [OE-core] [PATCH 0/2] bitbake.conf: gracefully work with ccache environment variables

2012-05-14 Thread Jason Wessel
On 05/14/2012 12:18 PM, Marko Lindqvist wrote: On 14 May 2012 19:09, Jason Wessel jason.wes...@windriver.com wrote: The end user of oe-core should be free to turn off ccache, or use an external ccache without impacting the sstate sums. ... External cache makes sense for anything being

[OE-core] [PATCH v2 1/1] bitbake.conf: Add CCACHE_DIR to BB_HASHBASE_WHITELIST

2012-05-14 Thread Jason Wessel
The location of the ccache should not affect the sum in the sstate files. The end user should be free to use an external ccache via defining CCACHE_DIR to a new value in local.conf or using the default per package local ccache in the temp directory. Signed-off-by: Jason Wessel jason.wes

Re: [OE-core] [PATCH 0/2] RFC - CCACHE_DIR to not impact sstate

2012-05-14 Thread Jason Wessel
On 05/14/2012 04:33 PM, Khem Raj wrote: On Sun, May 13, 2012 at 7:28 PM, Jason Wessel jason.wes...@windriver.com wrote: I am not exactly sure how to fix this, so I thought I might ask in the form of a working patch. The problem is that I want to use an external CCACHE_DIR on some build

Re: [OE-core] [PATCH 0/2] bitbake.conf: gracefully work with ccache environment variables

2012-05-14 Thread Jason Wessel
On 05/14/2012 05:00 PM, Marko Lindqvist wrote: As you can see from my answer to last part I quote, I'm not against your patch, so don't read first parts of this email with that mindset. They are more generic discussion about ccache caches. No worries. On 14 May 2012 23:58, Jason Wessel

[OE-core] [PATCH 1/2] bitbake/lib/bb/data.py: Allow an exported variable to be excluded from dependency processing

2012-05-13 Thread Jason Wessel
This change is intended to allow an exported variable to not impact the sstate sum in oe-core. Signed-off-by: Jason Wessel jason.wes...@windriver.com --- lib/bb/data.py |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lib/bb/data.py b/lib/bb/data.py index c0636e1

[OE-core] [PATCH 2/2] bitbake.conf: A change to CCACHE_DIR should not change the sstate sum

2012-05-13 Thread Jason Wessel
If the location of the CCACHE_DIR changes it should not impact the sstate sum. This allows a build generated with an external CCACHE_DIR to have the same sstate sum as a build that uses the ccache dir located in the temp build area. Signed-off-by: Jason Wessel jason.wes...@windriver.com

[OE-core] [PATCH 0/2] RFC - CCACHE_DIR to not impact sstate

2012-05-13 Thread Jason Wessel
I am not exactly sure how to fix this, so I thought I might ask in the form of a working patch. The problem is that I want to use an external CCACHE_DIR on some build servers, but use the defaults on others. Ultimately the sstate sums should be the same in either case, but they are not due to

[OE-core] [PATCH] .gitignore: add /bitbake to the ignore list for external distributions

2012-05-09 Thread Jason Wessel
git add file... to include in what will be committed) # # bitbake/ Signed-off-by: Jason Wessel jason.wes...@windriver.com --- .gitignore |1 + 1 file changed, 1 insertion(+) diff --git a/.gitignore b/.gitignore index 04e36c5..366151c 100644 --- a/.gitignore +++ b/.gitignore @@ -1,3

Re: [OE-core] [PATCH] .gitignore: add /bitbake to the ignore list for external distributions

2012-05-09 Thread Jason Wessel
On 05/09/2012 09:21 AM, Phil Blundell wrote: On Wed, 2012-05-09 at 08:46 -0500, Jason Wessel wrote: External distributions based on the oe-core will typically include bitbake in the top level directory. The idea is to make it easy for external distributions to easily assemble a distribution

Re: [OE-core] [PATCH] qemu-native: depend on unfs-server-native

2012-05-03 Thread Jason Wessel
On 05/03/2012 05:39 AM, Koen Kooi wrote: Op 3 mei 2012, om 10:47 heeft Richard Purdie het volgende geschreven: The point of these is to trigger them to build whenever a qemu image is built. This makes a lot of sense in some use cases, it also does not make sense in some other cases and it

[OE-core] [PATCH] terminal.bbclass, oe-buildenv-internal: pass SCREENDIR environment variable

2012-05-03 Thread Jason Wessel
Some versions of the screen utility provided from the host OS vendor write the socket directory to $HOME/.screen. When using a shared home directory across many servers, one sets the SCREENDIR environment variable to avoid collisions in the shared home directory. This results in problems

[OE-core] [PATCH] qemu-native: depend on unfs-server-native

2012-05-02 Thread Jason Wessel
to unfs-server-native. Signed-off-by: Jason Wessel jason.wes...@windriver.com --- meta/conf/machine/include/qemu.inc |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/meta/conf/machine/include/qemu.inc b/meta/conf/machine/include/qemu.inc index 421a149..742b629 100644

Re: [OE-core] [PATCH] qemu-native: depend on unfs-server-native

2012-05-02 Thread Jason Wessel
On 05/02/2012 09:29 AM, Koen Kooi wrote: Op 2 mei 2012, om 16:23 heeft Jason Wessel het volgende geschreven: The user mode NFS server does not get built by default when you are using a purely command line driven development environment without SDK tools. In order to accommodate simple test

[OE-core] [PATCH] runqemu: Fix TAP='TUNSETGROUP: Invalid argument' by falling back to tunctl -u

2012-05-02 Thread Jason Wessel
remains to try and use the groupid first. Signed-off-by: Jason Wessel jason.wes...@windriver.com --- scripts/runqemu-ifup | 20 +--- scripts/runqemu-internal |5 +++-- 2 files changed, 16 insertions(+), 9 deletions(-) diff --git a/scripts/runqemu-ifup b/scripts/runqemu

[OE-core] [PATCH] runqemu: Fix TAP='TUNSETGROUP: Invalid argument' by falling back to tunctl -u

2012-05-02 Thread Jason Wessel
remains to try and use the groupid first. Signed-off-by: Jason Wessel jason.wes...@windriver.com --- scripts/runqemu-ifup | 20 +--- scripts/runqemu-internal |5 +++-- 2 files changed, 16 insertions(+), 9 deletions(-) diff --git a/scripts/runqemu-ifup b/scripts/runqemu

Re: [OE-core] [PATCH] qemu-native: depend on unfs-server-native

2012-05-02 Thread Jason Wessel
On 05/02/2012 09:44 AM, Koen Kooi wrote: Op 2 mei 2012, om 16:33 heeft Jason Wessel het volgende geschreven: On 05/02/2012 09:29 AM, Koen Kooi wrote: Op 2 mei 2012, om 16:23 heeft Jason Wessel het volgende geschreven: The user mode NFS server does not get built by default when you are using

Re: [OE-core] [PATCH] qemu-native: depend on unfs-server-native

2012-05-02 Thread Jason Wessel
On 05/02/2012 04:49 PM, Phil Blundell wrote: On Wed, 2012-05-02 at 16:44 +0200, Koen Kooi wrote: Op 2 mei 2012, om 16:33 heeft Jason Wessel het volgende geschreven: On 05/02/2012 09:29 AM, Koen Kooi wrote: Op 2 mei 2012, om 16:23 heeft Jason Wessel het volgende geschreven: The user mode NFS

Re: [OE-core] [PATCH] Allow user mode NFS server to run without rpcbind / portmap

2011-10-10 Thread Jason Wessel
On 10/10/2011 12:04 AM, Saul Wold wrote: On 10/05/2011 11:43 AM, Jason Wessel wrote: From the 2.6.39 linux kernel and up it is possible to use and nfsroot mount without the need to talk to an RPC info server as long as the port numbers for mountd and nfsd are known in advance. This patch

[OE-core] [PATCH] Allow user mode NFS server to run without rpcbind / portmap

2011-10-05 Thread Jason Wessel
without the need to use rpcbind or portmap services. Signed-off-by: Jason Wessel jason.wes...@windriver.com --- .../023-no-rpc-register.patch | 34 .../unfs-server/unfs-server_2.1+2.2beta47.bb |3 +- scripts/runqemu-export-rootfs

[OE-core] [PATCH] Allow user mode NFS server to run without rpcbind / portmap

2011-10-05 Thread Jason Wessel
without the need to use rpcbind or portmap services. Signed-off-by: Jason Wessel jason.wes...@windriver.com --- .../023-no-rpc-register.patch | 34 .../unfs-server/unfs-server_2.1+2.2beta47.bb |3 +- scripts/runqemu-export-rootfs

<    1   2   3