date:20100826

Re: [oe] how to add file to SRC_URI for target only

2010-08-26 Thread Frans Meulenbroeks

2010/8/25 Chris Larson clar...@kergoth.com:
 On Wed, Aug 25, 2010 at 2:04 PM, Frans Meulenbroeks 
 fransmeulenbro...@gmail.com wrote:

 Is it possible to add a file to SRC_URI for target only in a combined
 native/target recipe?

 Of course I know I can fully redefine SRC_URI, but I feel that is less
 desirable.
 The issue is that the target recipe needs an additional patch that the
 native recipe cannot use.

 Or do we need to introduce an _target suffix?

 Guess an intermediate variable also could do the trick.
 E.g.

 PATCH = xx.patch
 PATCH_virtclass-native = 
 SRC_URI = source and files and patches ${PATCH}

 not really ideal either.

 I saw some other places where we need to tweak similarly with DEPENDS
 e.g.
 DEPENDS = x
 DEPENDS_virtclass-natvie = 

 guess here _target could help too.

 Any ideas/comments/patches/... ?


 Something like this should work:
 DEPENDS += $...@['', 'foo']['${BPN}' == '${PN}']}

Wow.
I think it indeed does, but my knowledge of the language is not that
good that I can say for sure.
The construct above also is not too understandable for beginners. I
think in this case I prefer an overrriding _virtclass-native
assignment (or a new-to-be-introduced _target suffix).

Frans

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] how to add file to SRC_URI for target only

2010-08-26 Thread Esben Haabendal

On Wed, Aug 25, 2010 at 11:11 PM, Chris Larson clar...@kergoth.com wrote:

 Something like this should work:
 DEPENDS += $...@['', 'foo']['${BPN}' == '${PN}']}

What is the run-time cost of this, compared to an overrides based approach?

/Esben

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

[oe] [PATCH] [v2] makedevs_1.0.0: got rid of separate native recipe and removed legacy staging (corrected signed-off by line)

2010-08-26 Thread Fahad Usman

* converted do_stage to do_install

* replaced ${STAGING_BINDIR} with ${D}${bindir}

* moved the do_install to non-native recipe

* added BBCLASSEXTEND = native

* added NATIVE_INSTALL_WORKS = 1

* bumped PR

Signed-off-by: Fahad Usman fahad_us...@mentor.com
---
 recipes/makedevs/makedevs-native_1.0.0.bb |   10 --
 recipes/makedevs/makedevs_1.0.0.bb|   10 --
 2 files changed, 8 insertions(+), 12 deletions(-)

diff --git a/recipes/makedevs/makedevs-native_1.0.0.bb 
b/recipes/makedevs/makedevs-native_1.0.0.bb
deleted file mode 100644
index 004a713..000
--- a/recipes/makedevs/makedevs-native_1.0.0.bb
+++ /dev/null
@@ -1,10 +0,0 @@
-SECTION = base
-require makedevs_${PV}.bb
-inherit native
-
-FILESDIR = $...@os.path.dirname(bb.data.getVar('FILE',d,1))}/makedevs-${PV}
-
-do_stage() {
-   install -d ${STAGING_BINDIR}/
-install -m 0755 ${S}/makedevs ${STAGING_BINDIR}/
-}
diff --git a/recipes/makedevs/makedevs_1.0.0.bb 
b/recipes/makedevs/makedevs_1.0.0.bb
index cab1a4c..2b7e84a 100644
--- a/recipes/makedevs/makedevs_1.0.0.bb
+++ b/recipes/makedevs/makedevs_1.0.0.bb
@@ -2,12 +2,11 @@ DESCRIPTION = A tool to make device nodes
 LICENSE = GPL
 SECTION = base
 PRIORITY = required
+PR = r9
 
 SRC_URI = file://makedevs.c
 S = ${WORKDIR}/makedevs-${PV}
 
-PR = r8
-
 inherit update-alternatives
 
 do_configure() {
@@ -18,6 +17,11 @@ do_compile() {
${CC} ${CFLAGS} ${LDFLAGS} -o ${S}/makedevs ${S}/makedevs.c
 }
 
+do_install_virtclass-native() {
+install -d ${D}${bindir}/
+install -m 0755 ${S}/makedevs ${D}${bindir}/
+}
+
 do_install() {
install -d ${D}${base_sbindir}
install -m 0755 ${S}/makedevs ${D}${base_sbindir}/makedevs.makedevs
@@ -28,4 +32,6 @@ ALTERNATIVE_NAME = makedevs
 ALTERNATIVE_LINK = ${base_sbindir}/makedevs
 ALTERNATIVE_PRIORITY = 50
 
+BBCLASSEXTEND = native
 
+NATIVE_INSTALL_WORKS = 1
-- 
1.6.3.3


___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

[oe] How to include shared libraries and header files in a recipe for OPENGL

2010-08-26 Thread Soumya R

Hi All,

  I am working mips Au1300 board. In rfs image I have included 
qt4-embedded-gles for openGL support .

When i run bitbake avn-gles-image i get the following dependency error

../../bb avn-gles-image
NOTE: Handling BitBake files: / (0386/0386) [100 %]
NOTE: Parsing finished. 371 cached, 11 parsed, 4 skipped, 0 masked.
NOTE: Resolving any missing task queue dependencies
NOTE: Runtime target 'qt4-embedded-gles' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['qt4-embedded-gles', 
'virtual/egl']
ERROR: Required build target 'avn-gles-image' has no buildable providers.
Missing or unbuildable dependency chain was: ['avn-gles-image', 
'qt4-embedded-gles', 'virtual/egl']
 
I could not find egl package so I removed that dependency and started building 
but ended up with EGL functionality test failed. Please
find the log below


Which edition of Qt do you want to use ?

Type 'c' if you want to use the Commercial Edition.
Type 'o' if you want to use the Open Source Edition.


Determining system architecture... (Linux:2.6.32-21-generic:i686)
32-bit Intel 80x86 (i386)
'mips' is supported
'i386' is supported
System architecture: 'mips'
Host architecture: 'i386'
Precompiled-headers support enabled.
Separate debug info support disabled.
Symbol visibility control disabled.
Symbolic function binding disabled.

This is the Qt for Embedded Linux Open Source Edition.

You are licensed to use this software under the terms of
the Lesser GNU General Public License (LGPL) versions 2.1.
You are also licensed to use this software under the terms of
the GNU General Public License (GPL) versions 3.

Type '3' to view the GNU General Public License version 3.
Type 'L' to view the Lesser GNU General Public License version 2.1.
Type 'yes' to accept this license offer.
Type 'no' to decline this license offer.

Do you accept the terms of either license? 
floatmath auto-detection... ()
compiling floatmath.cpp
floatmath.cpp:44: warning: unused parameter 'argc'
floatmath.cpp:44: warning: unused parameter 'argv'
linking floatmath
/home/likewise-open/KPIT/soumyar/avnbuild/openembedded/tmp/cross/mipsel/lib/gcc/mipsel-avn-linux/4.2.2/../../../../mipsel-avn-linux/bin/ld:
 warning: libc.so, needed by 
/home/likewise-open/KPIT/soumyar/avnbuild/openembedded/tmp/cross/mipsel/lib/gcc/mipsel-avn-linux/4.2.2/../../../../mipsel-avn-linux/lib/libgcc_s.so,
 not found (try using -rpath or -rpath-link)
floatmath enabled.
mmx auto-detection... ()
compiling mmx.cpp
cc1plus: error: unrecognized command line option -mmmx
make: *** [mmx.o] Error 1
mmx disabled.
3dnow auto-detection... ()
compiling 3dnow.cpp
cc1plus: error: unrecognized command line option -m3dnow
make: *** [3dnow.o] Error 1
3dnow disabled.
sse auto-detection... ()
compiling sse.cpp
cc1plus: error: unrecognized command line option -msse
make: *** [sse.o] Error 1
sse disabled.
sse2 auto-detection... ()
compiling sse2.cpp
cc1plus: error: unrecognized command line option -msse2
make: *** [sse2.o] Error 1
sse2 disabled.
libtiff auto-detection... ()
compiling libtiff.cpp
libtiff.cpp:42:20: error: tiffio.h: No such file or directory
libtiff.cpp:50:6: error: #error Required libtiff not found
libtiff.cpp: In function 'int main(int, char**)':
libtiff.cpp:57: error: 'tdata_t' was not declared in this scope
libtiff.cpp:57: error: expected `;' before 'buffer'
libtiff.cpp:58: error: 'buffer' was not declared in this scope
libtiff.cpp:58: error: '_TIFFfree' was not declared in this scope
libtiff.cpp:62: error: 'TIFFReadRGBAImageOriented' was not declared in this 
scope
make: *** [libtiff.o] Error 1
libtiff disabled.
libmng auto-detection... ()
compiling libmng.cpp
libmng.cpp:42:20: error: libmng.h: No such file or directory
libmng.cpp:50:2: error: #error System libmng version is less than 1.0.9; using 
built-in version instead.
libmng.cpp: In function 'int main(int, char**)':
libmng.cpp:46: error: 'mng_handle' was not declared in this scope
libmng.cpp:46: error: expected `;' before 'hMNG'
libmng.cpp:47: error: 'hMNG' was not declared in this scope
libmng.cpp:47: error: 'mng_cleanup' was not declared in this scope
make: *** [libmng.o] Error 1
libmng disabled.
DB2 auto-detection... ()
compiling db2.cpp
db2.cpp:42:20: error: sqlcli.h: No such file or directory
db2.cpp:43:21: error: sqlcli1.h: No such file or directory
make: *** [db2.o] Error 1
DB2 disabled.
InterBase auto-detection... ()
compiling ibase.cpp
ibase.cpp:42:19: error: ibase.h: No such file or directory
make: *** [ibase.o] Error 1
InterBase disabled.
MySQL (thread-safe) auto-detection... ()
compiling ../mysql/mysql.cpp
../mysql/mysql.cpp:42:19: error: mysql.h: No such file or directory
make: *** [mysql.o] Error 1
MySQL (thread-safe) disabled.
MySQL (thread-unsafe) auto-detection... ()
compiling mysql.cpp
mysql.cpp:42:19: error: mysql.h: No such file or directory
make: *** [mysql.o] Error 1
MySQL (thread-unsafe) disabled.
OCI auto-detection... ()
compiling oci.cpp
oci.cpp:42:17: error: oci.h: No such

Re: [oe] [PATCH v2] upstart: fix sysvinit compat

2010-08-26 Thread Anatoly Shipitsin

On Thu, Aug 26, 2010 at 14:45, Paul Menzel 
paulepan...@users.sourceforge.net wrote:


 I mean, did you write the those rc, rcS and rcS-default scripts
 yourself? (Probably not judging from the copyright in the header.) So
 where did you those from? From another distribution? Are they included
 somewhere?

 I'm get it from sysvinit recipe


 If it is possible, yes!

 Okey


 Just to be clear that a meant the following line.

  +EXTRA_OEMAKE += 'bindir=${base_bindir}' \
  +  'sbindir=${base_sbindir}' \
  +  'usrbindir=${bindir}' \
  +  'usrsbindir=${sbindir}' \
  +  'includedir=${includedir}' \
  +  'mandir=${mandir}'

  Automatically  upstart installed in /usr but for simple and right
  switching with update-alternatives
  it's move to root.

 Sorry, I do not understand. What is »root«? If it is »/« I do not see in
 which line it is used.

 yes to /


  I'm got this additional parameters from sysvinit.

 Are you referring to those two?

  +USE_VT ?= 1
  +SYSVINIT_ENABLED_GETTYS ?= 1

 But why don’t you add them to `recipes/upstart/upstart_0.3.8.bb`. You
 could add them to the inc file then.

 I'm forgot about this. But now i'm try build upstart_0.3.8.bb and this not
buildable.
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] [PATCH v2] upstart: fix sysvinit compat

2010-08-26 Thread Paul Menzel

[Please do not include »« in front of your *latest* answers.]


Am Donnerstag, den 26.08.2010, 16:07 +0600 schrieb Anatoly Shipitsin:
 On Thu, Aug 26, 2010 at 14:45, Paul Menzel 
 paulepan...@users.sourceforge.net wrote:
 
  I mean, did you write the those rc, rcS and rcS-default scripts
  yourself? (Probably not judging from the copyright in the header.) So
  where did you those from? From another distribution? Are they included
  somewhere?
 
  I'm get it from sysvinit recipe

Maybe add a note to the commit message then.

[…]

  Just to be clear that a meant the following line.
 
   +EXTRA_OEMAKE += 'bindir=${base_bindir}' \
   +  'sbindir=${base_sbindir}' \
   +  'usrbindir=${bindir}' \
   +  'usrsbindir=${sbindir}' \
   +  'includedir=${includedir}' \
   +  'mandir=${mandir}'
 
   Automatically  upstart installed in /usr but for simple and right
   switching with update-alternatives
   it's move to root.
 
  Sorry, I do not understand. What is »root«? If it is »/« I do not see in
  which line it is used.
 
  yes to /

Can you give me the line where it is installed to /. Is not always a
subdirectory of / used?

   I'm got this additional parameters from sysvinit.
 
  Are you referring to those two?
 
   +USE_VT ?= 1
   +SYSVINIT_ENABLED_GETTYS ?= 1
 
  But why don’t you add them to `recipes/upstart/upstart_0.3.8.bb`. You
  could add them to the inc file then.

 I'm forgot about this. But now i'm try build upstart_0.3.8.bb and this not
 buildable.

Can you find out if this version is pinned by any distribution in OE?

$ git grep 0\.3\.8

did not return anything for me regarding Upstart as far as I could see.

Maybe send a patch removing 0.3.8 first with »upstart: remove 0.3.8 b/c
not buildable« as the commit summary and the failure in the commit
message. That would be great.


Thanks,

Paul


signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] Patch procedure for dummies

