Is bitbake 1.10 the latest stable version?

Is bitbake 1.10 the latest stable version?

[Elvis Dowson]

Hi,
       I was wondering if bitbake-1.10 is the latest stable version? 

best regards,

Elvis Dowson

Re: Is bitbake 1.10 the latest stable version?

[Elvis Dowson]

On Jul 31, 2010, at 11:07 AM, Elvis Dowson wrote:

> I was wondering if bitbake-1.10 is the latest stable version? 

When trying to build a recipe, e.g. omap3-console-image, with the bitbake-1.10 and the current org.openembedded.dev, the display progress format looks pretty ugly  .. 

18% 40.5K 7m45s... .........
  2050K ......... ............ ..... ........... ......... 50% 36.0K 2m47s
  5250K .... 46% 14.4K 2m20s
  1700K .................. ........ .......................... ....... 23% 16.9K 4m26s
  2700K ...... ...... .... .................... .......... ................ ..... ... ..... ..... .............. 19% 27.6K 7m39s..
  2100K ................ 50% 31.9K 2m45s
  5300K ........... 30% 16.7K 3m40s
  1450K .......... ......... ..................... ... ........ ... ...... ............ . ....... ................. ........................ ...... ...... ...................... ............. 23% 20.3K 4m28s
  2750K ... ...... .... .......... 51% 32.3K 2m43s...
  5350K ................. ..... ............. 31% 25.8K 3m34s.... 19% 21.9K 7m35s
  2150K ................ ....... 47% 13.8K 2m16s
  1750K ....
  1500K ......... ............... ..... .......... .......... .... ....... .... ......................... .. ............... ............ ... ............. 23% 27.2K 4m28s


Best regards,

Elvis Dowson

Re: Is bitbake 1.10 the latest stable version?

[Eric Bénard]

Le 31/07/2010 09:43, Elvis Dowson a écrit :
>
> On Jul 31, 2010, at 11:07 AM, Elvis Dowson wrote:
>
>> I was wondering if bitbake-1.10 is the latest stable version?
>
> When trying to build a recipe, e.g. omap3-console-image, with the bitbake-1.10 and the current org.openembedded.dev, the display progress format looks pretty ugly  ..
>
this may be because you have several BBTHREADS and thus several fetch 
running and outputing log at the same time.

Eric

Re: Is bitbake 1.10 the latest stable version?

[Frans Meulenbroeks]

2010/7/31 Elvis Dowson <elvis.dowson@mac.com>

> Hi,
>       I was wondering if bitbake-1.10 is the latest stable version?
>
> best regards,
>
>
> I'd say this the bitbake 1.10 head is the most recent version. It is the
recommended version if you want to build oe unstable head.
I would not call it the "latest stable version" though. Stable for me means
(among others) it is version tagged in git, which has not happened yet.
So y

Frans

Re: Is bitbake 1.10 the latest stable version?

[Elvis Dowson]

Hi Eric,

On Jul 31, 2010, at 2:18 PM, Eric Bénard wrote:

>> 
> this may be because you have several BBTHREADS and thus several fetch running and outputing log at the same time.
> 

With bitbake 1.8.19, I don't have that problem, as seen from the output. I have 6 threads set for make and bitbake, in the older instance, the formatting works better. 

