can everyone build beagleboard-demo-image from OE checkout?

GoogleGroups
1

just to do a quick survey, how many people are building their
beagleboard-demo-image angstrom images from the development branch of
OE? for quite some time, i had difficulties building that under
fedora due to a couple tricky and subtle problems that showed up only
on fedora. recently, though, builds have been working fine but i'm
curious if builds are also working on other distros.

  and to follow up on that, how regularly are beagleboard
fixes/enhancements being pushed into OE? so that i can do regular
"git pull"s and know that i'll have the latest version? thanks.

rday

2

just to do a quick survey, how many people are building their
beagleboard-demo-image angstrom images from the development branch of
OE? for quite some time, i had difficulties building that under
fedora due to a couple tricky and subtle problems that showed up only
on fedora. recently, though, builds have been working fine but i'm
curious if builds are also working on other distros.

  and to follow up on that, how regularly are beagleboard
fixes/enhancements being pushed into OE? so that i can do regular
"git pull"s and know that i'll have the latest version? thanks.

rday
--

I typically build from the stable.2009 branch, not the dev branch.
Should I be using the dev branch?

Freeman

3

just to do a quick survey, how many people are building their
beagleboard-demo-image angstrom images from the development branch of
OE? for quite some time, i had difficulties building that under
fedora due to a couple tricky and subtle problems that showed up only
on fedora. recently, though, builds have been working fine but i'm
curious if builds are also working on other distros.

and to follow up on that, how regularly are beagleboard
fixes/enhancements being pushed into OE? so that i can do regular
"git pull"s and know that i'll have the latest version? thanks.

rday
--

I typically build from the stable.2009 branch, not the dev branch.
Should I be using the dev branch?

If you are happy with stable, do not switch :slight_smile:

Philip

4

How do I check out the demo image and build from it? I'm currently using 2009 stable. I'm starting to think I need to try dev now and then.

My Angstrom builds work fine on Fedora 12 x86_64, I don't really see any issues with it.

Bob

5

not if the stable branch does everything you want. it's a given
that the development branch sometimes breaks. but working with the
dev branch has (for me) two advantages:

  1) cutting edge, since i assume that all the new stuff gets in
     there first, and

  2) i'm at least helping to debug the latest and greatest by
     updating and re-building on a regular basis

it's that first point that's more important -- i'd just like to
confirm that any of the new C4-related stuff is pushed into the dev
branch fairly quickly, so i don't have to worry about applying any
additional patches.

rday

6