2010-08-26 Thread Hauser, Wolfgang (external)

Thanks from me too, but for me it would be helpful to add the necessary steps 
for people which don't have
snmp access for git and have to send patches through the allowed mail client as 
an attachment.

Regards
Wolfgang
 
-Ursprüngliche Nachricht-
Von: openembedded-devel-boun...@lists.openembedded.org 
[mailto:openembedded-devel-boun...@lists.openembedded.org] Im Auftrag von J. L. 
Gesendet: Mittwoch, 25. August 2010 19:47
An: openembedded-devel@lists.openembedded.org
Betreff: Re: [oe] Patch procedure for dummies

A huge thanks for taking the time AJ keep you the great work, I am
sure your helping tons of people me included!




On Wed, Aug 25, 2010 at 7:43 AM, AJ ONeal coola...@gmail.com wrote:
 Please give me feedback and I'll post this on the wiki.

 A task-oriented guide to creating a patch:



 Let's say you create a new recipe and you'd like to submit it for inclusion
 (and you've already tested that it works, of course).

 1. Now commit with a good strong helpful message

     git add recipes/nodejs/
     git commit # don't use the -m option

 2. The message should look like this

     added recipe for node.js

     * added recipe for node.js (bug # - no nodejs recipe)
     ** patched libev's wscript to not try to execute code
     ** patched node's wscript to not search in '/usr/include'

     Signed-off-by: AJ ONeal coola...@gmail.com

 3. Create your patch

     git format-patch -1 # or however many commits are part of this change

 3++. If you are submitting a second version also add --subject-prefix
 [v2]

     git send-email

 Your patch will be immediately visible on
 http://patchwork.openembedded.org/patch/



 4. Once your patch has been accepted or rejected, create an account and
 update the status to accepted or rejected

 4++. If you get soft-rejected (a lot of feedback), make the changes, submit
 the next version, and update the status of the previous patch to
 superseded

 Appendix: Properly configuring git (using tek...@gmail.com as an example
 user)

     sudo apt-get install git-core git-email
     git config --global user.name Tekkub
     git config --global user.email tek...@gmail.com
     git config --global sendemail.smtpserver smtp.gmail.com
     git config --global sendemail.smtpserverport 587
     git config --global sendemail.smtpencryption tls
     git config --global sendemail.smtpuser tekk...@gmail.com

 ___
 Openembedded-devel mailing list
 Openembedded-devel@lists.openembedded.org
 http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

[oe] stripping qt4-embedded

2010-08-26 Thread Bas van den Berg

Hi,

when building qt4-embedded, you get a lot of stuff by default:
qt4-embedded-examples
qt4-embedded-demos
   libqtwebkite4
  libqt... (many)

I tried changing the recipe to get rid of these, but to no effect. The recipes 
for
qt4 seems to be the most complex of all recipes ;], so no wonder..
Would the EXCLUDE like in the toolchain recipes work for qt4-embedded?
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] Patch procedure for dummies

2010-08-26 Thread Frans Meulenbroeks

2010/8/26 Hauser, Wolfgang (external) wolfgang.hauser.exter...@eads.com:
 Thanks from me too, but for me it would be helpful to add the necessary steps 
 for people which don't have
 snmp access for git and have to send patches through the allowed mail client 
 as an attachment.

Patches should not be set as attachment but inline.
If you do not have snmp access to your email account you have two options:
1. use a different account (e.g. gmail). you can make one especially
for this. Note that the account may differ from the one in signed-off
(although that is inconvenient)
2. just include the patch in the body of your email. Make sure you use
an email client that does not touch the message (turn spaces in tabs,
wrap lines etc etc).
In the past I did this. A good mail client to do so is pine (or alpine)

Frans

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

[oe] llvm cmake error

2010-08-26 Thread Jaap de Jong


Hi All,

I have some strange behavior while building openjdk-6 for ipx4xxbe
Any ideas are welcome!

Jaap

 
$ MACHINE=ixp4xxbe bitbake openjdk-6

//
ERROR: function do_configure failed
ERROR: log data follows
(/media/OpenEmbedded/unstable/tmp/work/armv5teb-angstrom-linux-gnueabi/llvm2.7-2.7-r8/temp/log.do_configure.31516)
| 
/media/OpenEmbedded/unstable/tmp/work/armv5teb-angstrom-linux-gnueabi/llvm2.7-2.7-r8/temp/run.do_configure.31516:
line 625: cmake_do_configure: command not found
NOTE: Task failed: 
/media/OpenEmbedded/unstable/tmp/work/armv5teb-angstrom-linux-gnueabi/llvm2.7-2.7-r8/temp/log.do_configure.31516
ERROR: TaskFailed event exception, aborting
ERROR: Build of 
/media/OpenEmbedded/unstable/org.openembedded.dev/recipes/llvm/llvm2.7_2.7.bb 
do_configure failed
ERROR: Task 488 
(/media/OpenEmbedded/unstable/org.openembedded.dev/recipes/llvm/llvm2.7_2.7.bb, 
do_configure) failed
ERROR: 
'/media/OpenEmbedded/unstable/org.openembedded.dev/recipes/llvm/llvm2.7_2.7.bb' 
failed


___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] Patch procedure for dummies

2010-08-26 Thread Hauser, Wolfgang (external)

In an earlier mail, I was told that it doesn't matter for patchwork if a patch 
is sent as an attachment.

We are pinned on Outlook here and webmailers are filtered out by the proxy, so 
I need to send patches via Outlook.
Easiest way in Outlook is an attachment.

Regards 
Wolfgang Hauser

-Ursprüngliche Nachricht-
Von: openembedded-devel-boun...@lists.openembedded.org 
[mailto:openembedded-devel-boun...@lists.openembedded.org] Im Auftrag von Frans 
Meulenbroeks
Gesendet: Donnerstag, 26. August 2010 13:50
An: openembedded-devel@lists.openembedded.org
Betreff: Re: [oe] Patch procedure for dummies

