On (15/08/10 23:25), Mike Westerhof wrote:
Frans Meulenbroeks wrote:
...
Anyway, if there are issues because of this action, or if you feel
removal of a recipe was not in accordance with the TSC guidelines, let
me know and I'll repair.
Well, here's the first one,
2010/8/16 Khem Raj raj.k...@gmail.com:
On (15/08/10 23:25), Mike Westerhof wrote:
Frans Meulenbroeks wrote:
...
Anyway, if there are issues because of this action, or if you feel
removal of a recipe was not in accordance with the TSC guidelines, let
me know and I'll repair.
Well, here's
Hi List,
I am new to openembeded.
I read the usermanual of openembeded. I configured my system as given in the
manual. But when I run
$ bitbake -b /home/kousikm/work/oe/openembedded/recipes/linux/
linux_2.6.34.bb
It gives the error:-
/var/lib/python-support/python2.6/bb/COW.py:29:
2010/8/16 Kousik Maiti kousikli...@gmail.com:
Hi List,
I am new to openembeded.
I read the usermanual of openembeded. I configured my system as given in the
manual. But when I run
$ bitbake -b /home/kousikm/work/oe/openembedded/recipes/linux/
linux_2.6.34.bb
Don't use bitbake -b. If you are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You removed the default openssl version (0.9.8) without bumping PR for
recipes using that, so now my autobuilder is quite red due to do_rootfs
failures (among other build errors related to these removals).
I can really see how the quality of OE has
2010/8/16 Koen Kooi k.k...@student.utwente.nl:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You removed the default openssl version (0.9.8) without bumping PR for
recipes using that, so now my autobuilder is quite red due to do_rootfs
failures (among other build errors related to these
2010/8/16 Frans Meulenbroeks fransmeulenbro...@gmail.com:
2010/8/16 Koen Kooi k.k...@student.utwente.nl:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You removed the default openssl version (0.9.8) without bumping PR for
recipes using that, so now my autobuilder is quite red due to
Signed-off-by: Frans Meulenbroeks fransmeulenbro...@gmail.com
---
As we have checksums in recipes for quite a while now, I feel the time has come
to
remove the checksums.ini code from utils.bbclass and to remove the (now empty)
checksums.ini file.
Attached is the patch.
Your feedback is
This makes it possible to specify whether the equivalent of 'rm -rf' or
only this of 'rm -f' is wanted. Due to backward compatibility it
defaults to the recursive variant.
Signed-off-by: Enrico Scholz enrico.sch...@sigma-chemnitz.de
---
lib/oe/path.py |4 ++--
1 files changed, 2
2010/8/16 Koen Kooi k.k...@student.utwente.nl:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16-08-10 11:30, Frans Meulenbroeks wrote:
2010/8/16 Frans Meulenbroeks fransmeulenbro...@gmail.com:
2010/8/16 Koen Kooi k.k...@student.utwente.nl:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I need to reconfigure some packages in my image, therefore I added some
additional packages for configuring.
I assumed, the packages are installed and configured in proper order
while creating an image by bitbake.
But at the time, the package pre- and postinstalls are executed in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16-08-10 13:10, Frans Meulenbroeks wrote:
2010/8/16 Koen Kooi k.k...@student.utwente.nl:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16-08-10 11:30, Frans Meulenbroeks wrote:
2010/8/16 Frans Meulenbroeks fransmeulenbro...@gmail.com:
Hi,
http://wiki.openembedded.org/index.php/Legacy_staging states that
NATIVE_INSTALL_WORKS must be set when there is a non trivial
do_install() function and BBCLASSEXTEND is used.
But
| git grep NATIVE_INSTALL_WORKS conf/ classes/ lib/
shows only one place where this variable is evaluated:
Thanks Frans.
But now I am facing another problem.
bitbake task-base
/var/lib/python-support/python2.6/bb/COW.py:30: DeprecationWarning: the sets
module is deprecated
import os, types, sets
ERROR: no files to build.
NOTE: Parsing finished. 0 cached, 0 parsed, 0 skipped, 0 masked.
NOTE: Cache
2010/8/16 Koen Kooi k.k...@student.utwente.nl:
would be nice if oe would detect those cases and force a rebuild.
That doesn't help if you're using packagemanagement. Now you have
foo_1.0-r0.ipk in the feeds that statically linked to openssl 0.9.8
and foo_1.0-r0.ipk locally that statically
* configure script was unable to find bison and flex utilities. It was giving
error configure: error: Cannot find required program bison. and configure:
error: Cannot find required program flex. Added bison-native and flex-native
in DEPENDS to remove this error.
* Bump PR to r1.
* Ran
On 16/08/10 13:14, Frans Meulenbroeks wrote:
2010/8/16 Koen Kooi k.k...@student.utwente.nl:
would be nice if oe would detect those cases and force a rebuild.
That doesn't help if you're using packagemanagement. Now you have
foo_1.0-r0.ipk in the feeds that statically linked to openssl 0.9.8
Am Montag, den 16.08.2010, 17:18 +0530 schrieb Kousik Maiti:
Thanks Frans.
But now I am facing another problem.
Please open a now thread for each new problem and use a precise and
descriptive subject line.
bitbake task-base
/var/lib/python-support/python2.6/bb/COW.py:30:
Am Montag, den 16.08.2010, 18:16 +0600 schrieb Noor Ahsan:
Nitpicks (I think): 1. add *to*, 2. erro*r*s
* configure script was unable to find bison and flex utilities. It was giving
error configure: error: Cannot find required program bison. and configure:
error: Cannot find required
* converted do_stage to do_install and replaced ${STAGING_BINDIR} with
${D}${bindir}
* and treated the source with oe-stylize.py script
Signed-off-by: Fahad Usman fahad_us...@mentor.com
---
recipes/dcop/dcopidl-native_3.5.8.bb | 29 -
1 files changed, 16
2010/8/16 Fahad Usman fahad_us...@mentor.com:
* converted do_stage to do_install and replaced ${STAGING_BINDIR} with
${D}${bindir}
* and treated the source with oe-stylize.py script
Signed-off-by: Fahad Usman fahad_us...@mentor.com
---
recipes/dcop/dcopidl-native_3.5.8.bb | 29
* Run 'oe-stylize.py' on the recipe and make changes accordingly
Signed-off-by: Noor Ahsan noor_ah...@mentor.com
---
recipes/sdcc/sdcc-native_2.8.0.bb |9 +++--
1 files changed, 3 insertions(+), 6 deletions(-)
diff --git a/recipes/sdcc/sdcc-native_2.8.0.bb
On Sun, Aug 15, 2010 at 04:59:17PM +0200, Frans Meulenbroeks wrote:
As some of you might have noticed I've been cleaning up our
recipes.during the last week or so.
As I had some time at hand this weekend, lots of cleaning has been done.
I did my very best to stay within the guidelines of the
2010/8/16 Marc Olzheim z...@zlo.nu:
On Sun, Aug 15, 2010 at 04:59:17PM +0200, Frans Meulenbroeks wrote:
As some of you might have noticed I've been cleaning up our
recipes.during the last week or so.
As I had some time at hand this weekend, lots of cleaning has been done.
I did my very best
On Mon, Aug 16, 2010 at 4:37 AM, Enrico Scholz
enrico.sch...@sigma-chemnitz.de wrote:
Hi,
http://wiki.openembedded.org/index.php/Legacy_staging states that
NATIVE_INSTALL_WORKS must be set when there is a non trivial
do_install() function and BBCLASSEXTEND is used.
But
| git grep
Hello.
On Fri, 2010-08-13 at 23:55, Stefan Schmidt wrote:
On Tue, 2010-08-10 at 17:44, Simon Busch wrote:
Signed-off-by: Simon Busch morp...@gravedo.de
Acked-by: Stefan Schmidt ste...@datenfreihafen.org
Will apply this with the other lvm patches tomorrow.
Done now. Thanks for getting
On Mon, Aug 16, 2010 at 03:43:10PM +0200, Frans Meulenbroeks wrote:
Hmm, the guidelines do not mention anything about licenses. Thus the
only version you left of coreutils after
82dcd385984ba059b346a0e37fd3e14d536074ad is infected with GPLv3, while
the older (6.0) GPLv2 version works fine
Greetings all,
I've created a 1.10.0 release based upon the current 1.10 branch in BitBake.
Unfortunately, it's nontrivial to list here everything that has been done
since 1.8, as master has been developed for years before stabilizing enough
to be released. See
Hi,
all distributions are now using
preferred-xorg-versions-X11R7.5.inc or
preferred-xorg-versions-live.inc or
no preferred-xorg-versions*.inc at all
So we can remove some older versions not pinned in those 2
to make future maintanance of xorg-* dirs a bit easier.
As this is really easy to
Signed-off-by: Martin Jansa martin.ja...@gmail.com
---
recipes/obsolete/xorg/xorg-data/xbitmaps_1.0.1.bb | 10 ++
.../xorg/xorg-data/xcursor-themes_1.0.1.bb | 11 +++
recipes/xorg-data/xbitmaps_1.0.1.bb| 10 --
Signed-off-by: Martin Jansa martin.ja...@gmail.com
---
recipes/obsolete/xorg/xorg-doc/xorg-docs_1.0.1.bb | 11 +++
recipes/obsolete/xorg/xorg-doc/xorg-docs_1.2.bb| 11 +++
recipes/obsolete/xorg/xorg-doc/xorg-docs_1.4.bb| 13 +
Signed-off-by: Martin Jansa martin.ja...@gmail.com
---
.../xorg-util/files/unbreak_cross_compile.patch| 26 +++
recipes/obsolete/xorg/xorg-util/lndir_1.0.1.bb |7 +
.../obsolete/xorg/xorg-util/makedepend_1.0.1.bb|4 +++
'configure' doesn't seem to include the necessary '../mpi' in the
symlinks that get generated. This hack will make the symlinks that do
get created work.
Signed-off-by: Jason Kridner jkrid...@beagleboard.org
---
recipes/libgcrypt/libgcrypt.inc |6 ++
1 files changed, 6 insertions(+), 0
Am 16.08.2010 15:59, schrieb Stefan Schmidt:
Hello.
On Fri, 2010-08-13 at 23:55, Stefan Schmidt wrote:
On Tue, 2010-08-10 at 17:44, Simon Busch wrote:
Signed-off-by: Simon Busch morp...@gravedo.de
Acked-by: Stefan Schmidt ste...@datenfreihafen.org
Will apply this with the other lvm
Am 14.08.2010 21:26, schrieb Michael 'Mickey' Lauer:
Am Freitag, den 13.08.2010, 23:52 +0200 schrieb Stefan Schmidt:
Hello.
On Tue, 2010-08-10 at 21:29, Simon Busch wrote:
Removing the fix-ecore-fb-initialization patch as it let ecore open the
supplied
touchscreen device twice which
We currently have no palmpre support for x-load. As long as we miss it we use
the config
from the beagleboard machine.
Signed-off-by: Simon Busch morp...@gravedo.de
---
conf/machine/palmpre.conf |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/conf/machine/palmpre.conf
The current git revision for palmpre machine fails to compile. I updated it to
the latest
revision available as u-boot is currently not usable on the palmpre machine at
all.
Signed-off-by: Simon Busch morp...@gravedo.de
---
recipes/u-boot/u-boot_git.bb |2 +-
1 files changed, 1
2010/8/16 Jason Kridner jkrid...@beagleboard.org:
'configure' doesn't seem to include the necessary '../mpi' in the
symlinks that get generated. This hack will make the symlinks that do
get created work.
Signed-off-by: Jason Kridner jkrid...@beagleboard.org
---
Rhoman, thanks for the patch.
One small question: Do we want to keep this recipe at
DEFAULT_PREFERENCE = -1 ??
Frans
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
2010/8/16 Marc Olzheim z...@zlo.nu:
In the case of coreutils, that is 6.0.
GPLv2 is ok here as well. The problem with GPLv3 here is that as soon as
we incorporate some GPLv3 package we need to provide the abilitiy for
customers to rebuild their image (Right to Tinker), which we cannot and
Chris,
Thanks for making the release keep up the good work!
Frans
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Hello.
On Mon, 2010-08-16 at 21:06, Simon Busch wrote:
The sources from Palm for the Palm Pre has beed modified with little
improvements and are
rebased against the latest version from Palm found at
http://opensource.palm.com from time
to time. The modified kernel tree is maintained by the
Hello.
On Mon, 2010-08-16 at 20:55, Simon Busch wrote:
We currently have no palmpre support for x-load. As long as we miss it we use
the config
from the beagleboard machine.
Signed-off-by: Simon Busch morp...@gravedo.de
Acked-by: Stefan Schmidt ste...@datenfreihafen.org
regards
Stefan
2010/8/16 Martin Jansa martin.ja...@gmail.com:
Hi,
all distributions are now using
preferred-xorg-versions-X11R7.5.inc or
preferred-xorg-versions-live.inc or
no preferred-xorg-versions*.inc at all
So we can remove some older versions not pinned in those 2
to make future maintanance of
В сообщении от Понедельник 16 августа 2010 22:59:53 автор Frans Meulenbroeks
написал:
One small question: Do we want to keep this recipe at
DEFAULT_PREFERENCE = -1 ??
Well, we're using 1.0.0 since the day it's been released, and it's a perfect
fit for us, but I know that it _might_ break some
2010/8/16 Roman I Khimov ro...@khimov.ru:
В сообщении от Понедельник 16 августа 2010 22:59:53 автор Frans Meulenbroeks
написал:
One small question: Do we want to keep this recipe at
DEFAULT_PREFERENCE = -1 ??
Well, we're using 1.0.0 since the day it's been released, and it's a perfect
fit
On Mon, Aug 16, 2010 at 12:25 PM, Roman I Khimov ro...@khimov.ru wrote:
В сообщении от Понедельник 16 августа 2010 22:59:53 автор Frans Meulenbroeks
написал:
One small question: Do we want to keep this recipe at
DEFAULT_PREFERENCE = -1 ??
Well, we're using 1.0.0 since the day it's been
On Mon, Aug 16, 2010 at 09:25:51PM +0200, Frans Meulenbroeks wrote:
2010/8/16 Martin Jansa martin.ja...@gmail.com:
Hi,
all distributions are now using
preferred-xorg-versions-X11R7.5.inc or
preferred-xorg-versions-live.inc or
no preferred-xorg-versions*.inc at all
So we can remove
2010/8/16 Martin Jansa martin.ja...@gmail.com:
On Mon, Aug 16, 2010 at 09:25:51PM +0200, Frans Meulenbroeks wrote:
I could not test, as patch 2 is not on patchwork (and retrieving them
from gmail is somewhat tricky)
I'm checking why :/ only clue is
bitb...@jama ~/oe $ git send-email
Currently lots of our patches reside in a directory called files.
Somewhere in the past koen explained me that that is not really proper
(and I agree with them).
files should only be used in case a dir has multiple recipes (say X.bb
and Y.bb) which both use the same patch
If there is only a single
Tested and pushed the patch.
Thanks for your contribution
Next time if you create a new version of a patch, can you please add
v2 to the subject line, and mark the old version as obsolete in
patchwork. (http://patchwork.openembedded.org/project/openembedded/list/)
Best regards, Frans
2010/8/16 Khem Raj raj.k...@gmail.com:
On Mon, Aug 16, 2010 at 12:25 PM, Roman I Khimov ro...@khimov.ru wrote:
В сообщении от Понедельник 16 августа 2010 22:59:53 автор Frans Meulenbroeks
написал:
One small question: Do we want to keep this recipe at
DEFAULT_PREFERENCE = -1 ??
Well, we're
On Mon, Aug 16, 2010 at 10:00:42PM +0200, Frans Meulenbroeks wrote:
Currently lots of our patches reside in a directory called files.
Somewhere in the past koen explained me that that is not really proper
(and I agree with them).
files should only be used in case a dir has multiple recipes
* without legacy staging
* fix QA issue libpython2: non -dev package contains symlink .so: libpython2
path
* use FILESPATHPKG
Signed-off-by: Martin Jansa martin.ja...@gmail.com
---
recipes/python/python-2.6-manifest.inc | 12 +-
.../00-fix-bindir-libdir-for-cross.patch |
Am Montag, den 16.08.2010, 22:04 +0200 schrieb Frans Meulenbroeks:
[…]
Next time if you create a new version of a patch, can you please add
v2 to the subject line, and mark the old version as obsolete in
patchwork. (http://patchwork.openembedded.org/project/openembedded/list/)
I would prefer
It seems that bison was missing this dependency. I'm not 100% certain this
is the right way to add it, so I'm leaving off my signed-off-by in hopes that
someone will ack this who really knows.
---
recipes/bison/bison.inc |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git
On Tue, Aug 10, 2010 at 1:33 AM, Graham Gower graham.go...@gmail.com wrote:
On 08/10/2010 07:24 AM, Andrea Adami wrote:
It seems this doesn't respect ${ONLINE_PACKAGE_MANAGEMENT} == none
I see a spurious /var/lib/opkg in the cpio of initramfs-kexecboot-image.
oe │ 0│Aug 9
---
recipes/flex/flex.inc |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/recipes/flex/flex.inc b/recipes/flex/flex.inc
index 49b26e8..5d3f076 100644
--- a/recipes/flex/flex.inc
+++ b/recipes/flex/flex.inc
@@ -4,7 +4,7 @@ LICENSE = BSD
DEPENDS = gettext
-INC_PR =
Jason Kridner wrote:
---
recipes/flex/flex.inc |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/recipes/flex/flex.inc b/recipes/flex/flex.inc
index 49b26e8..5d3f076 100644
--- a/recipes/flex/flex.inc
+++ b/recipes/flex/flex.inc
@@ -4,7 +4,7 @@ LICENSE = BSD
DEPENDS
On Sun, 15 Aug 2010, Frans Meulenbroeks wrote:
...
opie-freetype modern-freetype-includes.patch
opie-irdaapplet learning-cpp.patch
opie-quicklauncher pro.patch
...
libopie exports.patch
libopie ipaq-2.6-sys-class-backlight-support.patch
libopie ipaq-lcd-rotate-cleanup.patch
libopie
On Mon, Aug 16, 2010 at 7:43 PM, Tom Rini tom_r...@mentor.com wrote:
Jason Kridner wrote:
---
recipes/flex/flex.inc | 4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/recipes/flex/flex.inc b/recipes/flex/flex.inc
index 49b26e8..5d3f076 100644
---
Signed-off-by: Graham Gower graham.go...@gmail.com
---
classes/rootfs_ipk.bbclass |8 ++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/classes/rootfs_ipk.bbclass b/classes/rootfs_ipk.bbclass
index db04fb6..915e3d7 100644
--- a/classes/rootfs_ipk.bbclass
+++
Commit 0dee8eb3458f655ff7e21a898178051c521e5891 broke eglibc on mipsel.
mipsel-oe-linux-gcc -march=mips32 -mabi=32 -shared -static-libgcc -Wl,-O1
-Wl,-z,defs -Wl,-dynamic-linker=/lib/ld.so.1
-B/mnt/oe/tmp/work/mipsel-oe-linux/eglibc-2.11-r11.6+svnr10690/build-mipsel-oe-linux/csu/
On Mon, Aug 16, 2010 at 07:20:23PM -0700, Philip Balister wrote:
At least one other person is seeing this. Mine is on a clean build on a
new F13 machine. Any thoughts?
It's calling ncurses-config from your host which returns also -ltinfo.
Default ncurses in OE (5.4) doesn't have
On (17/08/10 11:47), Graham Gower wrote:
Commit 0dee8eb3458f655ff7e21a898178051c521e5891 broke eglibc on mipsel.
yeah I guess this commit was a temporary fix for arm. May be it should be
localised using arm override.
something like this
FULL_OPTIMIZATION_append_pn-eglibc_arm = -ggdb3
instead
On (17/08/10 07:03), Martin Jansa wrote:
On Mon, Aug 16, 2010 at 07:20:23PM -0700, Philip Balister wrote:
At least one other person is seeing this. Mine is on a clean build on a
new F13 machine. Any thoughts?
It's calling ncurses-config from your host which returns also -ltinfo.
heh you
66 matches
Mail list logo
