* problems with bitbake
@ 2008-06-18 15:12 Luís Vitório Cargnini
2008-06-18 15:25 ` Michael 'Mickey' Lauer
0 siblings, 1 reply; 8+ messages in thread
From: Luís Vitório Cargnini @ 2008-06-18 15:12 UTC (permalink / raw)
To: openembedded-devel, angstrom-distro-devel
Dear fellows:
I'm restarting the development process based on openembedded with
angstrom distro, after reconfiguring a new machine (ubuntu 8.04) to
work properly I did the following:
bitbake base-image ; bitbake console-image ; bitbake x11-image
and get the following errors:
ERROR: no files to build.
NOTE: Parsing finished. 0 cached, 0 parsed, 0 skipped, 0 masked.
NOTE: build 200806181208: started
NOTE: <type 'exceptions.IndexError'>:list index out of range while evaluating:
${@base_get_metadata_monotone_revision(d)}
Traceback (most recent call last):
File "/usr/bin/bitbake", line 134, in <module>
main()
File "/usr/bin/bitbake", line 131, in main
cooker.cook()
File "/var/lib/python-support/python2.5/bb/cooker.py", line 600, in cook
return self.buildTargets(pkgs_to_build)
File "/var/lib/python-support/python2.5/bb/cooker.py", line 496, in
buildTargets
bb.event.fire(bb.event.BuildStarted(buildname, targets,
self.configuration.event_data))
File "/var/lib/python-support/python2.5/bb/event.py", line 67, in fire
if tmpHandler(event) == Handled:
File "tmpHandler(e)", line 31, in tmpHandler
File "/var/lib/python-support/python2.5/bb/data.py", line 97, in getVar
return d.getVar(var,exp)
File "/var/lib/python-support/python2.5/bb/data_smart.py", line 170, in getVar
return self.expand(value,var)
File "/var/lib/python-support/python2.5/bb/data_smart.py", line 85, in expand
s = __expand_python_regexp__.sub(python_sub, s)
File "/var/lib/python-support/python2.5/bb/data_smart.py", line 71,
in python_sub
s = eval(code)
File "<string>", line 1, in <module>
File "<bb>", line 4, in base_get_metadata_monotone_revision
File "<bb>", line 4, in base_get_scmbasepath
IndexError: list index out of range
ERROR: no files to build.
NOTE: Parsing finished. 0 cached, 0 parsed, 0 skipped, 0 masked.
NOTE: build 200806181209: started
NOTE: <type 'exceptions.IndexError'>:list index out of range while evaluating:
${@base_get_metadata_monotone_revision(d)}
Traceback (most recent call last):
File "/usr/bin/bitbake", line 134, in <module>
main()
File "/usr/bin/bitbake", line 131, in main
cooker.cook()
File "/var/lib/python-support/python2.5/bb/cooker.py", line 600, in cook
return self.buildTargets(pkgs_to_build)
File "/var/lib/python-support/python2.5/bb/cooker.py", line 496, in
buildTargets
bb.event.fire(bb.event.BuildStarted(buildname, targets,
self.configuration.event_data))
File "/var/lib/python-support/python2.5/bb/event.py", line 67, in fire
if tmpHandler(event) == Handled:
File "tmpHandler(e)", line 31, in tmpHandler
File "/var/lib/python-support/python2.5/bb/data.py", line 97, in getVar
return d.getVar(var,exp)
File "/var/lib/python-support/python2.5/bb/data_smart.py", line 170, in getVar
return self.expand(value,var)
File "/var/lib/python-support/python2.5/bb/data_smart.py", line 85, in expand
s = __expand_python_regexp__.sub(python_sub, s)
File "/var/lib/python-support/python2.5/bb/data_smart.py", line 71,
in python_sub
s = eval(code)
File "<string>", line 1, in <module>
File "<bb>", line 4, in base_get_metadata_monotone_revision
File "<bb>", line 4, in base_get_scmbasepath
IndexError: list index out of range
ERROR: no files to build.
NOTE: Parsing finished. 0 cached, 0 parsed, 0 skipped, 0 masked.
NOTE: build 200806181209: started
NOTE: <type 'exceptions.IndexError'>:list index out of range while evaluating:
${@base_get_metadata_monotone_revision(d)}
Traceback (most recent call last):
File "/usr/bin/bitbake", line 134, in <module>
main()
File "/usr/bin/bitbake", line 131, in main
cooker.cook()
File "/var/lib/python-support/python2.5/bb/cooker.py", line 600, in cook
return self.buildTargets(pkgs_to_build)
File "/var/lib/python-support/python2.5/bb/cooker.py", line 496, in
buildTargets
bb.event.fire(bb.event.BuildStarted(buildname, targets,
self.configuration.event_data))
File "/var/lib/python-support/python2.5/bb/event.py", line 67, in fire
if tmpHandler(event) == Handled:
File "tmpHandler(e)", line 31, in tmpHandler
File "/var/lib/python-support/python2.5/bb/data.py", line 97, in getVar
return d.getVar(var,exp)
File "/var/lib/python-support/python2.5/bb/data_smart.py", line 170, in getVar
return self.expand(value,var)
File "/var/lib/python-support/python2.5/bb/data_smart.py", line 85, in expand
s = __expand_python_regexp__.sub(python_sub, s)
File "/var/lib/python-support/python2.5/bb/data_smart.py", line 71,
in python_sub
s = eval(code)
File "<string>", line 1, in <module>
File "<bb>", line 4, in base_get_metadata_monotone_revision
File "<bb>", line 4, in base_get_scmbasepath
IndexError: list index out of range
lvcargnini@protheus:~/instramed/openembedded$
my local.conf is the following:
# Use this to specify where BitBake should place the downloaded sources into
DL_DIR = "${HOME}/instramed/openembedded/sources"
# Delete the line below. Then specify which .bb files to consider for
# your build. Typically this will be something like BBFILES =
"/path/to/openembedded/packages/*/*.bb"
BBFILES := "${HOME}/instramed/org.openembedded.dev/packages/*/*.bb"
BBMASK = ""
TMPDIR = ${HOME}/instramed/openembedded/tmp
TARGET_OS = "linux"
DISTRO = "angstrom-2008.1"
MACHINE = "omap5912osk"
# 'uclibc' or 'glibc' or 'eglibc'
# ANGSTROM_MODE = "glibc"
INHERIT = "package_ipk"
# INHERIT = "package_tar"
# Add the required image file system types below. Valid are
# jffs2, tar(.gz|bz2), cpio(.gz), cramfs, ext2(.gz), ext3(.gz)
# squashfs, squashfs-lzma
IMAGE_FSTYPES = "jffs2 tar.bz2 cramfs"
# Uncomment this to disable the parse cache (not recommended).
# CACHE = ""
# Uncomment this if you want BitBake to emit debugging output
# BBDEBUG = "yes"
# Uncomment these two if you want BitBake to build images useful for debugging.
# PROFILE_OPTIMIZATION = "-pg"
# SELECTED_OPTIMIZATION = "${PROFILE_OPTIMIZATION}"
# LDFLAGS =+ "-pg"
# Uncomment this if you want BitBake to emit the log if a build fails.
BBINCLUDELOGS = "yes"
Please any help will be welcome
Thanks.
-
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: problems with bitbake
2008-06-18 15:12 problems with bitbake Luís Vitório Cargnini
@ 2008-06-18 15:25 ` Michael 'Mickey' Lauer
2008-06-18 16:56 ` [Angstrom-devel] " Luís Vitório Cargnini
0 siblings, 1 reply; 8+ messages in thread
From: Michael 'Mickey' Lauer @ 2008-06-18 15:25 UTC (permalink / raw)
To: openembedded-devel; +Cc: angstrom-distro-devel
Am Mittwoch 18 Juni 2008 17:12:53 schrieb Luís Vitório Cargnini:
> Dear fellows:
>
> I'm restarting the development process based on openembedded with
> angstrom distro, after reconfiguring a new machine (ubuntu 8.04) to
> work properly I did the following:
> bitbake base-image ; bitbake console-image ; bitbake x11-image
>
> and get the following errors:
>
> ERROR: no files to build.
This almost always is a problem of BBFILES or BBPATH settings. Since your
BBFILES seems to be set (double check whether the regex is valid), double
check whether BBPATH points to the proper directories, so that Bitbake
actually has a chance to find your local.conf and its bitbake.conf.
--
:M:
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Angstrom-devel] problems with bitbake
2008-06-18 15:25 ` Michael 'Mickey' Lauer
@ 2008-06-18 16:56 ` Luís Vitório Cargnini
2008-06-18 17:31 ` Michael 'Mickey' Lauer
` (2 more replies)
0 siblings, 3 replies; 8+ messages in thread
From: Luís Vitório Cargnini @ 2008-06-18 16:56 UTC (permalink / raw)
To: angstrom-distro-devel; +Cc: openembedded-devel
I did as you said, I finded the error in expression regular, the error
was in BBFILES I fixed it
but the error now is:
lvcargnini@protheus:~/instramed/openembedded$ bitbake nano
ERROR: Openembedded's config sanity checker detected a potential
misconfiguration.
Either fix the cause of this error or at your own risk disable the
checker (see sanity.conf).
Following is the list of potential problems / advisories:
Please set TARGET_ARCH directly, or choose a MACHINE or DISTRO that does so.
Please set TARGET_OS directly, or choose a MACHINE or DISTRO that does so.
DISTRO 'None' not found. Please set a valid DISTRO in your local.conf
On Wed, Jun 18, 2008 at 12:25 PM, Michael 'Mickey' Lauer
<mickey@vanille-media.de> wrote:
> Am Mittwoch 18 Juni 2008 17:12:53 schrieb Luís Vitório Cargnini:
>> Dear fellows:
>>
>> I'm restarting the development process based on openembedded with
>> angstrom distro, after reconfiguring a new machine (ubuntu 8.04) to
>> work properly I did the following:
>> bitbake base-image ; bitbake console-image ; bitbake x11-image
>>
>> and get the following errors:
>>
>> ERROR: no files to build.
>
> This almost always is a problem of BBFILES or BBPATH settings. Since your
> BBFILES seems to be set (double check whether the regex is valid), double
> check whether BBPATH points to the proper directories, so that Bitbake
> actually has a chance to find your local.conf and its bitbake.conf.
>
> --
> :M:
>
> _______________________________________________
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
>
--
------------------------------------------------------------------------------
Thanks && Regards
M.Sc. B.Sc. Luís Vitório Cargnini
IEEE Member
Electrical Engineer Faculty @ PUCRS
Ipiranga Avenue, 6681 – Building 30
P.O. Box: 90619-900 – Porto Alegre/RS
Phone: +55 51 3320 3500 extension: 7696
---------------------------------------------------------------------------------
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Angstrom-devel] problems with bitbake
2008-06-18 16:56 ` [Angstrom-devel] " Luís Vitório Cargnini
@ 2008-06-18 17:31 ` Michael 'Mickey' Lauer
2008-06-18 17:48 ` Luís Vitório Cargnini
2008-06-18 17:40 ` Alain M.
2008-06-18 17:50 ` Rolf Leggewie
2 siblings, 1 reply; 8+ messages in thread
From: Michael 'Mickey' Lauer @ 2008-06-18 17:31 UTC (permalink / raw)
To: angstrom-distro-devel, lvcargnini; +Cc: openembedded-devel
Am Mittwoch 18 Juni 2008 18:56:45 schrieb Luís Vitório Cargnini:
> I did as you said, I finded the error in expression regular, the error
> was in BBFILES I fixed it
> but the error now is:
>
>
> lvcargnini@protheus:~/instramed/openembedded$ bitbake nano
> ERROR: Openembedded's config sanity checker detected a potential
> misconfiguration.
> Either fix the cause of this error or at your own risk disable the
> checker (see sanity.conf).
> Following is the list of potential problems / advisories:
>
> Please set TARGET_ARCH directly, or choose a MACHINE or DISTRO that does
> so. Please set TARGET_OS directly, or choose a MACHINE or DISTRO that does
> so. DISTRO 'None' not found. Please set a valid DISTRO in your local.conf
This indicates that it does not find all configuration files. Doublecheck your
value of BBPATH and run bitbake -v -v -v to give us more debug output.
:M:
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Angstrom-devel] problems with bitbake
2008-06-18 16:56 ` [Angstrom-devel] " Luís Vitório Cargnini
2008-06-18 17:31 ` Michael 'Mickey' Lauer
@ 2008-06-18 17:40 ` Alain M.
2008-06-18 17:50 ` Rolf Leggewie
2 siblings, 0 replies; 8+ messages in thread
From: Alain M. @ 2008-06-18 17:40 UTC (permalink / raw)
To: openembedded-devel
I would like to ask you to kindly send the fix here on the list, I will
do the same on ubuntu 8.04 in a few weeks and it will be of great value
to me :)
Thanks,
Alain
Luís Vitório Cargnini escreveu:
> I did as you said, I finded the error in expression regular, the error
> was in BBFILES I fixed it
> but the error now is:
>
>
> lvcargnini@protheus:~/instramed/openembedded$ bitbake nano
> ERROR: Openembedded's config sanity checker detected a potential
> misconfiguration.
> Either fix the cause of this error or at your own risk disable the
> checker (see sanity.conf).
> Following is the list of potential problems / advisories:
>
> Please set TARGET_ARCH directly, or choose a MACHINE or DISTRO that does so.
> Please set TARGET_OS directly, or choose a MACHINE or DISTRO that does so.
> DISTRO 'None' not found. Please set a valid DISTRO in your local.conf
>
>
> On Wed, Jun 18, 2008 at 12:25 PM, Michael 'Mickey' Lauer
> <mickey@vanille-media.de> wrote:
>> Am Mittwoch 18 Juni 2008 17:12:53 schrieb Luís Vitório Cargnini:
>>> Dear fellows:
>>>
>>> I'm restarting the development process based on openembedded with
>>> angstrom distro, after reconfiguring a new machine (ubuntu 8.04) to
>>> work properly I did the following:
>>> bitbake base-image ; bitbake console-image ; bitbake x11-image
>>>
>>> and get the following errors:
>>>
>>> ERROR: no files to build.
>> This almost always is a problem of BBFILES or BBPATH settings. Since your
>> BBFILES seems to be set (double check whether the regex is valid), double
>> check whether BBPATH points to the proper directories, so that Bitbake
>> actually has a chance to find your local.conf and its bitbake.conf.
>>
>> --
>> :M:
>>
>> _______________________________________________
>> Angstrom-distro-devel mailing list
>> Angstrom-distro-devel@linuxtogo.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
>>
>
>
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Angstrom-devel] problems with bitbake
2008-06-18 17:31 ` Michael 'Mickey' Lauer
@ 2008-06-18 17:48 ` Luís Vitório Cargnini
[not found] ` <a7f8874a0806181100q2981dd42ke57a69cafd1bc607@mail.gmail.com>
0 siblings, 1 reply; 8+ messages in thread
From: Luís Vitório Cargnini @ 2008-06-18 17:48 UTC (permalink / raw)
To: Michael 'Mickey' Lauer; +Cc: openembedded-devel, angstrom-distro-devel
I fixed this issue exporting all the variables of the local.conf as
env vars inside bash
#OpenEmbedded
export BBPATH=$HOME/instramed/openembedded:$HOME/instramed/openembedded/build:$HOME/instramed/openembedded/org.openembedded.dev
export PKGDIR=$HOME/instramed/openembedded/build/
export BBFILES="$HOME/instramed/openembedded/org.openembedded.dev/packages/*/*.bb"
export DISTRO="angstrom-2008.1"
export MACHINE="omap5912osk"
export INHERIT="package_ipk"
export IMAGE_FSTYPES="jffs2 tar.bz2 cramfs squashfs"
export BBINCLUDELOGS="yes"
and it seems to be working
doing bitbake -v -v -v without the env vars:
bitbake -v -v -v base-image
lvcargnini@protheus:~/instramed/openembedded$ bitbake -v -v -v base-image
ERROR: no files to build.
NOTE: Parsing finished. 0 cached, 0 parsed, 0 skipped, 0 masked.
NOTE: build 200806181443: started
NOTE: <type 'exceptions.IndexError'>:list index out of range while evaluating:
${@base_get_metadata_monotone_revision(d)}
Traceback (most recent call last):
File "/usr/bin/bitbake", line 134, in <module>
main()
File "/usr/bin/bitbake", line 131, in main
cooker.cook()
File "/var/lib/python-support/python2.5/bb/cooker.py", line 600, in cook
return self.buildTargets(pkgs_to_build)
File "/var/lib/python-support/python2.5/bb/cooker.py", line 496, in
buildTargets
bb.event.fire(bb.event.BuildStarted(buildname, targets,
self.configuration.event_data))
File "/var/lib/python-support/python2.5/bb/event.py", line 67, in fire
if tmpHandler(event) == Handled:
File "tmpHandler(e)", line 31, in tmpHandler
File "/var/lib/python-support/python2.5/bb/data.py", line 97, in getVar
return d.getVar(var,exp)
File "/var/lib/python-support/python2.5/bb/data_smart.py", line 170, in getVar
return self.expand(value,var)
File "/var/lib/python-support/python2.5/bb/data_smart.py", line 85, in expand
s = __expand_python_regexp__.sub(python_sub, s)
File "/var/lib/python-support/python2.5/bb/data_smart.py", line 71,
in python_sub
s = eval(code)
File "<string>", line 1, in <module>
File "<bb>", line 4, in base_get_metadata_monotone_revision
File "<bb>", line 4, in base_get_scmbasepath
IndexError: list index out of range
lvcargnini@protheus:~/instramed/openembedded$
with env vars:
lvcargnini@protheus:~/instramed/openembedded$ bitbake -v -v -v base-image
NOTE: Handling BitBake files: \ (5582/5582) [100 %]
NOTE: Parsing finished. 529 cached, 4815 parsed, 238 skipped, 0 masked.
NOTE: build 200806181444: started
OE Build Configuration:
BB_VERSION = "1.8.10"
METADATA_BRANCH = "org.openembedded.dev"
METADATA_REVISION = "a45026d1f7e19f4cc183bd7a76768f689c18d410"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "omap5912osk"
DISTRO = "angstrom"
DISTRO_VERSION = "2008.1-test-20080618"
TARGET_FPU = "soft"
NOTE: Resolving any missing task queue dependencies
NOTE: selecting gcc-cross to satisfy
virtual/arm-angstrom-linux-gnueabi-gcc due to PREFERRED_PROVIDERS
NOTE: selecting glibc to satisfy virtual/libc due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel due to PREFERRED_PROVIDERS
NOTE: multiple providers are available for runtime update-alternatives
(update-alternatives-cworth, update-alternatives-dpkg);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime
update-alternatives
NOTE: selecting gcc-cross to satisfy runtime libgcc due to PREFERRED_PROVIDERS
NOTE: selecting glibc to satisfy runtime libsegfault due to PREFERRED_PROVIDERS
NOTE: selecting linux-libc-headers to satisfy runtime
linux-libc-headers-dev due to PREFERRED_PROVIDERS
NOTE: selecting glibc to satisfy runtime glibc due to PREFERRED_PROVIDERS
NOTE: multiple providers are available for runtime util-linux-mount
(util-linux, util-linux-ng);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime
util-linux-mount
NOTE: multiple providers are available for runtime util-linux-umount
(util-linux, util-linux-ng);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime
util-linux-umount
NOTE: selecting bluez-utils to satisfy runtime bluez-utils due to
PREFERRED_PROVIDERS
NOTE: selecting bluez-utils to satisfy runtime bluez-utils-compat due
to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime
kernel-module-crypto_algapi due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-zd1211rw
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime
kernel-module-ieee80211-crypt due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime
kernel-module-ieee80211-crypt-tkip due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-aes due
to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-ecb due
to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime
kernel-module-michael-mic due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime
kernel-module-ieee80211-crypt-wep due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-cryptomgr
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime
kernel-module-ieee80211-crypt-ccmp due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-arc4 due
to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-cifs due
to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-smbfs due
to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-vfat due
to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-af-packet
due to PREFERRED_PROVIDERS
NOTE: selecting avahi to satisfy runtime avahi-autoipd due to
PREFERRED_PROVIDERS
NOTE: selecting avahi to satisfy runtime avahi-daemon due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-ext2 due
to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-nfs due
to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime
kernel-module-spectrum-cs due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-serial-cs
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-hostap-cs
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-airo-cs
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-pcnet-cs
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-ide-disk
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-pcmcia
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-ide-cs
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-bnep due
to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime
kernel-module-bluetoothuart-cs due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime
kernel-module-bluetooth3c-cs due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-bluetooth
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-hci-usb
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-rfcomm
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-sco due
to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-hci-uart
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-dtl1-cs
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime
kernel-module-bluecard-cs due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-hci-vhci
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-hidp due
to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-l2cap due
to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime
kernel-module-ppp-deflate due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-ppp-async
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-ppp-mppe
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-usbmouse
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-mousedev
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-scsi-mod
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-uhci-hcd
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-usbhid
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime
kernel-module-usb-storage due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-usbcore
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-ohci-hcd
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-ehci-hcd
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-sd-mod
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-usbnet
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-usbserial
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime
kernel-module-snd-pcm-oss due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime
kernel-module-snd-mixer-oss due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-rtc-sysfs
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-rtc-proc
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-nls-utf8
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-rtc-dev
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-input due
to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-unix due
to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-uinput
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime
kernel-module-rtc-sa1100 due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-ide-core
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-nls-base
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-module-nls-cp437
due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime
kernel-module-nls-iso8859-1 due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime
kernel-module-snd-omap-alsa-aic23 due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime
kernel-module-tlv320aic23 due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy virtual/kernel due to PREFERRED_PROVIDERS
NOTE: preferred version 2.6.1 of glibc not available (for item
virtual/arm-angstrom-linux-gnueabi-libc-for-gcc)
NOTE: selecting glibc-intermediate to satisfy
virtual/arm-angstrom-linux-gnueabi-libc-for-gcc due to
PREFERRED_PROVIDERS
NOTE: selecting binutils-cross to satisfy
virtual/arm-angstrom-linux-gnueabi-binutils due to PREFERRED_PROVIDERS
NOTE: selecting linux-libc-headers to satisfy linux-libc-headers due
to PREFERRED_PROVIDERS
NOTE: selecting qemu-native to satisfy qemu-native due to PREFERRED_PROVIDERS
NOTE: Nothing PROVIDES 'virtual/arm-angstrom-linux-gnueabi-gcc-2.95'
(but '['/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/linux/poodle-kernel-2.4-embedix.bb',
'/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/linux/shepherd-kernel-2.4-embedix.bb',
'/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/linux/corgi-kernel-2.4-embedix.bb',
'/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/linux/poodle255-kernel-2.4-embedix.bb',
'/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/linux/husky-kernel-2.4-embedix.bb']'
DEPENDS on or otherwise requires it)
NOTE: Target 'virtual/arm-angstrom-linux-gnueabi-gcc-2.95' is
unbuildable, removing...
Missing or unbuildable dependency chain was:
['virtual/arm-angstrom-linux-gnueabi-gcc-2.95']
NOTE: selecting glibc to satisfy virtual/libintl due to PREFERRED_PROVIDERS
NOTE: selecting linux-omap1 to satisfy runtime kernel-base due to
PREFERRED_PROVIDERS
NOTE: multiple providers are available for runtime util-linux-losetup
(util-linux, util-linux-ng);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime
util-linux-losetup
NOTE: multiple providers are available for runtime
util-linux-swaponoff (util-linux, util-linux-ng);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime
util-linux-swaponoff
NOTE: multiple providers are available for runtime util-linux-cfdisk
(util-linux, util-linux-ng);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime
util-linux-cfdisk
NOTE: multiple providers are available for runtime util-linux-fdisk
(util-linux, util-linux-ng);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime
util-linux-fdisk
NOTE: multiple providers are available for runtime
util-linux-readprofile (util-linux, util-linux-ng);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime
util-linux-readprofile
NOTE: multiple providers are available for runtime util-linux-sfdisk
(util-linux, util-linux-ng);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime
util-linux-sfdisk
NOTE: selecting avahi to satisfy runtime avahi due to PREFERRED_PROVIDERS
NOTE: No buildable provider PROVIDES 'corgi-kernel-2.4-embedix' but
'['/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/linux/c7x0-kernels-2.4-embedix.bb']'
DEPENDS on or otherwise requires it. Enable debugging and see earlier
logs to find unbuildable providers.
NOTE: Target 'corgi-kernel-2.4-embedix' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['corgi-kernel-2.4-embedix']
NOTE: No buildable provider PROVIDES 'shepherd-kernel-2.4-embedix' but
'['/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/linux/c7x0-kernels-2.4-embedix.bb']'
DEPENDS on or otherwise requires it. Enable debugging and see earlier
logs to find unbuildable providers.
NOTE: Target 'shepherd-kernel-2.4-embedix' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['shepherd-kernel-2.4-embedix']
NOTE: No buildable provider PROVIDES 'husky-kernel-2.4-embedix' but
'['/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/linux/c7x0-kernels-2.4-embedix.bb']'
DEPENDS on or otherwise requires it. Enable debugging and see earlier
logs to find unbuildable providers.
NOTE: Target 'husky-kernel-2.4-embedix' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['husky-kernel-2.4-embedix']
NOTE: Nothing PROVIDES 'openzaurus-sa' (but
'['/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/linux/collie-kernels-2.4-embedix.bb']'
DEPENDS on or otherwise requires it)
NOTE: Target 'openzaurus-sa' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['openzaurus-sa']
NOTE: selecting gcc-cross-initial to satisfy
virtual/arm-angstrom-linux-gnueabi-gcc-initial due to
PREFERRED_PROVIDERS
NOTE: selecting glibc to satisfy virtual/libiconv due to PREFERRED_PROVIDERS
NOTE: selecting db to satisfy virtual/db due to PREFERRED_PROVIDERS
NOTE: selecting dbus-glib to satisfy dbus-glib due to PREFERRED_PROVIDERS
NOTE: selecting gtk+ to satisfy gtk+ due to PREFERRED_PROVIDERS
NOTE: multiple providers are available for runtime python-threading
(python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime
python-threading
NOTE: multiple providers are available for runtime python-core
(python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime python-core
NOTE: multiple providers are available for runtime python-io (python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime python-io
NOTE: multiple providers are available for runtime python-logging
(python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime
python-logging
NOTE: multiple providers are available for runtime python-xml (python,
python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime python-xml
NOTE: multiple providers are available for runtime python-stringold
(python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime
python-stringold
NOTE: multiple providers are available for runtime python-shell
(python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime python-shell
NOTE: multiple providers are available for runtime python-lang
(python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime python-lang
NOTE: selecting db to satisfy runtime db due to PREFERRED_PROVIDERS
NOTE: multiple providers are available for runtime python-re (python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime python-re
NOTE: multiple providers are available for runtime python-codecs
(python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime
python-codecs
NOTE: multiple providers are available for runtime python-math
(python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime python-math
NOTE: multiple providers are available for runtime python-zlib
(python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime python-zlib
NOTE: multiple providers are available for runtime python-netserver
(python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime
python-netserver
NOTE: multiple providers are available for runtime python-image
(python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime python-image
NOTE: multiple providers are available for runtime python-mime
(python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime python-mime
NOTE: multiple providers are available for runtime python-audio
(python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime python-audio
NOTE: multiple providers are available for runtime python-email
(python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime python-email
NOTE: multiple providers are available for runtime python-datetime
(python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime
python-datetime
NOTE: multiple providers are available for runtime python-crypt
(python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime python-crypt
NOTE: multiple providers are available for runtime python-netclient
(python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime
python-netclient
NOTE: multiple providers are available for runtime python-fcntl
(python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime python-fcntl
NOTE: multiple providers are available for runtime python-pickle
(python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime
python-pickle
NOTE: multiple providers are available for runtime python-tkinter
(python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime
python-tkinter
NOTE: multiple providers are available for runtime python-readline
(python, python24);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime
python-readline
NOTE: selecting dbus-glib to satisfy runtime dbus-glib due to
PREFERRED_PROVIDERS
NOTE: selecting gtk+ to satisfy runtime gtk+ due to PREFERRED_PROVIDERS
NOTE: selecting gtk+ to satisfy runtime gdk-pixbuf-loader-png due to
PREFERRED_PROVIDERS
NOTE: selecting gtk+ to satisfy runtime gdk-pixbuf-loader-jpeg due to
PREFERRED_PROVIDERS
NOTE: selecting gtk+ to satisfy runtime gdk-pixbuf-loader-xpm due to
PREFERRED_PROVIDERS
NOTE: selecting glibc to satisfy runtime glibc-gconv-iso8859-1 due to
PREFERRED_PROVIDERS
NOTE: selecting gtk+ to satisfy runtime gdk-pixbuf-loader-gif due to
PREFERRED_PROVIDERS
NOTE: selecting db-native to satisfy virtual/db-native due to
PREFERRED_PROVIDERS
NOTE: selecting gconf-dbus to satisfy gconf due to PREFERRED_PROVIDERS
NOTE: selecting libxcursor to satisfy libxcursor due to PREFERRED_PROVIDERS
NOTE: selecting libxext to satisfy libxext due to PREFERRED_PROVIDERS
NOTE: selecting gconf-dbus to satisfy runtime gconf-dbus due to
PREFERRED_PROVIDERS
NOTE: selecting gconf-dbus to satisfy runtime gconf due to PREFERRED_PROVIDERS
NOTE: selecting libxcursor to satisfy runtime libxcursor due to
PREFERRED_PROVIDERS
NOTE: selecting libxext to satisfy runtime libxext due to PREFERRED_PROVIDERS
NOTE: selecting libxt to satisfy libxt due to PREFERRED_PROVIDERS
NOTE: selecting libx11 to satisfy virtual/libx11 due to PREFERRED_PROVIDERS
NOTE: selecting libxfixes to satisfy libxfixes due to PREFERRED_PROVIDERS
NOTE: selecting libxrender to satisfy libxrender due to PREFERRED_PROVIDERS
NOTE: selecting libsm to satisfy libsm due to PREFERRED_PROVIDERS
NOTE: selecting libxft to satisfy libxft due to PREFERRED_PROVIDERS
NOTE: selecting xproto to satisfy xproto due to PREFERRED_PROVIDERS
NOTE: selecting libxt to satisfy runtime libxt due to PREFERRED_PROVIDERS
NOTE: selecting libx11 to satisfy runtime libx11 due to PREFERRED_PROVIDERS
NOTE: selecting libxfixes to satisfy runtime libxfixes due to
PREFERRED_PROVIDERS
NOTE: selecting libxrender to satisfy runtime libxrender due to
PREFERRED_PROVIDERS
NOTE: selecting libsm to satisfy runtime libsm due to PREFERRED_PROVIDERS
NOTE: selecting libxft to satisfy runtime libxft due to PREFERRED_PROVIDERS
NOTE: selecting xproto to satisfy runtime xproto due to PREFERRED_PROVIDERS
NOTE: selecting libice to satisfy libice due to PREFERRED_PROVIDERS
NOTE: selecting libice to satisfy runtime libice due to PREFERRED_PROVIDERS
NOTE: Preparing runqueue
NOTE: Marking Active Tasks
NOTE: Pruned 4352 inactive tasks, 1632 left
NOTE: Assign Weightings
NOTE: Compute totals (have 1 endpoint(s))
NOTE: Executing runqueue
NOTE: Running task 1 of 1632 (ID: 26,
/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/shasum/shasum-native.bb,
do_setscene)
NOTE: package shasum-native-1.0: started
NOTE: package shasum-native-1.0-r1: task do_setscene: started
NOTE: package shasum-native-1.0-r1: task do_setscene: completed
NOTE: package shasum-native-1.0: completed
NOTE: Running task 2 of 1632 (ID: 27,
/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/shasum/shasum-native.bb,
do_fetch)
NOTE: package shasum-native-1.0: started
NOTE: package shasum-native-1.0-r1: task do_fetch: started
NOTE: package shasum-native-1.0-r1: task do_fetch: completed
NOTE: package shasum-native-1.0: completed
NOTE: Running task 3 of 1632 (ID: 25,
/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/shasum/shasum-native.bb,
do_unpack)
NOTE: package shasum-native-1.0: started
NOTE: package shasum-native-1.0-r1: task do_unpack: started
NOTE: Unpacking
/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/shasum/files/main.c
to /home/lvcargnini/instramed/openembedded/tmp/work/i686-linux/shasum-native-1.0-r1/
NOTE: Unpacking
/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/shasum/files/mhash_sha256.h
to /home/lvcargnini/instramed/openembedded/tmp/work/i686-linux/shasum-native-1.0-r1/
NOTE: Unpacking
/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/shasum/files/sha256.c
to /home/lvcargnini/instramed/openembedded/tmp/work/i686-linux/shasum-native-1.0-r1/
NOTE: package shasum-native-1.0-r1: task do_unpack: completed
NOTE: package shasum-native-1.0: completed
NOTE: Running task 4 of 1632 (ID: 24,
/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/shasum/shasum-native.bb,
do_patch)
NOTE: package shasum-native-1.0: started
NOTE: package shasum-native-1.0-r1: task do_patch: started
NOTE: package shasum-native-1.0-r1: task do_patch: completed
NOTE: package shasum-native-1.0: completed
NOTE: Running task 5 of 1632 (ID: 21,
/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/shasum/shasum-native.bb,
do_configure)
NOTE: package shasum-native-1.0: started
NOTE: package shasum-native-1.0-r1: task do_configure: started
NOTE: package shasum-native-1.0-r1: task do_configure: completed
NOTE: package shasum-native-1.0: completed
NOTE: Running task 6 of 1632 (ID: 22,
/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/shasum/shasum-native.bb,
do_qa_configure)
NOTE: package shasum-native-1.0: started
NOTE: package shasum-native-1.0-r1: task do_qa_configure: started
NOTE: Checking sanity of the config.log file
NOTE: package shasum-native-1.0-r1: task do_qa_configure: completed
NOTE: package shasum-native-1.0: completed
NOTE: Running task 7 of 1632 (ID: 23,
/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/shasum/shasum-native.bb,
do_compile)
NOTE: package shasum-native-1.0: started
NOTE: package shasum-native-1.0-r1: task do_compile: started
NOTE: package shasum-native-1.0-r1: task do_compile: completed
NOTE: package shasum-native-1.0: completed
NOTE: Running task 8 of 1632 (ID: 28,
/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/shasum/shasum-native.bb,
do_install)
NOTE: package shasum-native-1.0: started
NOTE: package shasum-native-1.0-r1: task do_install: started
NOTE: package shasum-native-1.0-r1: task do_install: completed
NOTE: package shasum-native-1.0: completed
NOTE: Running task 9 of 1632 (ID: 20,
/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/shasum/shasum-native.bb,
do_populate_staging)
NOTE: package shasum-native-1.0: started
NOTE: package shasum-native-1.0-r1: task do_populate_staging: started
NOTE: package shasum-native-1.0-r1: task do_populate_staging: completed
NOTE: package shasum-native-1.0: completed
NOTE: Running task 10 of 1632 (ID: 739,
/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/stage-manager/stagemanager-native_0.0.1.bb,
do_setscene)
NOTE: package stagemanager-native-0.0.1: started
NOTE: package stagemanager-native-0.0.1-r11: task do_setscene: started
NOTE: package stagemanager-native-0.0.1-r11: task do_setscene: completed
NOTE: package stagemanager-native-0.0.1: completed
NOTE: Running task 11 of 1632 (ID: 740,
/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/stage-manager/stagemanager-native_0.0.1.bb,
do_fetch)
NOTE: package stagemanager-native-0.0.1: started
NOTE: package stagemanager-native-0.0.1-r11: task do_fetch: started
NOTE: package stagemanager-native-0.0.1-r11: task do_fetch: completed
NOTE: package stagemanager-native-0.0.1: completed
NOTE: Running task 12 of 1632 (ID: 738,
/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/stage-manager/stagemanager-native_0.0.1.bb,
do_unpack)
NOTE: package stagemanager-native-0.0.1: started
NOTE: package stagemanager-native-0.0.1-r11: task do_unpack: started
NOTE: Unpacking
/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/stage-manager/files/stage-manager
to /home/lvcargnini/instramed/openembedded/tmp/work/i686-linux/stagemanager-native-0.0.1-r11/
NOTE: Unpacking
/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/stage-manager/files/stage-manager-ipkg
to /home/lvcargnini/instramed/openembedded/tmp/work/i686-linux/stagemanager-native-0.0.1-r11/
NOTE: Unpacking
/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/stage-manager/files/stage-manager-ipkg-build
to /home/lvcargnini/instramed/openembedded/tmp/work/i686-linux/stagemanager-native-0.0.1-r11/
NOTE: package stagemanager-native-0.0.1-r11: task do_unpack: completed
NOTE: package stagemanager-native-0.0.1: completed
NOTE: Running task 13 of 1632 (ID: 737,
/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/stage-manager/stagemanager-native_0.0.1.bb,
do_patch)
NOTE: package stagemanager-native-0.0.1: started
NOTE: package stagemanager-native-0.0.1-r11: task do_patch: started
NOTE: package stagemanager-native-0.0.1-r11: task do_patch: completed
NOTE: package stagemanager-native-0.0.1: completed
NOTE: Running task 14 of 1632 (ID: 734,
/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/stage-manager/stagemanager-native_0.0.1.bb,
do_configure)
NOTE: package stagemanager-native-0.0.1: started
NOTE: package stagemanager-native-0.0.1-r11: task do_configure: started
NOTE: package stagemanager-native-0.0.1-r11: task do_configure: completed
NOTE: package stagemanager-native-0.0.1: completed
NOTE: Running task 15 of 1632 (ID: 735,
/home/lvcargnini/instramed/openembedded/org.openembedded.dev/packages/stage-manager/stagemanager-native_0.0.1.bb,
do_qa_configure)
NOTE: package stagemanager-native-0.0.1: started
NOTE: package stagemanager-native-0.0.1-r11: task do_qa_configure: started
NOTE: Checking sanity of the config.log file
NOTE: package stagemanager-native-0.0.1-r11: task do_qa_configure: completed
On Wed, Jun 18, 2008 at 2:31 PM, Michael 'Mickey' Lauer
<mickey@vanille-media.de> wrote:
> Am Mittwoch 18 Juni 2008 18:56:45 schrieb Luís Vitório Cargnini:
>> I did as you said, I finded the error in expression regular, the error
>> was in BBFILES I fixed it
>> but the error now is:
>>
>>
>> lvcargnini@protheus:~/instramed/openembedded$ bitbake nano
>> ERROR: Openembedded's config sanity checker detected a potential
>> misconfiguration.
>> Either fix the cause of this error or at your own risk disable the
>> checker (see sanity.conf).
>> Following is the list of potential problems / advisories:
>>
>> Please set TARGET_ARCH directly, or choose a MACHINE or DISTRO that does
>> so. Please set TARGET_OS directly, or choose a MACHINE or DISTRO that does
>> so. DISTRO 'None' not found. Please set a valid DISTRO in your local.conf
>
> This indicates that it does not find all configuration files. Doublecheck your
> value of BBPATH and run bitbake -v -v -v to give us more debug output.
>
> :M:
>
--
------------------------------------------------------------------------------
Thanks && Regards
M.Sc. B.Sc. Luís Vitório Cargnini
IEEE Member
Electrical Engineer Faculty @ PUCRS
Ipiranga Avenue, 6681 – Building 30
P.O. Box: 90619-900 – Porto Alegre/RS
Phone: +55 51 3320 3500 extension: 7696
---------------------------------------------------------------------------------
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: problems with bitbake
2008-06-18 16:56 ` [Angstrom-devel] " Luís Vitório Cargnini
2008-06-18 17:31 ` Michael 'Mickey' Lauer
2008-06-18 17:40 ` Alain M.
@ 2008-06-18 17:50 ` Rolf Leggewie
2 siblings, 0 replies; 8+ messages in thread
From: Rolf Leggewie @ 2008-06-18 17:50 UTC (permalink / raw)
To: openembedded-devel
Try http://blog.leggewie.org/?p=39 and you should have a correct
configuration.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Angstrom-devel] problems with bitbake
[not found] ` <ae36f8040806181114o78d06b43v883d9074b8c15a8b@mail.gmail.com>
@ 2008-06-19 18:21 ` Luís Vitório Cargnini
0 siblings, 0 replies; 8+ messages in thread
From: Luís Vitório Cargnini @ 2008-06-19 18:21 UTC (permalink / raw)
To: Hans Henry von Tresckow; +Cc: openembedded-devel, angstrom-distro-devel
ok th elocal.conf should be moved from build/local to build/conf only
this than I an let only BBPATH exported.
On Wed, Jun 18, 2008 at 3:14 PM, Luís Vitório Cargnini
<lvcargnini@gmail.com> wrote:
> I did as you said but it not worked too:
> lvcargnini@protheus:~/instramed/openembedded$ bitbake base-image
> ERROR: Openembedded's config sanity checker detected a potential
> misconfiguration.
> Either fix the cause of this error or at your own risk disable the
> checker (see sanity.conf).
> Following is the list of potential problems / advisories:
>
> Please set TARGET_ARCH directly, or choose a MACHINE or DISTRO that does so.
> Please set TARGET_OS directly, or choose a MACHINE or DISTRO that does so.
> DISTRO 'None' not found. Please set a valid DISTRO in your local.conf
>
>
> On Wed, Jun 18, 2008 at 3:00 PM, Hans Henry von Tresckow
> <hvontres@gmail.com> wrote:
>>
>>
>> On Wed, Jun 18, 2008 at 10:48 AM, Luís Vitório Cargnini
>> <lvcargnini@gmail.com> wrote:
>>>
>>> I fixed this issue exporting all the variables of the local.conf as
>>> env vars inside bash
>>> #OpenEmbedded
>>> export
>>> BBPATH=$HOME/instramed/openembedded:$HOME/instramed/openembedded/build:$HOME/instramed/openembedded/org.openembedded.dev
>>> export PKGDIR=$HOME/instramed/openembedded/build/
>>> export
>>> BBFILES="$HOME/instramed/openembedded/org.openembedded.dev/packages/*/*.bb"
>>> export DISTRO="angstrom-2008.1"
>>> export MACHINE="omap5912osk"
>>> export INHERIT="package_ipk"
>>> export IMAGE_FSTYPES="jffs2 tar.bz2 cramfs squashfs"
>>> export BBINCLUDELOGS="yes"
>>> and it seems to be working
>>>
>>>
>>
>> You should only need to export BBPATH to the shell. That way bitbake can
>> find your local.conf file and all the other vars.
>>
>>
>> --
>> Henry von Tresckow (hvontres)
>
>
>
> --
> ------------------------------------------------------------------------------
> Thanks && Regards
> M.Sc. B.Sc. Luís Vitório Cargnini
> IEEE Member
> Electrical Engineer Faculty @ PUCRS
> Ipiranga Avenue, 6681 – Building 30
> P.O. Box: 90619-900 – Porto Alegre/RS
> Phone: +55 51 3320 3500 extension: 7696
> ---------------------------------------------------------------------------------
>
--
------------------------------------------------------------------------------
Thanks && Regards
M.Sc. B.Sc. Luís Vitório Cargnini
IEEE Member
Electrical Engineer Faculty @ PUCRS
Ipiranga Avenue, 6681 – Building 30
P.O. Box: 90619-900 – Porto Alegre/RS
Phone: +55 51 3320 3500 extension: 7696
---------------------------------------------------------------------------------
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2008-06-19 18:22 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-06-18 15:12 problems with bitbake Luís Vitório Cargnini
2008-06-18 15:25 ` Michael 'Mickey' Lauer
2008-06-18 16:56 ` [Angstrom-devel] " Luís Vitório Cargnini
2008-06-18 17:31 ` Michael 'Mickey' Lauer
2008-06-18 17:48 ` Luís Vitório Cargnini
[not found] ` <a7f8874a0806181100q2981dd42ke57a69cafd1bc607@mail.gmail.com>
[not found] ` <ae36f8040806181114o78d06b43v883d9074b8c15a8b@mail.gmail.com>
2008-06-19 18:21 ` Luís Vitório Cargnini
2008-06-18 17:40 ` Alain M.
2008-06-18 17:50 ` Rolf Leggewie
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.