2010/8/26 Hauser, Wolfgang (external) wolfgang.hauser.exter...@eads.com:
 Thanks from me too, but for me it would be helpful to add the necessary steps 
 for people which don't have
 snmp access for git and have to send patches through the allowed mail client 
 as an attachment.

Patches should not be set as attachment but inline.
If you do not have snmp access to your email account you have two options:
1. use a different account (e.g. gmail). you can make one especially
for this. Note that the account may differ from the one in signed-off
(although that is inconvenient)
2. just include the patch in the body of your email. Make sure you use
an email client that does not touch the message (turn spaces in tabs,
wrap lines etc etc).
In the past I did this. A good mail client to do so is pine (or alpine)

Frans

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] Patch procedure for dummies

2010-08-26 Thread Frans Meulenbroeks

2010/8/26 Hauser, Wolfgang (external) wolfgang.hauser.exter...@eads.com:
 In an earlier mail, I was told that it doesn't matter for patchwork if a 
 patch is sent as an attachment.

 We are pinned on Outlook here and webmailers are filtered out by the proxy, 
 so I need to send patches via Outlook.
 Easiest way in Outlook is an attachment.


I'm not sure what patchwork does, but it could well be that the
mailing list itself filters attachements.
I don't think I have seen attachements on this list (but I may be mistaken).

Frans

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] udev hangs on boot

2010-08-26 Thread Mark Brown

On Wed, Aug 25, 2010 at 11:45:24AM +0100, Dimitris Papastamos wrote:

 The issue has been resolved. Udev was hanging on boot because the kernel
 was compiled without unix domain sockets support.

Hrm, udev probably ought to be complaining more loudly about that one,
and have error handling that doesn't involve hanging.


___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

[oe] remove cdrtools ?

2010-08-26 Thread Frans Meulenbroeks

While browsing through our recipes I found this:
cdrtools/cdrtools-native_2.01.01_alpha77.bb

This was added in 2006 by Raymond Danks, I did some cleaning 1.5 year
ago, Holger moved it to the latest version last march.

When I wanted to attack this device to remove legacy staging, I
suddenly asked myself: why do we have this recipe in the first place?

Facts:
There is no target recipe for it
no one pins it
no recipe depends on it

I can imagine having a cd recording app could be useful, but do we
within oe really want to support and maintain recording apps?
I guess any decent dev system has cdrtools and at least 5 other
recording apps, so I consider this recipe to be out of scope for OE.

My proposal: remove this recipe