(others can correct me if i'm wrong here.)

  if you're a beginner to git, the instructions at the OE wiki for
checking out and building the dev branch are not as clear as they
could be. start here:

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

  first, you can grab the repo with:

$ git clone git://git.openembedded.org/openembedded

what's not explicitly mentioned there is that, after a new clone,
you're actually working with the dev branch:

$ git branch
* org.openembedded.dev
$

if you want to build from the stable branch, you explicitly need to
check it out with:

$ git checkout -b stable/2009 origin/stable/2009

once you do that, you can see you now have two branches:

$ git branch
  org.openembedded.dev
* stable/2009
$

and you can switch back to the dev branch with:

$ git checkout org.openembedded.dev
Switched to branch 'org.openembedded.dev'
$

  so if you're currently building from stable, just checkout the dev
branch but, if you do, i *believe* you need to rebuild from scratch
since you can't generate the builds from those two branches in the
same output directory.

  as of now, the dev branch builds fine on fedora 12 x86_64.

rday

7

if you're a beginner to git, the instructions at the OE wiki for

checking out and building the dev branch are not as clear as they
could be. start here:

   Openembedded-Hotels, Villen, Unterkünfte in Leipzig

   first, you can grab the repo with:

$ git clone git://git.openembedded.org/openembedded

what's not explicitly mentioned there is that, after a new clone,
you're actually working with the dev branch:

$ git branch
* org.openembedded.dev
$

if you want to build from the stable branch, you explicitly need to
check it out with:

$ git checkout -b stable/2009 origin/stable/2009

once you do that, you can see you now have two branches:

$ git branch
   org.openembedded.dev
* stable/2009
$

and you can switch back to the dev branch with:

$ git checkout org.openembedded.dev
Switched to branch 'org.openembedded.dev'
$

   so if you're currently building from stable, just checkout the dev
branch but, if you do, i *believe* you need to rebuild from scratch
since you can't generate the builds from those two branches in the
same output directory.

   as of now, the dev branch builds fine on fedora 12 x86_64.

rday
   
Thank you, I greatly appreciate the clarification. I'm not (as yet) too good with git, and entirely new to openembedded.

Bob

8

From: beagleboard@googlegroups.com
[mailto:beagleboard@googlegroups.com] On Behalf Of Robert P. J. Day
Sent: Thursday, February 04, 2010 2:21 PM
To: BeagleBoard list
Subject: [beagleboard] can everyone build beagleboard-demo-image from OE
checkout?

  just to do a quick survey, how many people are building their
beagleboard-demo-image angstrom images from the development branch of
OE? for quite some time, i had difficulties building that under
fedora due to a couple tricky and subtle problems that showed up only
on fedora. recently, though, builds have been working fine but i'm
curious if builds are also working on other distros.

I use Ubuntu 9.10 x64 on a quad core i7 machine and I'm on the dev branch. I
build every couple of days and if I get a build failure, I first do a
bitbake -c clean on the package that fails and then a bitbake -c build on
the same package. In most cases, the error resolves itself and then I
continue with bitbake beagleboard-demo-image.

9

I build beagleboard-demo-image from dev branch in Fedora 12 x86_64 on
core i7 PC. I got
error, does anyone have same problem?

/home/tang/Project/OE/build/tmp/staging/x86_64-linux/usr/share/
aclocal/glib-1.2.m4:8: warning: underquoted definition of AM_PATH_GLIB

/home/tang/Project/OE/build/tmp/staging/x86_64-linux/usr/share/

aclocal/glib-1.2.m4:8: run info '(automake)Extending aclocal'

/home/tang/Project/OE/build/tmp/staging/x86_64-linux/usr/share/

aclocal/glib-1.2.m4:8: or see http://sources.redhat.com/automake/automake.html#Extending-aclocal

sh: dpkg-parsechangelog: command not found
configure.ac:2: error: AC_INIT should be called with package and

version arguments

/home/tang/Project/OE/build/tmp/staging/x86_64-linux/usr/share/

aclocal-1.10/init.m4:26: AM_INIT_AUTOMAKE is expanded from...

configure.ac:2: the top level
autom4te: /home/tang/Project/OE/build/tmp/staging/x86_64-linux/usr/

bin/m4 failed with exit status: 1

aclocal: autom4te failed with exit status: 1
autoreconf: aclocal failed with exit status: 1
FATAL: autoreconf execution failed.

NOTE: Task failed: /home/tang/Project/OE/build/tmp/work/armv7a-
angstrom-linux-gnueabi/libgpsmgr-0.1-r0/temp/log.do_configure.10120
ERROR: TaskFailed event exception, aborting
ERROR: Build of /home/tang/Project/OE/openembedded/recipes/maemo4/
libgpsmgr_0.1.bb do_configure failed
ERROR: Task 6600 (/home/tang/Project/OE/openembedded/recipes/maemo4/
libgpsmgr_0.1.bb, do_configure) failed
NOTE: Tasks Summary: Attempted 2828 tasks of which 1847 didn't need to
be rerun and 1 failed.
ERROR: '/home/tang/Project/OE/openembedded/recipes/maemo4/
libgpsmgr_0.1.bb' failed

10

Wasn't that fixed yesterday: http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=d88aa38f6b3117996af10d8c5a4ea76128f3cdc0 ?

11

Thanks, Koen. It is solved, but new one comes, I just updated my dev.
branch.

/home/tang/Project/OE/build/tmp/staging/armv7a-angstrom-linux-

gnueabi/usr/lib/libmusicbrainz3.so: undefined reference to
`__cxa_guard_release@CXXABI_1.3'

/home/tang/Project/OE/build/tmp/staging/armv7a-angstrom-linux-

gnueabi/usr/lib/libmusicbrainz3.so: undefined reference to
`std::basic_string<char, std::char_traits<char>, std::allocator<char>

::_Rep::_S_empty_rep_storage@GLIBCXX_3.4'
/home/tang/Project/OE/build/tmp/staging/armv7a-angstrom-linux-

gnueabi/usr/lib/libmusicbrainz3.so: undefined reference to
`std::basic_string<char, std::char_traits<char>, std::allocator<char>

::rfind(char, unsigned int) const@GLIBCXX_3.4'
collect2: ld returned 1 exit status
make[3]: *** [gnome-mplayer] Error 1
make[3]: Leaving directory `/home/tang/Project/OE/build/tmp/work/

armv7a-angstrom-linux-gnueabi/gnome-mplayer-0.9.9-r10.0/gnome-
mplayer-0.9.9/src'

make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/tang/Project/OE/build/tmp/work/

armv7a-angstrom-linux-gnueabi/gnome-mplayer-0.9.9-r10.0/gnome-
mplayer-0.9.9/src'

make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/tang/Project/OE/build/tmp/work/

armv7a-angstrom-linux-gnueabi/gnome-mplayer-0.9.9-r10.0/gnome-
mplayer-0.9.9'

make: *** [all] Error 2
FATAL: oe_runmake failed

NOTE: Task failed: /home/tang/Project/OE/build/tmp/work/armv7a-
angstrom-linux-gnueabi/gnome-mplayer-0.9.9-r10.0/temp/log.do_compile.
20225
ERROR: TaskFailed event exception, aborting
ERROR: Build of /home/tang/Project/OE/openembedded/recipes/gnome-
mplayer/gnome-mplayer_0.9.9.bb do_compile failed
ERROR: Task 5783 (/home/tang/Project/OE/openembedded/recipes/gnome-
mplayer/gnome-mplayer_0.9.9.bb, do_compile) failed
NOTE: Tasks Summary: Attempted 5197 tasks of which 5188 didn't need to
be rerun and 1 failed.
ERROR: '/home/tang/Project/OE/openembedded/recipes/gnome-mplayer/gnome-
mplayer_0.9.9.bb' failed