Re: [oe] update canutils to current version
2010/8/13 Vitus Jensen vjen...@gmx.de: On Fri, 13 Aug 2010, Khem Raj wrote: On Fri, Aug 13, 2010 at 2:59 AM, Vitus Jensen vjen...@gmx.de wrote: On Fri, 13 Aug 2010, Frans Meulenbroeks wrote: 2010/8/13 Vitus Jensen vjen...@gmx.de: On Fri, 13 Aug 2010, Vitus Jensen wrote: The following patches will update canutils to the current version 4.0.6 and remove older 4.0.x versions. Also only the latest version of libsocketcan will be kept. Frans, thank you for the ACKs. Could you please apply the patches, too? I have no right to do so. Applied. Thanks for the contribution System guru's: Vitus's patches did not show up in patchwork They did. But after you posted you ACKs I changed their state to Accepted and then they are usually filtered by Action Required. I'm not really sure I did the right thing but I don't believe they shouldn't remain in New. If they got applied change the state to 'applied' Sure, already did! Do I set the 'archive' bit, too? Frans got hit by the fact, that 'accepted' patches don't show up in the list by default. Vitus posts patches Frans acks patches Vitus changes state to 'accepted' Vitus asks Frans to apply Frans: where are those patches in patchwork??? Frans forces his googlemail to produce usable mail and applies Vitus changes state to 'applied' Probably I should update the wiki to document the above procedure, right? I saw a different thread from Paul on patchwork. Let's discuss this in that thread. Frans ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] bump libphone-ui and libphone-ui-shr as to the 0.0.1 release and bump SRCREV to the 0.0.1 commit
On Sat, Aug 14, 2010 at 03:28:44AM +0200, Lukas Märdian wrote: Signed-off-by: Lukas Märdian lukasmaerd...@gmail.com --- recipes/shr/libphone-ui-shr_git.bb |6 +++--- recipes/shr/libphone-ui_git.bb |4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) Applied, thanks! Next time, please prepare better commit message: http://wiki.openembedded.net/index.php/Commit_Policy -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] patch queue/patchwork: How should states be used? (was: update canutils to current version)
On Sat, Aug 14, 2010 at 09:59:59AM +0200, Frans Meulenbroeks wrote: review patch. if ok and it is a simple patch download patch from patchwork in mbox fmt git am patch bitbake recipe if ok, git push. check contrib/patchwork/pw-am.sh to simplify steps 2 and 3. Regards, -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] serload-native: Removing legacy staging
2010/8/13 Ahsan, Noor noor_ah...@mentor.com:
* Replaced do_stage function with do_install and replaced ${STAGING_BINDIR}
with ${D}${bindir}
Signed-off-by: Ahsan, Noor noor_ah...@mentor.com
---
recipes/simpad-utilities/serload-native.bb | 12
1 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/recipes/simpad-utilities/serload-native.bb
b/recipes/simpad-utilities/serload-native.bb
index 9be199f..d147db2 100644
--- a/recipes/simpad-utilities/serload-native.bb
+++ b/recipes/simpad-utilities/serload-native.bb
@@ -3,14 +3,18 @@ LICENSE= GPL
DESCRIPTION = Console utility for transferring a SIMpad boot image via
serial a SIMpad
FILESDIR = $...@os.path.dirname(bb.data.getVar('FILE',d,1))}/serload
SRC_URI = file://serialdownload.cpp file://main.cpp file://serialdownload.h
+PR = r1
inherit native
+NATIVE_INSTALL_WORKS = 1
+
do_compile() {
- cp ${WORKDIR}/*.h ${WORKDIR}/*.cpp .
- ${CXX} -I. -o serload main.cpp serialdownload.cpp
+ cp ${WORKDIR}/*.h ${WORKDIR}/*.cpp .
+ ${CXX} -I. -o serload main.cpp serialdownload.cpp
}
-do_stage() {
- install -m 0755 serload ${STAGING_BINDIR}/
+do_install() {
+ install -d ${D}${bindir}/
+ install -m 0755 serload ${D}${bindir}/
}
removed FILESDIR as suggested by Tom RIni,
reran oe-styilze
compiled
committed and pushed
Thanks for your contribution.
Feel free to attack some more recipes :-)
Frans
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH]Removing Legacy staging from genboot native recipe
reworked the patch a little bit, tested building and pushed. FILEDIR is also gone thanks for your contribution Frans ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] need help with do_install for v8 bitbake recipe
I've created a recipe for v8 and the do_compile() works. http://fastr.github.com/articles/v8-on-OpenEmbedded.html I'm still not very familiar with bitbake and I'd like to know what I need to do with do_install() and do_stage() so that the library is available to other packages when I add DEPENDS += libv8. The only file is libv8.a in the builddir. Specifically I'm trying to build nodejs with v8 as a shared library, because I can't get the v8 that comes with it to cross-compile. AJ ONeal ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] bump libphone-ui and libphone-ui-shr as to the 0.0.1 release and bump SRCREV to the 0.0.1 commit
Am 14.08.2010 10:12, schrieb Martin Jansa: Applied, thanks! Next time, please prepare better commit message: http://wiki.openembedded.net/index.php/Commit_Policy It was my first OE patch and I wasn't aware of the commit policy. Will take care next time, thanks! -- Lukas ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] iputils fails to build due to missing sgmlspl
I was mistaken. It didn't build iputils. I started over from scratch, built everything up to iputils, and failed! sgmlspl wasn't installed correctly (not in the path). I tried: bash-3.2$ cp $OVEROTOP/tmp/work/i686-linux/sgmlspl-native-1.03ii-r0/SGMLSpm/sgmlspl $OVEROTOP/tmp/sysroots/i686-linux/usr/bin/ but then got another error: Can't locate SGMLS/Output.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.10.0 /usr/local/share/perl/5.10.0 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .) at /mnt/data/overo-oe/tmp/sysroots/i686-linux/usr/bin/sgmlspl line 62. Seeing that is was looking outside of the OE paths and not able to find it, I gave up. sudo-apt-get install sgmlspl bitbake iputils now it appears to be running... AJ ONeal (317) 426-6525 On Fri, Aug 13, 2010 at 6:25 PM, AJ ONeal coola...@gmail.com wrote: Seems that it was a hanging environment issue. I exited from the current shell, opened a new one, ran the same thing a third time and it worked. AJ ONeal On Fri, Aug 13, 2010 at 4:05 PM, AJ ONeal coola...@gmail.com wrote: Actually, that's what I did. I just typed it wrong when I put it in the e-mail. There is no non-native sgmlspl package. AJ ONeal On Fri, Aug 13, 2010 at 3:32 PM, Tom Rini tom_r...@mentor.com wrote: AJ ONeal wrote: This is with a fresh install of oe and bitbake (as per the gumstix docs) | /mnt/data/Code/overo-oe/tmp/sysroots/i686-linux/usr/armv7a/lib/gcc/arm-angstrom-linux-gnueabi/4.3.3/../../../../arm-angstrom-linux-gnueabi/bin/ld: warning: libc.so, needed by /mnt/data/Code/overo-oe/tmp/sysroots/i686-linux/usr/armv7a/lib/gcc/arm-angstrom-linux-gnueabi/4.3.3/../../../../arm-angstrom-linux-gnueabi/lib/libgcc_s.so, not found (try using -rpath or -rpath-link) | make -C doc man | make[1]: Entering directory `/mnt/data/Code/overo-oe/tmp/work/armv7a-angstrom-linux-gnueabi/iputils-20071127-r1/iputils_20071127.orig/doc' | /bin/sh: sgmlspl: command not found | make[1]: *** [arping.8] Error 127 | make[1]: Leaving directory `/mnt/data/Code/overo-oe/tmp/work/armv7a-angstrom-linux-gnueabi/iputils-20071127-r1/iputils_20071127.orig/doc' | make: *** [man] Error 2 | FATAL: oe_runmake failed The problem is not solved by bitbake -c clean iputils; bitbake sgmlspl; bitbake iputils You would need to do bitbake sgmlspl-native ; bitbake iputils, to get sgmlspl that runs on the host. sgmlspl-native will bring in perl-native and some other stuff, FYI. -- Tom Rini Mentor Graphics Corporation ___ 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] need help with do_install for v8 bitbake recipe
On Sat, Aug 14, 2010 at 03:29:48AM -0600, AJ ONeal wrote: I've created a recipe for v8 and the do_compile() works. http://fastr.github.com/articles/v8-on-OpenEmbedded.html I'm still not very familiar with bitbake and I'd like to know what I need to do with do_install() and do_stage() so that the library is available to other packages when I add DEPENDS += libv8. The only file is libv8.a in the builddir. Specifically I'm trying to build nodejs with v8 as a shared library, because I can't get the v8 that comes with it to cross-compile. AJ ONeal Hi, do_stage is deprecated don't use it anymore. Bye Henning ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] What to do about the poor bitbake Quality Control?
I agree with you AJ, its become a serious pain to just get a built image. I myself have only built once completely and have yet to again since figuring out the changes I needed to make to that image. I would like to help myself but someone like me whose not very competent in this area finds the documentation a tad lacking to properly learn the ways to help. I still have yet to figure out how to even get my own program from the net to build with OE as just following the hello world does not seem to be enough for me to grasp how to do it with an actual problem. Which runs me into my next issue I can not properly modify the way some programs build to get the features I want. I have also noticed on the gumstix boards while most of the time it seems its the same errors people get, every once in awhile you see some people with one issue and others with another. I am sure this wont be of much use as a post but figured I would chime in from an inexperienced beginner trying to get a footing in here and to actually be able to use things properly. On Sat, Aug 14, 2010 at 8:46 AM, AJ ONeal coola...@gmail.com wrote: This is about the 4th time that I've `rm -rf`-d everything and started from scratch and never yet got a working `bitbake omap3-console-image` Every time I `git pull` it's a different set of problems. It's never the same package twice, but they never all compile for the basic console image anywhere from 4 to 20 hours in. Fortunately, I do have a machine that did build omap3-console-image a few weeks ago at work. But I've never been able to get it on my machine at home (same os) to start playing around with. What needs to happen in order for things to git checked that they work with at least a few common meta-tasks before being pushed out? And is there anything I can do to help? (Donate some machine time to run tests, for example) Obviously, we all have our day jobs and whatnot, but this is becoming really frustrating for me and I'd like to see things improve. AJ ONeal ___ 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] What to do about the poor bitbake Quality Control?
I've been compiling some common general issues
http://fastr.github.com/articles/Troubleshooting-bitbake.html
Here's some quick-n-dirty instructions akin to using devshell:
1. cd ${OVEROTOP}/tmp/work/${ARCH}/${PACKAGE}_${VER}_r${REV}/${BUILD}
- ${ARCH} is probably armv7a-angstrom-linux-gnueabi
- ${BUILD} is a directory which is not NOT src or temp such as the
package name or git or trunk or svn
- ${VER} and ${REV} - duh.
2. `cp ../temp/run.do_compile.${OLD_PID}
- ${OLD_PID} is a number like 3597 or 4352
- do_compile could be any task - do_install, etc
3. vim run.do_compile.1234
1. comment out do_compile() (or whatever)
2. add bash --norc
4. ./run.do_compile.1234 will put you in an environment with all
variables set
5. make (or whatever) to try to build, debug issues
6. exit (when done to go back to shell without run.do_compile settings)
This is based on the tip on openembedded wiki, but it took me a while to
understand what theirs meant so I cleaned it up in a fashion which is
hopefully crystal clear.
AJ ONeal
On Sat, Aug 14, 2010 at 10:16 AM, J. L. vwyodap...@gmail.com wrote:
I agree with you AJ, its become a serious pain to just get a built
image. I myself have only built once completely and have yet to again
since figuring out the changes I needed to make to that image. I would
like to help myself but someone like me whose not very competent in
this area finds the documentation a tad lacking to properly learn the
ways to help. I still have yet to figure out how to even get my own
program from the net to build with OE as just following the hello
world does not seem to be enough for me to grasp how to do it with an
actual problem. Which runs me into my next issue I can not properly
modify the way some programs build to get the features I want.
I have also noticed on the gumstix boards while most of the time it
seems its the same errors people get, every once in awhile you see
some people with one issue and others with another.
I am sure this wont be of much use as a post but figured I would chime
in from an inexperienced beginner trying to get a footing in here and
to actually be able to use things properly.
On Sat, Aug 14, 2010 at 8:46 AM, AJ ONeal coola...@gmail.com wrote:
This is about the 4th time that I've `rm -rf`-d everything and started
from
scratch and never yet got a working `bitbake omap3-console-image`
Every time I `git pull` it's a different set of problems. It's never the
same package twice, but they never all compile for the basic console
image
anywhere from 4 to 20 hours in.
Fortunately, I do have a machine that did build omap3-console-image a few
weeks ago at work. But I've never been able to get it on my machine at
home
(same os) to start playing around with.
What needs to happen in order for things to git checked that they work
with
at least a few common meta-tasks before being pushed out?
And is there anything I can do to help? (Donate some machine time to run
tests, for example)
Obviously, we all have our day jobs and whatnot, but this is becoming
really
frustrating for me and I'd like to see things improve.
AJ ONeal
___
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
Re: [oe] What to do about the poor bitbake Quality Control?
Right on thanks that does seem to answer a couple questions I have
come across so far especially the devshell. I will give making my
recipe another shot again today and see if I can get further with it
or even crazier get it to build correctly. Thanks again hopefully we
will see some other input to your original statement.
On Sat, Aug 14, 2010 at 10:06 AM, AJ ONeal coola...@gmail.com wrote:
I've been compiling some common general issues
http://fastr.github.com/articles/Troubleshooting-bitbake.html
Here's some quick-n-dirty instructions akin to using devshell:
1. cd ${OVEROTOP}/tmp/work/${ARCH}/${PACKAGE}_${VER}_r${REV}/${BUILD}
- ${ARCH} is probably armv7a-angstrom-linux-gnueabi
- ${BUILD} is a directory which is not NOT src or temp such as the
package name or git or trunk or svn
- ${VER} and ${REV} - duh.
2. `cp ../temp/run.do_compile.${OLD_PID}
- ${OLD_PID} is a number like 3597 or 4352
- do_compile could be any task - do_install, etc
3. vim run.do_compile.1234
1. comment out do_compile() (or whatever)
2. add bash --norc
4. ./run.do_compile.1234 will put you in an environment with all
variables set
5. make (or whatever) to try to build, debug issues
6. exit (when done to go back to shell without run.do_compile settings)
This is based on the tip on openembedded wiki, but it took me a while to
understand what theirs meant so I cleaned it up in a fashion which is
hopefully crystal clear.
AJ ONeal
On Sat, Aug 14, 2010 at 10:16 AM, J. L. vwyodap...@gmail.com wrote:
I agree with you AJ, its become a serious pain to just get a built
image. I myself have only built once completely and have yet to again
since figuring out the changes I needed to make to that image. I would
like to help myself but someone like me whose not very competent in
this area finds the documentation a tad lacking to properly learn the
ways to help. I still have yet to figure out how to even get my own
program from the net to build with OE as just following the hello
world does not seem to be enough for me to grasp how to do it with an
actual problem. Which runs me into my next issue I can not properly
modify the way some programs build to get the features I want.
I have also noticed on the gumstix boards while most of the time it
seems its the same errors people get, every once in awhile you see
some people with one issue and others with another.
I am sure this wont be of much use as a post but figured I would chime
in from an inexperienced beginner trying to get a footing in here and
to actually be able to use things properly.
On Sat, Aug 14, 2010 at 8:46 AM, AJ ONeal coola...@gmail.com wrote:
This is about the 4th time that I've `rm -rf`-d everything and started
from
scratch and never yet got a working `bitbake omap3-console-image`
Every time I `git pull` it's a different set of problems. It's never the
same package twice, but they never all compile for the basic console
image
anywhere from 4 to 20 hours in.
Fortunately, I do have a machine that did build omap3-console-image a few
weeks ago at work. But I've never been able to get it on my machine at
home
(same os) to start playing around with.
What needs to happen in order for things to git checked that they work
with
at least a few common meta-tasks before being pushed out?
And is there anything I can do to help? (Donate some machine time to run
tests, for example)
Obviously, we all have our day jobs and whatnot, but this is becoming
really
frustrating for me and I'd like to see things improve.
AJ ONeal
___
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
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] What to do about the poor bitbake Quality Control?
2010/8/14 AJ ONeal coola...@gmail.com: This is about the 4th time that I've `rm -rf`-d everything and started from scratch and never yet got a working `bitbake omap3-console-image` Every time I `git pull` it's a different set of problems. It's never the same package twice, but they never all compile for the basic console image anywhere from 4 to 20 hours in. Fortunately, I do have a machine that did build omap3-console-image a few weeks ago at work. But I've never been able to get it on my machine at home (same os) to start playing around with. What needs to happen in order for things to git checked that they work with at least a few common meta-tasks before being pushed out? And is there anything I can do to help? (Donate some machine time to run tests, for example) Obviously, we all have our day jobs and whatnot, but this is becoming really frustrating for me and I'd like to see things improve. If you are using dev head, you're living on the edge. If you can't stand that better use the stable branch. As far as there are issues: Either report them, or better fix them. (or as a workaround you could find the commit wthat broke it and report that and perhaps temporariy locally revert that commit if you cannot fix it). Having said that: I don't really see many issues. Maybe I'm building a different set of packages or for a different set of hw or for a different distro. Frans ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] What to do about the poor bitbake Quality Control?
On 08/14/2010 12:01 PM, Frans Meulenbroeks wrote: 2010/8/14 AJ ONealcoola...@gmail.com: This is about the 4th time that I've `rm -rf`-d everything and started from scratch and never yet got a working `bitbake omap3-console-image` Every time I `git pull` it's a different set of problems. It's never the same package twice, but they never all compile for the basic console image anywhere from 4 to 20 hours in. Fortunately, I do have a machine that did build omap3-console-image a few weeks ago at work. But I've never been able to get it on my machine at home (same os) to start playing around with. What needs to happen in order for things to git checked that they work with at least a few common meta-tasks before being pushed out? And is there anything I can do to help? (Donate some machine time to run tests, for example) Obviously, we all have our day jobs and whatnot, but this is becoming really frustrating for me and I'd like to see things improve. If you are using dev head, you're living on the edge. If you can't stand that better use the stable branch. As far as there are issues: Either report them, or better fix them. (or as a workaround you could find the commit wthat broke it and report that and perhaps temporariy locally revert that commit if you cannot fix it). Having said that: I don't really see many issues. Maybe I'm building a different set of packages or for a different set of hw or for a different distro. I think they are building from the gumstix overo repo. We are interested in failures (at least failures for recipes that are in .dev), but we can't guarantee when our fixes will hit the gumstix repository. Philip Philip ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] autotools issues (MKINSTALLDIRS, -s_
On Sun, Aug 08, 2010 at 05:53:42PM +0200, Frans Meulenbroeks wrote: I'm not too good in autotools. While makeing the git recipe for urjtag I bumped into the following two issues: First of all it seems autoreconf needs the -s flag. This tells to use symlinks. Guess things are done out of order or so. I've fixed this by adding EXTRA_AUTORECONF = -s to my recipes. That makes configure happy, but it does not really feel as a good solution. Don't know about this. The second issue is that install fails. Apparently MKINSTALLDIRS does not have the proper value (it should be tools/mkinstalldirs, but it is an empty string). I've tried some things, peeked at some other patches for MKINSTALLDIRS but didn't really get to a satisfactory solution Any wizard here who can give me some guidance? I noticed in the past also trouble with MKINSTALLDIRS and I think older gettext versions are buggy and affect this. I workaround it with AM_GNU_GETTEXT([external]) # version 0.11 doesn't support make distcheck, see # http://lists.debian.org/debian-i18n/2009/09/msg00176.html # versions 0.12-0.14.6 require a mkinstalldirs hack for make distcheck # (at least for automake version 1.11) MKINSTALLDIRS=\$\(top_srcdir\)/autotools/mkinstalldirs AC_SUBST(MKINSTALLDIRS) AM_GNU_GETTEXT_VERSION(0.12) in my configure.ac. Try increasing the version of the required gettext version in the last line to verify that you have the same problem. If you don't use gettext than I cannot help you ... Jens ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] What to do about the poor bitbake Quality Control?
How do I enable logging to tenderbox? I'd be happy to do that. I googled it to little avail: http://www.google.com/search?hl=enq=tinderbox+openembedded For reference, here's the process I've been following: rm ~/overo-oe -rf # *clean it all out* mkdir -p ~/overo-oe cd ~/overo-oe git clone git://gitorious.org/gumstix-oe/mainline.git org.openembedded.dev # *get a fresh copy of the repo* cd org.openembedded.dev git checkout --track -b overo origin/overo cd ~/overo-oe git clone git://git.openembedded.net/bitbake bitbake cd bitbake git checkout 1.8.18 cd ~/overo-oe cp -r org.openembedded.dev/contrib/gumstix/build . cp ~/.bashrc ~/bashrc.bak cat ~/overo-oe/build/profile ~/.bashrc source ~/overo-oe/build/profile bitbake omap3-console-image # *make the basic image from a fresh start* AJ ONeal On Sat, Aug 14, 2010 at 1:04 PM, Frans Meulenbroeks fransmeulenbro...@gmail.com wrote: 2010/8/14 Frans Meulenbroeks fransmeulenbro...@gmail.com: If you are using dev head, you're living on the edge. If you can't stand that better use the stable branch. As far as there are issues: Either report them, or better fix them. (or as a workaround you could find the commit wthat broke it and report that and perhaps temporariy locally revert that commit if you cannot fix it). Having said that: I don't really see many issues. Maybe I'm building a different set of packages or for a different set of hw or for a different distro. Frans Addition: I noticed when pressing send that you also mailed to gumstix-users, so apparently you do have a gumstix. I haven't so I have never build for it and cannot really help you with it as I am not planning on buying one (so even though I could build I cannot test). What you also can do is enable logging to tinderbox then at least the info of the faulty builds becomes available for others. 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