Can I have an ack for this (or if you feel this should be kept can you
please explain why this would be useful to keep and would you then
please also convert the recipe from legacy staging (and probably move
to 3.0)?

Frans.

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

[oe] [PATCH1/2] clutter*: Bump revisions to latest stable cleanup

2010-08-26 Thread Andreas Mueller

From bfa206373e1c566068f454160185135dfb55cf6c Mon Sep 17 00:00:00 2001
From: Andreas Mueller schnitzelt...@gmx.de
Date: Thu, 26 Aug 2010 14:29:26 +0200
Subject: [PATCH] clutter*.bb: Bump revisions to latest stable  cleanup
 Tested on gumstix overo:
   clutter: 1.2.12:
 Test result: Build OK / most conformance/interactive tests running
 no fonts displayed (pango related? / suggestions welcome)
   clutter-box2d: 0.10.0_git:
 Test result: Build OK / latest examples running
 Note: Introspection build error was fixed upstream
   clutter-gst: 1.2.0:
 Test result: Build OK
   clutter-gtk: 0.10.6:
 Test result: Build OK
   clutter-gesture 0.0.2_git
 Test result: Build OK


Signed-off-by: Andreas Mueller schnitzelt...@gmx.de
---
 recipes/clutter/clutter-box2d.inc  |   22 ++-
 .../clutter-box2d/example-data-location.patch  |   11 +
 recipes/clutter/clutter-box2d_0.10.0_git.bb|   14 ++
 recipes/clutter/clutter-common.inc |   37 
 .../clutter/clutter-gesture/no-gl-include.patch|   21 ++
 recipes/clutter/clutter-gesture_0.0.2_git.bb   |   17 ++
 recipes/clutter/clutter-gst.inc|   23 ++-
 recipes/clutter/clutter-gst_1.2.0.bb   |9 +
 recipes/clutter/clutter-gtk.inc|   15 +-
 recipes/clutter/clutter-gtk_0.10.6.bb  |   10 +
 recipes/clutter/clutter.inc|   91 +++--
 recipes/clutter/clutter/sample.desktop |9 +
 recipes/clutter/clutter/test-conformance-run   |8 +
 recipes/clutter/clutter_1.2.12.bb  |   27 +++
 recipes/clutter/files/gtk-doc-for-git.make |  213 
 recipes/clutter/files/gtk-doc.make |  173 
 recipes/gnome/libchamplain-gtk_0.2.8.bb|3 +-
 recipes/gnome/libchamplain_0.2.8.bb|3 +-
 recipes/moblin/bickley_git.bb  |4 +-
 recipes/moblin/hornsey_git.bb  |4 +-
 recipes/moblin/nbtk_git.bb |4 +-
 21 files changed, 504 insertions(+), 214 deletions(-)
 create mode 100644 recipes/clutter/clutter-box2d/example-data-location.patch
 create mode 100644 recipes/clutter/clutter-box2d_0.10.0_git.bb
 create mode 100644 recipes/clutter/clutter-common.inc
 create mode 100644 recipes/clutter/clutter-gesture/no-gl-include.patch
 create mode 100644 recipes/clutter/clutter-gesture_0.0.2_git.bb
 create mode 100644 recipes/clutter/clutter-gst_1.2.0.bb
 create mode 100644 recipes/clutter/clutter-gtk_0.10.6.bb
 create mode 100644 recipes/clutter/clutter/sample.desktop
 create mode 100755 recipes/clutter/clutter/test-conformance-run
 create mode 100644 recipes/clutter/clutter_1.2.12.bb
 create mode 100644 recipes/clutter/files/gtk-doc-for-git.make
 delete mode 100644 recipes/clutter/files/gtk-doc.make

diff --git a/recipes/clutter/clutter-box2d.inc 
b/recipes/clutter/clutter-box2d.inc
index 2b39916..a16d62e 100644
--- a/recipes/clutter/clutter-box2d.inc
+++ b/recipes/clutter/clutter-box2d.inc
@@ -2,16 +2,28 @@ DESCRIPTION = Clutter Box2D
 HOMEPAGE = http://www.clutter-project.org/;
 LICENSE = GPLv2
 
-DEPENDS = clutter-1.0
+DEPENDS = clutter
+
+INC_PR = r1
 
 # The main clutter lib is machine specific so we need to be too
 PACKAGE_ARCH = ${MACHINE_ARCH}
 
 inherit autotools pkgconfig gtk-doc
 
-EXTRA_OECONF += --disable-introspection
+require clutter-common.inc
 
-do_install_append () {
-   install -d ${D}${bindir}
-   install ${S}/examples/.libs/blockbox ${D}${bindir}
+do_configure_prepend() {
+   make_all_execs_installable
 }
+
+# clutter-box2d-examples 
+PACKAGES =+ ${PN}-examples
+FILES_${PN}-examples = ${bindir}/* ${datadir}/clutter-box2d-examples
+
+do_install() {
+   autotools_do_install
+   install -m 755 -d ${D}${datadir}/clutter-box2d-examples
+   install -m 0755 ${S}/examples/redhand.png 
${D}${datadir}/clutter-box2d-examples
+}
+
diff --git a/recipes/clutter/clutter-box2d/example-data-location.patch 
b/recipes/clutter/clutter-box2d/example-data-location.patch
new file mode 100644
index 000..3aaab54
--- /dev/null
+++ b/recipes/clutter/clutter-box2d/example-data-location.patch
@@ -0,0 +1,11 @@
+--- a/examples/blockbox.h.old  2010-07-20 15:05:30.0 +0200
 b/examples/blockbox.h  2010-08-23 18:20:03.0 +0200
+@@ -8,7 +8,7 @@
+ #include scenes.h
+ #include util.h
+ 
+-#define ASSETS_DIR ./
++#define ASSETS_DIR /usr/share/clutter-box2d-examples/
+ extern gboolean simulating;
+ 
+ #endif
diff --git a/recipes/clutter/clutter-box2d_0.10.0_git.bb 
b/recipes/clutter/clutter-box2d_0.10.0_git.bb
new file mode 100644
index 000..a7f348e
--- /dev/null
+++ b/recipes/clutter/clutter-box2d_0.10.0_git.bb
@@ -0,0 +1,14 @@
+require clutter-box2d.inc
+
+SRCREV = 4e72b9c135a9439b82d801c62422531db611f98b
+
+PR = ${INC_PR}.0
+PR_append = +git${SRCREV}
+
+SRC_URI =

[oe] [PATCH2/2] clutter*: Bump revisions to latest stable cleanup

2010-08-26 Thread Andreas Mueller

From bfce18ac13b6fe40a26aec110c26441f9350ed28 Mon Sep 17 00:00:00 2001
From: Andreas Mueller schnitzelt...@gmx.de
Date: Thu, 26 Aug 2010 14:38:30 +0200
Subject: [PATCH] clutter*: Remove obsolete recipes / files


Signed-off-by: Andreas Mueller schnitzelt...@gmx.de
---
 recipes/clutter/clutter-0.9_git.bb |   23 -
 recipes/clutter/clutter-1.0_1.0.10.bb  |   22 
 recipes/clutter/clutter-box2d/introspection.diff   |   31 --
 recipes/clutter/clutter-box2d_0.10.0.bb|9 --
 recipes/clutter/clutter-cairo.inc  |   11 --
 .../clutter/clutter-cairo/enable_examples.patch|   28 --
 recipes/clutter/clutter-cairo_svn.bb   |   11 --
 recipes/clutter/clutter-fpu.inc|6 -
 recipes/clutter/clutter-glx_svn.bb |   10 --
 recipes/clutter/clutter-gst-0.9_git.bb |   13 ---
 recipes/clutter/clutter-gst/autofoo-0.4.patch  |   15 ---
 recipes/clutter/clutter-gst/autofoo.patch  |   25 -
 recipes/clutter/clutter-gst_0.4svn.bb  |9 --
 recipes/clutter/clutter-gst_svn.bb |9 --
 recipes/clutter/clutter-gtk-0.6_git.bb |   10 --
 recipes/clutter/clutter-gtk-0.8_git.bb |   10 --
 recipes/clutter/clutter/enable-tests-r2990.patch   |   50 --
 recipes/clutter/clutter/enable_tests-0.4.patch |   52 --
 recipes/clutter/clutter/enable_tests-0.6.patch |   40 
 recipes/clutter/clutter/enable_tests.patch |   48 -
 recipes/clutter/clutter_0.4svn.bb  |   15 ---
 recipes/clutter/clutter_0.6svn.bb  |   10 --
 recipes/clutter/clutter_0.8+git.bb |   15 ---
 recipes/clutter/clutter_svn.bb |   15 ---
 ...st-videosink-guard-GL-calls-with-ifdef-CL.patch |  102 
 recipes/clutter/files/enable_tests.patch   |   32 --
 26 files changed, 0 insertions(+), 621 deletions(-)
 delete mode 100644 recipes/clutter/clutter-0.9_git.bb
 delete mode 100644 recipes/clutter/clutter-1.0_1.0.10.bb
 delete mode 100644 recipes/clutter/clutter-box2d/introspection.diff
 delete mode 100644 recipes/clutter/clutter-box2d_0.10.0.bb
 delete mode 100644 recipes/clutter/clutter-cairo.inc
 delete mode 100644 recipes/clutter/clutter-cairo/enable_examples.patch
 delete mode 100644 recipes/clutter/clutter-cairo_svn.bb
 delete mode 100644 recipes/clutter/clutter-fpu.inc
 delete mode 100644 recipes/clutter/clutter-glx_svn.bb
 delete mode 100644 recipes/clutter/clutter-gst-0.9_git.bb
 delete mode 100644 recipes/clutter/clutter-gst/autofoo-0.4.patch
 delete mode 100644 recipes/clutter/clutter-gst/autofoo.patch
 delete mode 100644 recipes/clutter/clutter-gst_0.4svn.bb
 delete mode 100644 recipes/clutter/clutter-gst_svn.bb
 delete mode 100644 recipes/clutter/clutter-gtk-0.6_git.bb
 delete mode 100644 recipes/clutter/clutter-gtk-0.8_git.bb
 delete mode 100644 recipes/clutter/clutter/enable-tests-r2990.patch
 delete mode 100644 recipes/clutter/clutter/enable_tests-0.4.patch
 delete mode 100644 recipes/clutter/clutter/enable_tests-0.6.patch
 delete mode 100644 recipes/clutter/clutter/enable_tests.patch
 delete mode 100644 recipes/clutter/clutter_0.4svn.bb
 delete mode 100644 recipes/clutter/clutter_0.6svn.bb
 delete mode 100644 recipes/clutter/clutter_0.8+git.bb
 delete mode 100644 recipes/clutter/clutter_svn.bb
 delete mode 100644 
recipes/clutter/files/0001-clutter-gst-videosink-guard-GL-calls-with-ifdef-CL.patch
 delete mode 100644 recipes/clutter/files/enable_tests.patch

diff --git a/recipes/clutter/clutter-0.9_git.bb 
b/recipes/clutter/clutter-0.9_git.bb
deleted file mode 100644
index 5bbd8a8..000
--- a/recipes/clutter/clutter-0.9_git.bb
+++ /dev/null
@@ -1,23 +0,0 @@
-require clutter.inc
-
-SRCREV = 13e055a351f83c56b895b131566a6e842d24ed2a
-
-PV = 1.1.0
-PR = ${INC_PR}.0
-PR_append = +git${SRCREV}
-
-SRC_URI = git://git.clutter-project.org/clutter.git;protocol=git \
-   file://enable_tests.patch 
-S = ${WORKDIR}/git
-
-BASE_CONF += --disable-introspection
-
-PARALLEL_MAKE = 
-
-do_compile_prepend() {
-   for i in $(find ${S} -name Makefile) ; do
-   sed -i -e s:-Werror::g $i
-   done
-( cd clutter/cogl/gles ; for i in *.glsl ; do sh stringify.sh -h $i ; done 
)
-}
-
diff --git a/recipes/clutter/clutter-1.0_1.0.10.bb 
b/recipes/clutter/clutter-1.0_1.0.10.bb
deleted file mode 100644
index 93fb893..000
--- a/recipes/clutter/clutter-1.0_1.0.10.bb
+++ /dev/null
@@ -1,22 +0,0 @@
-require clutter.inc
-
-PR = ${INC_PR}.0
-
-SRC_URI = 
http://source.clutter-project.org/sources/clutter/1.0/clutter-${PV}.tar.bz2 \
-
-SRC_URI[md5sum] = bf48e85291cba33f3f149f4eefe759f0
-SRC_URI[sha256sum] = 
6fb98dc4d16a3a98be734cf0a6cc4f8d8179800603c3e41011c414eeaf1f456b
-
-S = ${WORKDIR}/clutter-${PV}
-
-BASE_CONF += --disable-introspection
-
-PARALLEL_MAKE = 
-
-do_compile_prepend() {
-   for i in $(find ${S} -name

Re: [oe] stripping qt4-embedded

2010-08-26 Thread Soumya R

Hi,
  Change the QT_CONFIG_FLAGS to -nomake examples -nomake demos in the recipe.

Hope it helps :)

From: openembedded-devel-boun...@lists.openembedded.org 
[openembedded-devel-boun...@lists.openembedded.org] On Behalf Of Bas van den 
Berg [bb...@mail.altenpts.nl]
Sent: Thursday, August 26, 2010 4:48 PM
To: openembedded-devel@lists.openembedded.org
Subject: [oe] stripping qt4-embedded

Hi,

when building qt4-embedded, you get a lot of stuff by default:
qt4-embedded-examples
qt4-embedded-demos
   libqtwebkite4
  libqt... (many)

I tried changing the recipe to get rid of these, but to no effect. The recipes 
for
qt4 seems to be the most complex of all recipes ;], so no wonder..
Would the EXCLUDE like in the toolchain recipes work for qt4-embedded?
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] how to add file to SRC_URI for target only

2010-08-26 Thread Chris Larson

On Thu, Aug 26, 2010 at 1:11 AM, Esben Haabendal
esbenhaaben...@gmail.comwrote:

 On Wed, Aug 25, 2010 at 11:11 PM, Chris Larson clar...@kergoth.com
 wrote:

  Something like this should work:
  DEPENDS += $...@['', 'foo']['${BPN}' == '${PN}']}

 What is the run-time cost of this, compared to an overrides based approach?


In order to *implement* the override, you'd end up having to do this
comparison, or something similar, in an anonymous python function or a
snippet like this in overrides, so I wouldn't worry much about the
particular implementation :)
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] how to add file to SRC_URI for target only

2010-08-26 Thread Chris Larson

On Wed, Aug 25, 2010 at 11:14 PM, Frans Meulenbroeks 
fransmeulenbro...@gmail.com wrote:

 2010/8/25 Chris Larson clar...@kergoth.com:
  On Wed, Aug 25, 2010 at 2:04 PM, Frans Meulenbroeks 
  fransmeulenbro...@gmail.com wrote:
 
  Is it possible to add a file to SRC_URI for target only in a combined
  native/target recipe?
 
  Of course I know I can fully redefine SRC_URI, but I feel that is less
  desirable.
  The issue is that the target recipe needs an additional patch that the
  native recipe cannot use.
 
  Or do we need to introduce an _target suffix?
 
  Guess an intermediate variable also could do the trick.
  E.g.
 
  PATCH = xx.patch
  PATCH_virtclass-native = 
  SRC_URI = source and files and patches ${PATCH}
 
  not really ideal either.
 
  I saw some other places where we need to tweak similarly with DEPENDS
  e.g.
  DEPENDS = x
  DEPENDS_virtclass-natvie = 
 
  guess here _target could help too.
 
  Any ideas/comments/patches/... ?
 
 
  Something like this should work:
  DEPENDS += $...@['', 'foo']['${BPN}' == '${PN}']}

 Wow.
 I think it indeed does, but my knowledge of the language is not that
 good that I can say for sure.
 The construct above also is not too understandable for beginners. I
 think in this case I prefer an overrriding _virtclass-native
 assignment (or a new-to-be-introduced _target suffix).


Okay, how about..

OVERRIDES =. $...@['', 'target:']['${BPN}' == '${PN}']}

:)
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

[oe] [PATCH] minimal.conf: added ivp4 and ipv6 as distro features

2010-08-26 Thread Frans Meulenbroeks

minimal.conf has nfs as distro feature but not ip4 or ipv6.
This makes that busybox does not generate networking applets

Signed-off-by: Frans Meulenbroeks fransmeulenbro...@gmail.com
---
 conf/distro/minimal.conf |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/conf/distro/minimal.conf b/conf/distro/minimal.conf
index d0d2341..7216976 100644
--- a/conf/distro/minimal.conf
+++ b/conf/distro/minimal.conf
@@ -24,7 +24,7 @@ DISTRO_CHECK := $...@bb.data.getvar('DISTRO_VERSION',d,1) or 
bb.fatal('Remove thi
 # Use bluetooth 4.0
 DISTRO_BLUETOOTH_MANAGER = bluez4
 # We want images supporting the following features (for task-base)
-DISTRO_FEATURES = nfs smbfs wifi ppp alsa ext2 vfat pcmcia usbgadget usbhost 
pci
+DISTRO_FEATURES = ipv4 ipv6 nfs smbfs wifi ppp alsa ext2 vfat pcmcia 
usbgadget usbhost pci
 # Following features are for ARM and E500 based machines
 DISTRO_FEATURES += eabi
 
-- 
1.7.0.4


___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] remove cdrtools ?

2010-08-26 Thread Tom Rini


Frans Meulenbroeks wrote:

While browsing through our recipes I found this:
cdrtools/cdrtools-native_2.01.01_alpha77.bb

This was added in 2006 by Raymond Danks, I did some cleaning 1.5 year
ago, Holger moved it to the latest version last march.

When I wanted to attack this device to remove legacy staging, I
suddenly asked myself: why do we have this recipe in the first place?


It's needed for making ISO images of which I thought we used to support 
(boot CDs for x86 boards for example).


--
Tom Rini
Mentor Graphics Corporation

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] remove cdrtools ?

2010-08-26 Thread Tom Rini


Tom Rini wrote:

Frans Meulenbroeks wrote:

While browsing through our recipes I found this:
cdrtools/cdrtools-native_2.01.01_alpha77.bb

This was added in 2006 by Raymond Danks, I did some cleaning 1.5 year
ago, Holger moved it to the latest version last march.

When I wanted to attack this device to remove legacy staging, I
suddenly asked myself: why do we have this recipe in the first place?


It's needed for making ISO images of which I thought we used to support 
(boot CDs for x86 boards for example).


See bootimg.bbclass

--
Tom Rini
Mentor Graphics Corporation

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

[oe] Question on apr on what it said during build

2010-08-26 Thread J. L.

I am building a image and had apr error out while building so I did a
-c clean and rebuilt it which it did fine but, I saw something I had
not noticed before and would like to know if its something to worry
about and if its not what does it mean. The message is below:

NOTE: Running task 749 of 759 (ID: 13,
/home/vdubhack/overo-oe/org.openembedded.dev/recipes/apr/apr_1.3.5.bb,
do_package)
NOTE: the following files were installed but not shipped in any package:
NOTE:   /usr/lib/apr.exp
NOTE:   /usr/share/build-1/mkdir.sh
NOTE:   /usr/share/build-1/apr_rules.mk
NOTE:   /usr/share/build-1/make_var_export.awk
NOTE:   /usr/share/build-1/make_exports.awk


thanks for your help

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

[oe] packages

2010-08-26 Thread C Michael Sundius

I'm trying to understand how package feeds work. From the documentation it
seems
that you can use a package feed to install prebuilt packages onto a running
taget.
but what I'd like to do is to have OE look to see if a pre built package
exists before it
goes and builds one. Sort of like a packaged staging, but distributed, so
anyone could
pick up the package it needs from a single server, rather than having to
build it first
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] remove cdrtools ?

2010-08-26 Thread Frans Meulenbroeks

2010/8/26 Tom Rini tom_r...@mentor.com:
 Tom Rini wrote:

 Frans Meulenbroeks wrote:

 While browsing through our recipes I found this:
 cdrtools/cdrtools-native_2.01.01_alpha77.bb

 This was added in 2006 by Raymond Danks, I did some cleaning 1.5 year
 ago, Holger moved it to the latest version last march.

 When I wanted to attack this device to remove legacy staging, I
 suddenly asked myself: why do we have this recipe in the first place?

 It's needed for making ISO images of which I thought we used to support
 (boot CDs for x86 boards for example).

 See bootimg.bbclass

Ah, ok, didn't know that.
Actually it seems that bootimg.bbclass is not used, and a quick search
didn't show up a way to use it, but its existence is good enough to
keep cdrtools.
I'll see if I can update it.

Frans

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

[oe] hildon-lgpl in nonworking but appears in DEPENDS in recipes

2010-08-26 Thread Khem Raj

Hi,

hildon was moved to nonworking recipes but there are recipes which
DEPEND on this.

gpe-mini-browser/gpe-mini-browser-hildon_0.16.bb:DEPENDS  =
osb-nrcit libosso hildon-lgpl hildon-fm libgpewidget
gpe-mini-browser/gpe-mini-browser-hildon_0.15.bb:DEPENDS  =
osb-nrcit libosso hildon-lgpl hildon-fm libgpewidget
gpe-mini-browser/gpe-mini-browser-hildon_0.17.bb:DEPENDS  =
osb-nrcit libosso hildon-lgpl hildon-fm libgpewidget
libgpepimc/libgpepimc-hildon_0.5.bb:DEPENDS = libgpewidget-hildon
gtk+ sqlite hildon-lgpl
maemo/hildon-status-bar_0.8.11-1.bb:DEPENDS = hildon-lgpl libosso hildon-libs
maemo/hildon-control-panel_0.9.1-1.2.bb:DEPENDS = hildon-lgpl
hildon-base-lib osso-af-settings libosso hildon-libs osso-af-settings
libosso-help
maemo/libosso-help_1.0.01.bb:DEPENDS =  libosso hildon-lgpl
hildon-base-lib hildon-libs
maemo/osso-application-installer_1.0.03-1.bb:DEPENDS = hildon-lgpl
hildon-base-lib libosso hildon-libs hildon-control-panel
shared-mime-info
tasks/task-maemo.bb:hildon-lgpl

I am tempted to move them to nonworking as well. opinions ?

Thanks
-Khem

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] hildon-lgpl in nonworking but appears in DEPENDS in recipes

2010-08-26 Thread Frans Meulenbroeks

2010/8/26 Khem Raj raj.k...@gmail.com:
 Hi,

 hildon was moved to nonworking recipes but there are recipes which
 DEPEND on this.

 gpe-mini-browser/gpe-mini-browser-hildon_0.16.bb:DEPENDS      =
 osb-nrcit libosso hildon-lgpl hildon-fm libgpewidget
 gpe-mini-browser/gpe-mini-browser-hildon_0.15.bb:DEPENDS      =
 osb-nrcit libosso hildon-lgpl hildon-fm libgpewidget
 gpe-mini-browser/gpe-mini-browser-hildon_0.17.bb:DEPENDS      =
 osb-nrcit libosso hildon-lgpl hildon-fm libgpewidget
 libgpepimc/libgpepimc-hildon_0.5.bb:DEPENDS     = libgpewidget-hildon
 gtk+ sqlite hildon-lgpl
 maemo/hildon-status-bar_0.8.11-1.bb:DEPENDS = hildon-lgpl libosso 
 hildon-libs
 maemo/hildon-control-panel_0.9.1-1.2.bb:DEPENDS = hildon-lgpl
 hildon-base-lib osso-af-settings libosso hildon-libs osso-af-settings
 libosso-help
 maemo/libosso-help_1.0.01.bb:DEPENDS =  libosso hildon-lgpl
 hildon-base-lib hildon-libs
 maemo/osso-application-installer_1.0.03-1.bb:DEPENDS = hildon-lgpl
 hildon-base-lib libosso hildon-libs hildon-control-panel
 shared-mime-info
 tasks/task-maemo.bb:    hildon-lgpl

 I am tempted to move them to nonworking as well. opinions ?

I agree that it is pointless to keep them if they do not build so
moving them to nonworking is imho quite logical and therefore has my
blessing.

However, while you're at it there is more to be moved as there are
recipes which depend on the ones you propose to move:
dependencies on libgpepimc-hildon
gpe-todo/gpe-todo-hildon_0.54.bb:DEPENDS = libgpewidget-hildon
libgpepimc-hildon libtododb sdk-default-icons libosso
gpe-todo/gpe-todo-hildon_0.55.bb:DEPENDS = libgpewidget-hildon
libgpepimc-hildon libtododb sdk-default-icons libosso
:
dependencies on libosso-help:
maemo-mapper/maemo-mapper_svn.bb:DEPENDS = gdbm libconic sqlite3 gtk+
libhildonfm libosso osso-ic-oss libosso-help gnome-vfs dbus
bluez-libs
maemo/hildon-control-panel_0.9.1-1.2.bb:DEPENDS = hildon-lgpl
hildon-base-lib osso-af-settings libosso hildon-libs osso-af-settings
libosso-help

I haven't checked for the non-lib recipes, might be some additonal deps too.

Frans

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] testing branch 2010-08-23

2010-08-26 Thread Cliff Brake

On Thu, Aug 26, 2010 at 3:50 PM, Gary Thomas g...@mlbassoc.com wrote:
 On 08/23/2010 05:49 PM, Cliff Brake wrote:

 Hello,

 As detailed in the following page, we are trying to get a testing
 branch going where we try to verify OE builds for a number of
 combinations of distro/machine/target/

 http://wiki.openembedded.net/index.php/Testing

 I have branched dev.oe.org to the testing-testing branch, and have
 verified it builds the following.

 beagleboard     angstrom-2008.1
 beagleboard-linuxtag2010-demo-image
        Ubuntu 10.04 64-bit     User:Cbrake
 beagleboard     angstrom-2008.1         console-image   Ubuntu 10.04
 64-bit     User:Cbrake

 To be clear, a line with an entry in the 'last tested' column indicates a
 successful build of that combination?

Yes, that is my current idea.  I changed the name of the column to
last successful build to be a little more clear.

Thanks,
Cliff

-- 
=
http://bec-systems.com

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

[oe] [PATCH] ncurses-5.7 : fix sdk build

2010-08-26 Thread Eric Bénard

ENABLE_WIDEC should also be false when building sdk
like when building native (tested on ubuntu server 9.10)

Signed-off-by: Eric Bénard e...@eukrea.com
---
 recipes/ncurses/ncurses_5.7.bb |6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/recipes/ncurses/ncurses_5.7.bb b/recipes/ncurses/ncurses_5.7.bb
index 57374ec..29c1674 100644
--- a/recipes/ncurses/ncurses_5.7.bb
+++ b/recipes/ncurses/ncurses_5.7.bb
@@ -4,7 +4,7 @@ LICENSE = MIT
 SECTION = libs
 PATCHDATE = 20100501
 PKGV = ${PV}+${PATCHDATE}
-PR = r11
+PR = r12
 
 DEPENDS = ncurses-native unifdef-native
 DEPENDS_virtclass-native = unifdef-native
@@ -32,7 +32,7 @@ EXTRA_AUTORECONF = -I m4
 ENABLE_WIDEC = true
 # Build breaks on Ubuntu else :(
 ENABLE_WIDEC_virtclass-native = false
-
+ENABLE_WIDEC_virtclass-nativesdk = false
 
 # Override the function from the autotools class; ncurses requires a
 # patched autoconf213 to generate the configure script. This autoconf
@@ -170,7 +170,7 @@ pkg_prerm_ncurses-tools () {
 fi
 }
 
-BBCLASSEXTEND = native sdk
+BBCLASSEXTEND = native nativesdk
 
 PACKAGES =  \
   ncurses-dbg \
-- 
1.6.3.3


___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

[oe] [PATCH] postgresql-8.1.8 : fix configure

2010-08-26 Thread Eric Bénard

without this patch, using angstrom 2010.x on armv6 I actually get :
| checking alignment of short... configure: error:
   cannot compute alignment of short, 77
| ERROR: Function do_configure failed
NOTE: package postgresql-8.1.8-r4: task do_configure: Failed

Signed-off-by: Eric Bénard e...@eukrea.com
---
 site/arm-common |7 +++
 1 files changed, 7 insertions(+), 0 deletions(-)

diff --git a/site/arm-common b/site/arm-common
index 20de8c5..1554c8f 100644
--- a/site/arm-common
+++ b/site/arm-common
@@ -166,6 +166,13 @@ ac_cv_pwrite=${ac_cv_pwrite=no}
 
php_cv_lib_cookie_io_functions_use_off64_t=${php_cv_lib_cookie_io_functions_use_off64_t=yes}
 cv_php_mbstring_stdarg=${cv_php_mbstring_stdarg=yes}
 
+# postgresql
+pgac_cv_alignof_short=2
+pgac_cv_alignof_int=4
+pgac_cv_alignof_long=4
+pgac_cv_alignof_long_long_int=8
+pgac_cv_alignof_double=8
+
 # rsync
 rsync_cv_HAVE_BROKEN_LARGEFILE=${rsync_cv_HAVE_BROKEN_LARGEFILE=no}
 rsync_cv_HAVE_SOCKETPAIR=${rsync_cv_HAVE_SOCKETPAIR=yes}
-- 
1.6.3.3


___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] hildon-lgpl in nonworking but appears in DEPENDS in recipes

2010-08-26 Thread Khem Raj

On Thu, Aug 26, 2010 at 12:34 PM, Frans Meulenbroeks
fransmeulenbro...@gmail.com wrote:
 2010/8/26 Khem Raj raj.k...@gmail.com:
 Hi,

 hildon was moved to nonworking recipes but there are recipes which
 DEPEND on this.

 gpe-mini-browser/gpe-mini-browser-hildon_0.16.bb:DEPENDS      =
 osb-nrcit libosso hildon-lgpl hildon-fm libgpewidget
 gpe-mini-browser/gpe-mini-browser-hildon_0.15.bb:DEPENDS      =
 osb-nrcit libosso hildon-lgpl hildon-fm libgpewidget
 gpe-mini-browser/gpe-mini-browser-hildon_0.17.bb:DEPENDS      =
 osb-nrcit libosso hildon-lgpl hildon-fm libgpewidget
 libgpepimc/libgpepimc-hildon_0.5.bb:DEPENDS     = libgpewidget-hildon
 gtk+ sqlite hildon-lgpl
 maemo/hildon-status-bar_0.8.11-1.bb:DEPENDS = hildon-lgpl libosso 
 hildon-libs
 maemo/hildon-control-panel_0.9.1-1.2.bb:DEPENDS = hildon-lgpl
 hildon-base-lib osso-af-settings libosso hildon-libs osso-af-settings
 libosso-help
 maemo/libosso-help_1.0.01.bb:DEPENDS =  libosso hildon-lgpl
 hildon-base-lib hildon-libs
 maemo/osso-application-installer_1.0.03-1.bb:DEPENDS = hildon-lgpl
 hildon-base-lib libosso hildon-libs hildon-control-panel
 shared-mime-info
 tasks/task-maemo.bb:    hildon-lgpl

 I am tempted to move them to nonworking as well. opinions ?

 I agree that it is pointless to keep them if they do not build so
 moving them to nonworking is imho quite logical and therefore has my
 blessing.

 However, while you're at it there is more to be moved as there are
 recipes which depend on the ones you propose to move:
 dependencies on libgpepimc-hildon
 gpe-todo/gpe-todo-hildon_0.54.bb:DEPENDS     = libgpewidget-hildon
 libgpepimc-hildon libtododb sdk-default-icons libosso
 gpe-todo/gpe-todo-hildon_0.55.bb:DEPENDS     = libgpewidget-hildon
 libgpepimc-hildon libtododb sdk-default-icons libosso
 :
 dependencies on libosso-help:
 maemo-mapper/maemo-mapper_svn.bb:DEPENDS = gdbm libconic sqlite3 gtk+
 libhildonfm libosso osso-ic-oss libosso-help gnome-vfs dbus
 bluez-libs
 maemo/hildon-control-panel_0.9.1-1.2.bb:DEPENDS = hildon-lgpl
 hildon-base-lib osso-af-settings libosso hildon-libs osso-af-settings
 libosso-help


thanks. Yes I will move them one after another.

 I haven't checked for the non-lib recipes, might be some additonal deps too.

 Frans

 ___
 Openembedded-devel mailing list
 Openembedded-devel@lists.openembedded.org
 http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] [PATCH] ncurses-5.7 : fix sdk build

2010-08-26 Thread Tom Rini


Eric Bénard wrote:


@@ -170,7 +170,7 @@ pkg_prerm_ncurses-tools () {
 fi
 }
 
-BBCLASSEXTEND = native sdk

+BBCLASSEXTEND = native nativesdk


Don't remove sdk from here, just add nativesdk.  We haven't fully 
converted everything.


--
Tom Rini
Mentor Graphics Corporation

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] testing branch 2010-08-23

2010-08-26 Thread Gary Thomas


On 08/23/2010 05:49 PM, Cliff Brake wrote:

Hello,

As detailed in the following page, we are trying to get a testing
branch going where we try to verify OE builds for a number of
combinations of distro/machine/target/

http://wiki.openembedded.net/index.php/Testing

I have branched dev.oe.org to the testing-testing branch, and have
verified it builds the following.

beagleboard angstrom-2008.1 beagleboard-linuxtag2010-demo-image
Ubuntu 10.04 64-bit User:Cbrake
beagleboard angstrom-2008.1 console-image   Ubuntu 10.04 64-bit 
User:Cbrake 


To be clear, a line with an entry in the 'last tested' column indicates a
successful build of that combination?


Next Monday, we will merge testing-testing to the testing branch, and
tag it with the testing_2010-08-23 tag, and note the combinations that
build in the above wiki page.

We are looking for people who are willing to test clean builds of
other combinations on a regular basis, or other ideas on how to make
this testing concept work.  My initial thought is to work on a
weekly cycle, but of course not every combination will be tested every
week.

If this gains enough traction, perhaps we will want to make the
testing branch the default OE meta-data branch so that new users by
default get something that will probably build.  I think its also very
useful to give users a known starting point.  With the myriad of
combinations available, its useful to know what is a good baseline.


--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world


___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

[oe] [PATCH 1/2] matrix-gui-e: add dependency packages

2010-08-26 Thread Chase Maupin

* Added dependency packages such as qt4-embedded-fonts required
  for the matrix-gui application to run.
* Added dependency on matrix-gui-common.

Signed-off-by: Chase Maupin chase.mau...@ti.com
---
 recipes/ti/matrix-gui-e_svn.bb |5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/recipes/ti/matrix-gui-e_svn.bb b/recipes/ti/matrix-gui-e_svn.bb
index adb14df..3bb304d 100644
--- a/recipes/ti/matrix-gui-e_svn.bb
+++ b/recipes/ti/matrix-gui-e_svn.bb
@@ -6,7 +6,7 @@ PRIORITY = optional
 
 SRCREV = 58
 PV = 1.0
-PR = r14+svnr${SRCPV}
+PR = r15+svnr${SRCPV}
 
 SRC_URI = 
svn://gforge.ti.com/svn/matrix_gui/;module=trunk;proto=https;user=anonymous;pswd=''
 \
file://init \
@@ -27,4 +27,5 @@ do_install() {
install -c -m 0755 ${WORKDIR}/init ${D}${sysconfdir}/init.d/matrix-gui-e
 }
 
-RRECOMMENDS_${PN} = qt4-embedded-plugin-mousedriver-tslib
+RRECOMMENDS_${PN} = qt4-embedded-plugin-mousedriver-tslib qt4-embedded-fonts
+RDEPENDS_${PN} += matrix-gui-common
-- 
1.7.0.4


___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

[oe] [PATCH 2/2] matrix-gui-e: change initscript start level

2010-08-26 Thread Chase Maupin

* Set the init script to be added to list of run level
  5 scripts.

Signed-off-by: Chase Maupin chase.mau...@ti.com
---
 recipes/ti/matrix-gui-e_svn.bb |6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/recipes/ti/matrix-gui-e_svn.bb b/recipes/ti/matrix-gui-e_svn.bb
index 3bb304d..35abd25 100644
--- a/recipes/ti/matrix-gui-e_svn.bb
+++ b/recipes/ti/matrix-gui-e_svn.bb
@@ -6,7 +6,7 @@ PRIORITY = optional
 
 SRCREV = 58
 PV = 1.0
-PR = r15+svnr${SRCPV}
+PR = r16+svnr${SRCPV}
 
 SRC_URI = 
svn://gforge.ti.com/svn/matrix_gui/;module=trunk;proto=https;user=anonymous;pswd=''
 \
file://init \
@@ -15,8 +15,8 @@ SRC_URI = 
svn://gforge.ti.com/svn/matrix_gui/;module=trunk;proto=https;user=ano
 S = ${WORKDIR}/trunk
 
 INITSCRIPT_NAME = matrix-gui-e
-#INITSCRIPT_PARAMS = defaults 99
-INITSCRIPT_PARAMS = start 99 3 . stop 99 3 .
+INITSCRIPT_PARAMS = defaults 99
+#INITSCRIPT_PARAMS = start 99 3 . stop 99 3 .
 
 inherit qt4e update-rc.d
 
-- 
1.7.0.4


___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] testing branch 2010-08-23

2010-08-26 Thread Gary Thomas


On 08/26/2010 02:10 PM, Cliff Brake wrote:

On Thu, Aug 26, 2010 at 3:50 PM, Gary Thomasg...@mlbassoc.com  wrote:

On 08/23/2010 05:49 PM, Cliff Brake wrote:


Hello,

As detailed in the following page, we are trying to get a testing
branch going where we try to verify OE builds for a number of
combinations of distro/machine/target/

http://wiki.openembedded.net/index.php/Testing

I have branched dev.oe.org to the testing-testing branch, and have
verified it builds the following.

beagleboard angstrom-2008.1
beagleboard-linuxtag2010-demo-image
Ubuntu 10.04 64-bit User:Cbrake
beagleboard angstrom-2008.1 console-image   Ubuntu 10.04
64-bit User:Cbrake


To be clear, a line with an entry in the 'last tested' column indicates a
successful build of that combination?


Yes, that is my current idea.  I changed the name of the column to
last successful build to be a little more clear.


OK, I've added a couple of builds I'm trying.  It's interesting to
note that all the other builds are using 64-bit hosts and I've had
0% luck with that myself :-(

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world


___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] testing branch 2010-08-23

2010-08-26 Thread Graham Gower

if a build fails, then issues are reported, and the testing-testing
branch is moved ahead to capture fixes made in the dev branch. Once
the issue is fixed, all combinations are retested.

Can I suggest that the testing-testing branch not be moved ahead? Its
not really fair on testers to have to retest, especially if the branch
is moved ahead a couple of times. Obviously breakages should be fixed
and committed, but can't it just wait for the following week's testing
branch to show up as a successful build?

-Graham

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

[oe] Testing build failure

2010-08-26 Thread Gary Thomas


MACHINE=beagleboard 
DISTRO=angstrom-2010.x  
IMAGE=beagleboard-linuxtag2010-demo-image   
HOST=Fedora 12 32-bit   
fails to build ti-dsplink
  -- because ti-cgt6x installed tools incorrectly

Cliff - how did this build for you on Ubuntu/64-bit?  Can you send me
the logs for ti-dsplink and ti-cgt6x?

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world


___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] testing branch 2010-08-23

2010-08-26 Thread Khem Raj

On Thu, Aug 26, 2010 at 4:20 PM, Graham Gower graham.go...@gmail.com wrote:
 if a build fails, then issues are reported, and the testing-testing
 branch is moved ahead to capture fixes made in the dev branch. Once
 the issue is fixed, all combinations are retested.

 Can I suggest that the testing-testing branch not be moved ahead?


I think yes the fixes should be committed to master and then pulled
into the testing-testing branch
IOW testing-testing moved ahead to new head on each monday and I think
if you have successful build
on prior monday and dont want to test it the tag should still be
there. I think continuous build is the only
way we can make sure that what we are committing is not breaking
stuff. ideally testing branch should move
every time a fix is committed upstream which was reported in
testing-testing branch but Monday to Monday is
ok too.

 Its
 not really fair on testers to have to retest, especially if the branch
 is moved ahead a couple of times. Obviously breakages should be fixed
 and committed, but can't it just wait for the following week's testing
 branch to show up as a successful build?

 -Graham

 ___
 Openembedded-devel mailing list
 Openembedded-devel@lists.openembedded.org
 http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] [PATCH] [v2] added recipe for nodejs

2010-08-26 Thread Khem Raj

On (24/08/10 01:57), Paul Menzel wrote:
 Dear AJ,
 
 
 sorry I overlooked that message. I will reply to your other message
 tomorrow.
 
 
 Am Montag, den 23.08.2010, 17:22 -0600 schrieb AJ ONeal:
  bump
  
  AJ ONeal
  
  On Sat, Aug 21, 2010 at 9:28 PM, AJ ONeal coola...@gmail.com wrote:
  
   ---
 
 After this line a short summary of the changes compared to previous
 iterations would be great. Git will ignore this when applying the patch
 but it eases the work of the reviewers.
 
recipes/nodejs/files/libev-cross-cc.patch  |   18 
recipes/nodejs/files/node-cross-cc.patch   |   14 ++
.../node-dont-include-hosts-usr-include.patch  |   22 +++
recipes/nodejs/nodejs_0.2.0.bb |   28
   
4 files changed, 82 insertions(+), 0 deletions(-)
create mode 100644 recipes/nodejs/files/libev-cross-cc.patch
create mode 100644 recipes/nodejs/files/node-cross-cc.patch
create mode 100644
   recipes/nodejs/files/node-dont-include-hosts-usr-include.patch
create mode 100644 recipes/nodejs/nodejs_0.2.0.bb
  
   diff --git a/recipes/nodejs/files/libev-cross-cc.patch
   b/recipes/nodejs/files/libev-cross-cc.patch
   new file mode 100644
   index 000..446015b
   --- /dev/null
   +++ b/recipes/nodejs/files/libev-cross-cc.patch
   @@ -0,0 +1,18 @@
   +diff --git node-v0.2.0/deps/libev/wscript.orig
   node-v0.2.0/deps/libev/wscript
   +index 19e7bb2..f0a3d3b 100644
   +--- node-v0.2.0/deps/libev/wscript.orig
    node-v0.2.0/deps/libev/wscript
   +@@ -52,7 +52,12 @@ def configure(conf):
   +   return 0;
   +   }
   +   
   +-  conf.check_cc(fragment=code, define_name=HAVE_CLOCK_SYSCALL,
   execute=True,
   ++  # TODO determine this dynamically
   ++  CROSS = True
   ++  execute = True
   ++  if CROSS:
   ++execute = False
   ++  conf.check_cc(fragment=code, define_name=HAVE_CLOCK_SYSCALL,
   execute=execute,
   + msg=Checking for SYS_clock_gettime)
   +
   +   have_librt = conf.check(lib='rt', uselib_store='RT')
   diff --git a/recipes/nodejs/files/node-cross-cc.patch
   b/recipes/nodejs/files/node-cross-cc.patch
   new file mode 100644
   index 000..48a6226
   --- /dev/null
   +++ b/recipes/nodejs/files/node-cross-cc.patch
   @@ -0,0 +1,14 @@
   +diff --git node-v0.2.0/wscript.orig node-v0.2.0/wscript
   +index df9ef53..a55d464 100644
   +--- node-v0.2.0/wscript.orig
    node-v0.2.0/wscript
   +@@ -326,6 +326,9 @@ def v8_cmd(bld, variant):
   +   arch = 
   +   if bld.env['DEST_CPU'] == 'x86_64':
   + arch = arch=x64
   ++  # XXX Better support cross-compilation
   ++  else:
   ++arch = arch= + bld.env['DEST_CPU']
   +
   +   if variant == default:
   + mode = release
   diff --git 
   a/recipes/nodejs/files/node-dont-include-hosts-usr-include.patch
   b/recipes/nodejs/files/node-dont-include-hosts-usr-include.patch
   new file mode 100644
   index 000..edbf7c4
   --- /dev/null
   +++ b/recipes/nodejs/files/node-dont-include-hosts-usr-include.patch
   @@ -0,0 +1,22 @@
   +diff --git node-v0.2.0/wscript.orig node-v0.2.0/wscript
   +index 3c5ebc5..905bd58 100644
   +--- node-v0.2.0/wscript.orig
    node-v0.2.0/wscript
   +@@ -162,11 +162,12 @@ def configure(conf):
   +   if Options.options.efence:
   + conf.check(lib='efence', libpath=['/usr/lib', '/usr/local/lib'],
   uselib_store='EFENCE')
   +
   +-  if not conf.check(lib=execinfo, includes=['/usr/include',
   '/usr/local/include'], libpath=['/usr/lib', '/usr/local/lib'],
   uselib_store=EXECINFO):
   +-# Note on Darwin/OS X: This will fail, but will still be used as the
   +-# execinfo stuff are part of the standard library.
   +-if sys.platform.startswith(freebsd):
   +-  conf.fatal(Install the libexecinfo port from
   /usr/ports/devel/libexecinfo.)
   ++  # OpenEmbedded doesn't like us checking here
   ++  #if not conf.check(lib=execinfo, includes=['/usr/include',
   '/usr/local/include'], libpath=['/usr/lib', '/usr/local/lib'],
   uselib_store=EXECINFO):
   ++  #  # Note on Darwin/OS X: This will fail, but will still be used as 
   the
   ++  #  # execinfo stuff are part of the standard library.
   ++  #  if sys.platform.startswith(freebsd):
   ++  #conf.fatal(Install the libexecinfo port from
   /usr/ports/devel/libexecinfo.)
   +
   +   if not Options.options.without_ssl:
   + if conf.check_cfg(package='openssl',
 
 Did you sent these patches upstream? Maybe document that in the patch
 headers. There is also a page in the Wiki regarding this.
 
   diff --git a/recipes/nodejs/nodejs_0.2.0.bb b/recipes/nodejs/
   nodejs_0.2.0.bb
   new file mode 100644
   index 000..83bfa2e
   --- /dev/null
   +++ b/recipes/nodejs/nodejs_0.2.0.bb
   @@ -0,0 +1,28 @@
   +DESCRIPTION = nodeJS Evented I/O for V8 JavaScript
   +HOMEPAGE = http://nodejs.org;
   +LICENSE = MIT
   +DEPENDS = openssl
   +SRC_URI =  \
   +  http://nodejs.org/dist/node-v${PV}.tar.gz \
   +

Re: [oe] [PATCH] quilt: Add option QUILT_NO_RM_SYMLINKS so follow symlinks with quilt refresh

2010-08-26 Thread Chris Larson

On Fri, Jul 9, 2010 at 1:21 PM, Khem Raj raj.k...@gmail.com wrote:

 ++  if [ $QUILT_NO_RM_SYMLINKS != yes ]



I'd suggest:
  if [ -L $filename -a $QUILT_NO_RM_SYMLINKS != yes ]
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] testing branch 2010-08-23

2010-08-26 Thread Graham Gower

On 27 August 2010 13:15, Khem Raj raj.k...@gmail.com wrote:
 On Thu, Aug 26, 2010 at 4:20 PM, Graham Gower graham.go...@gmail.com wrote:
 if a build fails, then issues are reported, and the testing-testing
 branch is moved ahead to capture fixes made in the dev branch. Once
 the issue is fixed, all combinations are retested.

 Can I suggest that the testing-testing branch not be moved ahead?


 I think yes the fixes should be committed to master and then pulled
 into the testing-testing branch
 IOW testing-testing moved ahead to new head on each monday and I think
 if you have successful build
 on prior monday and dont want to test it the tag should still be
 there. I think continuous build is the only
 way we can make sure that what we are committing is not breaking
 stuff. ideally testing branch should move
 every time a fix is committed upstream which was reported in
 testing-testing branch but Monday to Monday is
 ok too.

I think maybe I was just confused about how it will work in practise.
I'll just wait and watch it for a couple of weeks :)

-Graham

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

[oe] [PATCH] MAINTAINERS: add an entry

2010-08-26 Thread Roman I Khimov

Signed-off-by: Roman I Khimov khi...@altell.ru
---
 MAINTAINERS |8 
 1 files changed, 8 insertions(+), 0 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 67a65c4..0fad51d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -329,6 +329,14 @@ Recipes:anthy, nunome, uim*, granule, qpobox*, 
qte-font-unifont*
 Recipes:qpf-unismall, qpobox, poboxserver, imkit*, scim, zten
 Recipes:eb*, tomoe, offline-wikipedia
 
+Person:Roman I Khimov
+Mail:  khi...@altell.ru
+Mail:  ro...@khimov.ru
+Website:http://roman.khimov.ru
+Recipes:clamav, cluster-glue, cluster-resource-agents, conntrack-tools
+Recipes:ethtool, libhtp, openais, pacemaker, ragel-native, squid
+Recipes:squidguard, suricata
+
 Person: Sergey Lapin
 Mail:   sla...@ossfans.org
 Machines:   palm*, afeb9260
-- 
1.6.4.2


___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] [PATCH] MAINTAINERS: add an entry

2010-08-26 Thread Roman I Khimov

В сообщении от Пятница 27 августа 2010 09:07:53 автор Roman I Khimov написал:
 +Person:  Roman I Khimov
 +Mail:khi...@altell.ru
 +Mail:ro...@khimov.ru
 +Website:http://roman.khimov.ru

And I'll fix tabs vs. spaces, yes.

-- 
 http://roman.khimov.ru
mailto: ro...@khimov.ru
gpg --keyserver hkp://subkeys.pgp.net --recv-keys 0xE5E055C3


signature.asc
Description: This is a digitally signed message part.
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: [oe] [PATCH] [v2] added recipe for nodejs

2010-08-26 Thread AJ ONeal

I'll resubmit this weekend and put that patch tutorial on the wiki too.

AJ ONeal


On Thu, Aug 26, 2010 at 10:04 PM, Khem Raj raj.k...@gmail.com wrote:

 On (24/08/10 01:57), Paul Menzel wrote:
  Dear AJ,
 
 
  sorry I overlooked that message. I will reply to your other message
  tomorrow.
 
 
  Am Montag, den 23.08.2010, 17:22 -0600 schrieb AJ ONeal:
   bump
  
   AJ ONeal
  
   On Sat, Aug 21, 2010 at 9:28 PM, AJ ONeal coola...@gmail.com wrote:
  
---
 
  After this line a short summary of the changes compared to previous
  iterations would be great. Git will ignore this when applying the patch
  but it eases the work of the reviewers.
 
 recipes/nodejs/files/libev-cross-cc.patch  |   18
 
 recipes/nodejs/files/node-cross-cc.patch   |   14 ++
 .../node-dont-include-hosts-usr-include.patch  |   22
 +++
 recipes/nodejs/nodejs_0.2.0.bb |   28

 4 files changed, 82 insertions(+), 0 deletions(-)
 create mode 100644 recipes/nodejs/files/libev-cross-cc.patch
 create mode 100644 recipes/nodejs/files/node-cross-cc.patch
 create mode 100644
recipes/nodejs/files/node-dont-include-hosts-usr-include.patch
 create mode 100644 recipes/nodejs/nodejs_0.2.0.bb
   
diff --git a/recipes/nodejs/files/libev-cross-cc.patch
b/recipes/nodejs/files/libev-cross-cc.patch
new file mode 100644
index 000..446015b
--- /dev/null
+++ b/recipes/nodejs/files/libev-cross-cc.patch
@@ -0,0 +1,18 @@
+diff --git node-v0.2.0/deps/libev/wscript.orig
node-v0.2.0/deps/libev/wscript
+index 19e7bb2..f0a3d3b 100644
+--- node-v0.2.0/deps/libev/wscript.orig
 node-v0.2.0/deps/libev/wscript
+@@ -52,7 +52,12 @@ def configure(conf):
+   return 0;
+   }
+   
+-  conf.check_cc(fragment=code, define_name=HAVE_CLOCK_SYSCALL,
execute=True,
++  # TODO determine this dynamically
++  CROSS = True
++  execute = True
++  if CROSS:
++execute = False
++  conf.check_cc(fragment=code, define_name=HAVE_CLOCK_SYSCALL,
execute=execute,
+ msg=Checking for SYS_clock_gettime)
+
+   have_librt = conf.check(lib='rt', uselib_store='RT')
diff --git a/recipes/nodejs/files/node-cross-cc.patch
b/recipes/nodejs/files/node-cross-cc.patch
new file mode 100644
index 000..48a6226
--- /dev/null
+++ b/recipes/nodejs/files/node-cross-cc.patch
@@ -0,0 +1,14 @@
+diff --git node-v0.2.0/wscript.orig node-v0.2.0/wscript
+index df9ef53..a55d464 100644
+--- node-v0.2.0/wscript.orig
 node-v0.2.0/wscript
+@@ -326,6 +326,9 @@ def v8_cmd(bld, variant):
+   arch = 
+   if bld.env['DEST_CPU'] == 'x86_64':
+ arch = arch=x64
++  # XXX Better support cross-compilation
++  else:
++arch = arch= + bld.env['DEST_CPU']
+
+   if variant == default:
+ mode = release
diff --git
 a/recipes/nodejs/files/node-dont-include-hosts-usr-include.patch
b/recipes/nodejs/files/node-dont-include-hosts-usr-include.patch
new file mode 100644
index 000..edbf7c4
--- /dev/null
+++ b/recipes/nodejs/files/node-dont-include-hosts-usr-include.patch
@@ -0,0 +1,22 @@
+diff --git node-v0.2.0/wscript.orig node-v0.2.0/wscript
+index 3c5ebc5..905bd58 100644
+--- node-v0.2.0/wscript.orig
 node-v0.2.0/wscript
+@@ -162,11 +162,12 @@ def configure(conf):
+   if Options.options.efence:
+ conf.check(lib='efence', libpath=['/usr/lib',
 '/usr/local/lib'],
uselib_store='EFENCE')
+
+-  if not conf.check(lib=execinfo, includes=['/usr/include',
'/usr/local/include'], libpath=['/usr/lib', '/usr/local/lib'],
uselib_store=EXECINFO):
+-# Note on Darwin/OS X: This will fail, but will still be used
 as the
+-# execinfo stuff are part of the standard library.
+-if sys.platform.startswith(freebsd):
+-  conf.fatal(Install the libexecinfo port from
/usr/ports/devel/libexecinfo.)
++  # OpenEmbedded doesn't like us checking here
++  #if not conf.check(lib=execinfo, includes=['/usr/include',
'/usr/local/include'], libpath=['/usr/lib', '/usr/local/lib'],
uselib_store=EXECINFO):
++  #  # Note on Darwin/OS X: This will fail, but will still be used
 as the
++  #  # execinfo stuff are part of the standard library.
++  #  if sys.platform.startswith(freebsd):
++  #conf.fatal(Install the libexecinfo port from
/usr/ports/devel/libexecinfo.)
+
+   if not Options.options.without_ssl:
+ if conf.check_cfg(package='openssl',
 
  Did you sent these patches upstream? Maybe document that in the patch
  headers. There is also a page in the Wiki regarding this.
 
diff --git a/recipes/nodejs/nodejs_0.2.0.bb b/recipes/nodejs/
nodejs_0.2.0.bb
new file mode 100644
index 000..83bfa2e
--- /dev/null

45 matches

Mail list logo