NOTE: Unpacking /usr/share/sources/Python-2.6.1.tar.bz2 to tmp/work/x86_64-linux/python-native-2.6.1-ml8.2/
NOTE: Running task 167 of 3214 (ID: 659, /tool/overo-oe/org.openembedded.dev/recipes/util-linux-ng/util-linux-ng_2.16.bb, do_fetch)
NOTE: Running task 168 of 3214 (ID: 660, /tool/overo-oe/org.openembedded.dev/recipes/util-linux-ng/util-linux-ng_2.16.bb, do_unpack)
NOTE: Unpacking /usr/share/sources/util-linux-ng-2.16.tar.bz2 to tmp/work/armv7a-angstrom-linux-gnueabi/util-linux-ng-2.16-r9.3/
NOTE: Running task 169 of 3214 (ID: 2174, /tool/overo-oe/org.openembedded.dev/recipes/xorg-lib/libice_1.0.6.bb, do_setscene)
NOTE: Running task 170 of 3214 (ID: 2824, /tool/overo-oe/org.openembedded.dev/recipes/perl/perl-native_5.8.8.bb, do_setscene)
NOTE: Running task 171 of 3214 (ID: 2175, /tool/overo-oe/org.openembedded.dev/recipes/xorg-lib/libice_1.0.6.bb, do_fetch)
NOTE: Running task 172 of 3214 (ID: 2825, /tool/overo-oe/org.openembedded.dev/recipes/perl/perl-native_5.8.8.bb, do_fetch)
NOTE: Running task 173 of 3214 (ID: 2176, /tool/overo-oe/org.openembedded.dev/recipes/xorg-lib/libice_1.0.6.bb, do_unpack)
NOTE: Running task 174 of 3214 (ID: 2826, /tool/overo-oe/org.openembedded.dev/recipes/perl/perl-native_5.8.8.bb, do_unpack)
NOTE: Unpacking /usr/share/sources/libICE-1.0.6.tar.bz2 to tmp/work/armv7a-angstrom-linux-gnueabi/libice-1_1.0.6-r1/
NOTE: Unpacking /usr/share/sources/perl-5.8.8.tar.gz to tmp/work/x86_64-linux/perl-native-5.8.8-r15/
NOTE: Running task 175 of 3214 (ID: 2681, /tool/overo-oe/org.openembedded.dev/recipes/xorg-lib/libxdmcp_1.0.3.bb, do_setscene)
NOTE: Running task 176 of 3214 (ID: 2682, /tool/overo-oe/org.openembedded.dev/recipes/xorg-lib/libxdmcp_1.0.3.bb, do_fetch)
NOTE: Running task 177 of 3214 (ID: 2655, /tool/overo-oe/org.openembedded.dev/recipes/xorg-lib/libxau_1.0.5.bb, do_setscene)
NOTE: Running task 178 of 3214 (ID: 2683, /tool/overo-oe/org.openembedded.dev/recipes/xorg-lib/libxdmcp_1.0.3.bb, do_unpack)
NOTE: Unpacking /usr/share/sources/libXdmcp-1.0.3.tar.bz2 to tmp/work/armv7a-angstrom-linux-gnueabi/libxdmcp-1_1.0.3-r1/

Best regards,

Elvis Dowson

Re: Is bitbake 1.10 the latest stable version?

[Elvis Dowson]

Hi,
       If you ask me, updating bitbake and openembedded is bound to cause problems ! 

I was running bitbake 1.8 and oe from about 3 months ago, but when I tried updating it to bitbake 1.10 and did an update of my oe repo, I had failures for glibc,  complaining about LD_LIBRARY_PATH being set to the current directory. 

It is not the first time that this is happening, everytime you do an update of the oe repository, things start going wrong and you usually have to spend a whole week trying to fix things. 

Luckily for me, I had a backup copy of my Fedora 12 x86 64-bit virtual machine, and now have switch to the older repository and working revision. 

The resulting outputs of the OE build system are reproduceable, but OE behaviour by itself  across revisions is not. 

Best regards,

Elvis Dowson

Re: Is bitbake 1.10 the latest stable version?

[Khem Raj]

On Sat, Jul 31, 2010 at 4:35 AM, Elvis Dowson <elvis.dowson@mac.com> wrote:
> Hi,
>       If you ask me, updating bitbake and openembedded is bound to cause problems !
>
> I was running bitbake 1.8 and oe from about 3 months ago, but when I tried updating it to bitbake 1.10 and did an update of my oe repo, I had failures for glibc,  complaining about LD_LIBRARY_PATH being set to the current directory.
>
> It is not the first time that this is happening, everytime you do an update of the oe repository, things start going wrong and you usually have to spend a whole week trying to fix things.
>
> Luckily for me, I had a backup copy of my Fedora 12 x86 64-bit virtual machine, and now have switch to the older repository and working revision.
>
> The resulting outputs of the OE build system are reproduceable, but OE behaviour by itself  across revisions is not.

if you use development branch then be ready to bear these kind of
issues occasionally otherwise use stable branch and in general OE
master is a lot better in consistency compared to many other projects

>
> Best regards,
>
> Elvis Dowson
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: Is bitbake 1.10 the latest stable version?

[Eric Bénard]

Hi elvis,

Le 31/07/2010 13:24, Elvis Dowson a écrit :
> On Jul 31, 2010, at 2:18 PM, Eric Bénard wrote:
>
>>>
>> this may be because you have several BBTHREADS and thus several fetch running and outputing log at the same time.
>>
>
> With bitbake 1.8.19, I don't have that problem, as seen from the output. I have 6 threads set for make and bitbake, in the older instance, the formatting works better.
>
> NOTE: Unpacking /usr/share/sources/Python-2.6.1.tar.bz2 to tmp/work/x86_64-linux/python-native-2.6.1-ml8.2/
> NOTE: Running task 167 of 3214 (ID: 659, /tool/overo-oe/org.openembedded.dev/recipes/util-linux-ng/util-linux-ng_2.16.bb, do_fetch)
> NOTE: Running task 168 of 3214 (ID: 660, /tool/overo-oe/org.openembedded.dev/recipes/util-linux-ng/util-linux-ng_2.16.bb, do_unpack)
> NOTE: Unpacking /usr/share/sources/util-linux-ng-2.16.tar.bz2 to tmp/work/armv7a-angstrom-linux-gnueabi/util-linux-ng-2.16-r9.3/
> NOTE: Running task 169 of 3214 (ID: 2174, /tool/overo-oe/org.openembedded.dev/recipes/xorg-lib/libice_1.0.6.bb, do_setscene)
> NOTE: Running task 170 of 3214 (ID: 2824, /tool/overo-oe/org.openembedded.dev/recipes/perl/perl-native_5.8.8.bb, do_setscene)
> NOTE: Running task 171 of 3214 (ID: 2175, /tool/overo-oe/org.openembedded.dev/recipes/xorg-lib/libice_1.0.6.bb, do_fetch)
> NOTE: Running task 172 of 3214 (ID: 2825, /tool/overo-oe/org.openembedded.dev/recipes/perl/perl-native_5.8.8.bb, do_fetch)
> NOTE: Running task 173 of 3214 (ID: 2176, /tool/overo-oe/org.openembedded.dev/recipes/xorg-lib/libice_1.0.6.bb, do_unpack)
> NOTE: Running task 174 of 3214 (ID: 2826, /tool/overo-oe/org.openembedded.dev/recipes/perl/perl-native_5.8.8.bb, do_unpack)
> NOTE: Unpacking /usr/share/sources/libICE-1.0.6.tar.bz2 to tmp/work/armv7a-angstrom-linux-gnueabi/libice-1_1.0.6-r1/
> NOTE: Unpacking /usr/share/sources/perl-5.8.8.tar.gz to tmp/work/x86_64-linux/perl-native-5.8.8-r15/
> NOTE: Running task 175 of 3214 (ID: 2681, /tool/overo-oe/org.openembedded.dev/recipes/xorg-lib/libxdmcp_1.0.3.bb, do_setscene)
> NOTE: Running task 176 of 3214 (ID: 2682, /tool/overo-oe/org.openembedded.dev/recipes/xorg-lib/libxdmcp_1.0.3.bb, do_fetch)
> NOTE: Running task 177 of 3214 (ID: 2655, /tool/overo-oe/org.openembedded.dev/recipes/xorg-lib/libxau_1.0.5.bb, do_setscene)
> NOTE: Running task 178 of 3214 (ID: 2683, /tool/overo-oe/org.openembedded.dev/recipes/xorg-lib/libxdmcp_1.0.3.bb, do_unpack)
> NOTE: Unpacking /usr/share/sources/libXdmcp-1.0.3.tar.bz2 to tmp/work/armv7a-angstrom-linux-gnueabi/libxdmcp-1_1.0.3-r1/
>
try fetching several packages with bitbake 1.8.19 to have a real vs your 
previous mail (I think the log comes from the program who fetch the 
file, not from bitbake so you may get the same mixed log while several 
files are fetched at the same time)

Eric