From rajive_26 at yahoo.com Thu Feb 2 15:36:48 2012 From: rajive_26 at yahoo.com (rajive gupta) Date: Thu, 2 Feb 2012 06:36:48 -0800 (PST) Subject: [ELDK] eldk-5.1 powerpc-4xx building problem Message-ID: <1328193408.48731.YahooMailClassic@web160804.mail.bf1.yahoo.com> Hi I have install eldk-5.1 for powerpc-4xx . I am having following problem while building eldk MACHINE=generic-powerpc-4xx bitbake core-image-minimal Pseudo is not present but is required, building this first before the main build DEBUG: Removed the following variables from the environment: GNOME_DESKTOP_SESSION_ID, GJS_DEBUG_OUTPUT, LESSOPEN, QT_IM_MODULE, XDG_VTNR, GNOME_KEYRING_CONTROL, WINDOWPATH, SHLVL, HISTSIZE, WINDOWID, IMSETTINGS_INTEGRATE_DESKTOP, BBFETCH2, IMSETTINGS_MODULE, XDG_RUNTIME_DIR, XMODIFIERS, XDG_SESSION_ID, BUILDDIR, GDMSESSION, HOSTNAME, HISTCONTROL, CVS_RSH, MAIL, LS_COLORS, GJS_DEBUG_TOPICS, XDG_SEAT DEBUG: Found bblayers.conf (/opt/eldk-5.1/build/eldk-rel-v5.1-2012-01-02-8281cbd-powerpc-4xx/conf/bblayers.conf) DEBUG: LOAD /opt/eldk-5.1/build/eldk-rel-v5.1-2012-01-02-8281cbd-powerpc-4xx/conf/bblayers.conf DEBUG: Adding layer /home/rajive/git/eldk/meta DEBUG: LOAD /home/rajive/git/eldk/meta/conf/layer.conf DEBUG: Adding layer /home/rajive/git/eldk/meta-yocto DEBUG: LOAD /home/rajive/git/eldk/meta-yocto/conf/layer.conf DEBUG: Adding layer /home/rajive/git/eldk/meta-eldk DEBUG: LOAD /home/rajive/git/eldk/meta-eldk/conf/layer.conf DEBUG: LOAD /home/rajive/git/eldk/meta/conf/bitbake.conf DEBUG: CONF conf/bitbake.conf:670: including conf/site.conf DEBUG: CONF file 'conf/site.conf' not found DEBUG: CONF conf/bitbake.conf:671: including conf/auto.conf DEBUG: CONF file 'conf/auto.conf' not found DEBUG: CONF conf/bitbake.conf:672: including conf/local.conf DEBUG: LOAD conf/local.conf DEBUG: CONF conf/bitbake.conf:673: including conf/build/i686-linux.conf DEBUG: CONF file 'conf/build/i686-linux.conf' not found DEBUG: CONF conf/bitbake.conf:674: including conf/target/INVALID-oe-linux.conf DEBUG: CONF file 'conf/target/INVALID-oe-linux.conf' not found DEBUG: CONF conf/bitbake.conf:675: including conf/machine/generic-powerpc-4xx.conf DEBUG: LOAD /home/rajive/git/eldk/meta-eldk/conf/machine/generic-powerpc-4xx.conf DEBUG: CONF /home/rajive/git/eldk/meta-eldk/conf/machine/generic-powerpc-4xx.conf:8: including conf/machine/include/tune-ppc440e.inc DEBUG: BB /home/rajive/git/eldk/meta/conf/machine/include/tune-ppc440e.inc: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/conf/machine/include/tune-ppc440e.inc DEBUG: CONF /home/rajive/git/eldk/meta/conf/machine/include/tune-ppc440e.inc:3: including conf/machine/include/powerpc/arch-powerpc.inc DEBUG: BB /home/rajive/git/eldk/meta/conf/machine/include/powerpc/arch-powerpc.inc: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/conf/machine/include/powerpc/arch-powerpc.inc DEBUG: CONF conf/bitbake.conf:676: including conf/machine-sdk/i686.conf DEBUG: LOAD /home/rajive/git/eldk/meta/conf/machine-sdk/i686.conf DEBUG: CONF conf/bitbake.conf:677: including conf/distro/eldk.conf DEBUG: LOAD /home/rajive/git/eldk/meta-eldk/conf/distro/eldk.conf DEBUG: CONF conf/bitbake.conf:678: including conf/distro/defaultsetup.conf DEBUG: LOAD /home/rajive/git/eldk/meta/conf/distro/defaultsetup.conf DEBUG: CONF /home/rajive/git/eldk/meta/conf/distro/defaultsetup.conf:1: including conf/distro/include/default-providers.inc DEBUG: BB /home/rajive/git/eldk/meta/conf/distro/include/default-providers.inc: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/conf/distro/include/default-providers.inc DEBUG: CONF /home/rajive/git/eldk/meta/conf/distro/defaultsetup.conf:2: including conf/distro/include/default-versions.inc DEBUG: BB /home/rajive/git/eldk/meta/conf/distro/include/default-versions.inc: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/conf/distro/include/default-versions.inc DEBUG: CONF /home/rajive/git/eldk/meta/conf/distro/defaultsetup.conf:3: including conf/distro/include/default-distrovars.inc DEBUG: BB /home/rajive/git/eldk/meta/conf/distro/include/default-distrovars.inc: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/conf/distro/include/default-distrovars.inc DEBUG: CONF /home/rajive/git/eldk/meta/conf/distro/defaultsetup.conf:4: including conf/distro/include/world-broken.inc DEBUG: BB /home/rajive/git/eldk/meta/conf/distro/include/world-broken.inc: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/conf/distro/include/world-broken.inc DEBUG: CONF /home/rajive/git/eldk/meta/conf/distro/defaultsetup.conf:7: including conf/distro/include/tcmode-default.inc DEBUG: BB /home/rajive/git/eldk/meta/conf/distro/include/tcmode-default.inc: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/conf/distro/include/tcmode-default.inc DEBUG: CONF /home/rajive/git/eldk/meta/conf/distro/include/tcmode-default.inc:65: including conf/distro/include/as-needed.inc DEBUG: BB /home/rajive/git/eldk/meta/conf/distro/include/as-needed.inc: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/conf/distro/include/as-needed.inc DEBUG: CONF /home/rajive/git/eldk/meta/conf/distro/defaultsetup.conf:10: including conf/distro/include/tclibc-eglibc.inc DEBUG: BB /home/rajive/git/eldk/meta/conf/distro/include/tclibc-eglibc.inc: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/conf/distro/include/tclibc-eglibc.inc DEBUG: CONF conf/bitbake.conf:679: including conf/documentation.conf DEBUG: LOAD /home/rajive/git/eldk/meta/conf/documentation.conf DEBUG: CONF conf/bitbake.conf:680: including conf/sanity.conf DEBUG: LOAD /home/rajive/git/eldk/meta/conf/sanity.conf DEBUG: CONF conf/bitbake.conf:681: including conf/abi_version.conf DEBUG: LOAD /home/rajive/git/eldk/meta/conf/abi_version.conf DEBUG: BB :0: inheriting classes/base.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/base.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/base.bbclass DEBUG: BB :0: inheriting classes/patch.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/patch.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/patch.bbclass DEBUG: BB :0: inheriting classes/staging.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/staging.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/staging.bbclass DEBUG: BB :0: inheriting classes/mirrors.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/mirrors.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/mirrors.bbclass DEBUG: BB :0: inheriting classes/utils.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/utils.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/utils.bbclass DEBUG: BB :0: inheriting classes/utility-tasks.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/utility-tasks.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/utility-tasks.bbclass DEBUG: BB :0: inheriting classes/metadata_scm.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/metadata_scm.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/metadata_scm.bbclass DEBUG: BB :0: inheriting classes/buildstats.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/buildstats.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/buildstats.bbclass DEBUG: BB :0: inheriting classes/logging.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/logging.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/logging.bbclass DEBUG: BB :0: inheriting classes/add_machine_symlinks.bbclass DEBUG: BB /home/rajive/git/eldk/meta-eldk/classes/add_machine_symlinks.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta-eldk/classes/add_machine_symlinks.bbclass DEBUG: BB :0: inheriting classes/package_ipk.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/package_ipk.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/package_ipk.bbclass DEBUG: BB :0: inheriting classes/package.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/package.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/package.bbclass DEBUG: BB :0: inheriting classes/packagedata.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/packagedata.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/packagedata.bbclass DEBUG: BB :0: inheriting classes/prserv.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/prserv.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/prserv.bbclass DEBUG: BB :0: inheriting classes/image-mklibs.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/image-mklibs.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/image-mklibs.bbclass DEBUG: BB :0: inheriting classes/image-prelink.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/image-prelink.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/image-prelink.bbclass DEBUG: BB :0: inheriting classes/insane.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/insane.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/insane.bbclass DEBUG: BB :0: inheriting classes/debian.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/debian.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/debian.bbclass DEBUG: BB :0: inheriting classes/devshell.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/devshell.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/devshell.bbclass DEBUG: BB :0: inheriting classes/terminal.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/terminal.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/terminal.bbclass DEBUG: BB :0: inheriting classes/sstate.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/sstate.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/sstate.bbclass DEBUG: BB :0: inheriting classes/license.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/license.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/license.bbclass DEBUG: BB :0: inheriting classes/sanity.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/sanity.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/sanity.bbclass DEBUG: Clearing SRCREV cache due to cache policy of: clear DEBUG: Using cache in '/opt/eldk-5.1/build/eldk-rel-v5.1-2012-01-02-8281cbd-powerpc-4xx/tmp/cache/bb_codeparser.dat' for codeparser cache ERROR:? Poky'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 install following missing utilities: C++ Compiler (g++),makeinfo ERROR: Execution of event handler 'check_sanity_eventhandler' failed I have followed the eldk document step by step. Can you please help me Thanks Rajive From rajive_26 at yahoo.com Thu Feb 2 15:58:41 2012 From: rajive_26 at yahoo.com (rajive gupta) Date: Thu, 2 Feb 2012 06:58:41 -0800 (PST) Subject: [ELDK] eldk-5.1 powerpc-4xx building problem In-Reply-To: Message-ID: <1328194721.12687.YahooMailClassic@web160801.mail.bf1.yahoo.com> Hi I did this with yum install and had following messages sudo yum install g++ [sudo] password for rajive: Loaded plugins: langpacks, presto, refresh-packagekit Setting up Install Process No package g++ available. Error: Nothing to do [rajive at vehicle-rcs eldk-rel-v5.1-2012-01-02-8281cbd-powerpc-4xx]$ sudo yum install textinfo Loaded plugins: langpacks, presto, refresh-packagekit Setting up Install Process No package textinfo available. Error: Nothing to do Rajive --- On Thu, 2/2/12, Lorenzo Petroli wrote: From: Lorenzo Petroli Subject: Re: [ELDK] eldk-5.1 powerpc-4xx building problem To: "rajive gupta" Date: Thursday, February 2, 2012, 6:51 AM Hi. sudo apt-get install g++sudo apt-get install texinfo This might solve your problem Best RegardsLorenzo 2012/2/2 rajive gupta Hi I have install eldk-5.1 for powerpc-4xx . I am having following problem while building eldk MACHINE=generic-powerpc-4xx bitbake core-image-minimal Pseudo is not present but is required, building this first before the main build DEBUG: Removed the following variables from the environment: GNOME_DESKTOP_SESSION_ID, GJS_DEBUG_OUTPUT, LESSOPEN, QT_IM_MODULE, XDG_VTNR, GNOME_KEYRING_CONTROL, WINDOWPATH, SHLVL, HISTSIZE, WINDOWID, IMSETTINGS_INTEGRATE_DESKTOP, BBFETCH2, IMSETTINGS_MODULE, XDG_RUNTIME_DIR, XMODIFIERS, XDG_SESSION_ID, BUILDDIR, GDMSESSION, HOSTNAME, HISTCONTROL, CVS_RSH, MAIL, LS_COLORS, GJS_DEBUG_TOPICS, XDG_SEAT DEBUG: Found bblayers.conf (/opt/eldk-5.1/build/eldk-rel-v5.1-2012-01-02-8281cbd-powerpc-4xx/conf/bblayers.conf) DEBUG: LOAD /opt/eldk-5.1/build/eldk-rel-v5.1-2012-01-02-8281cbd-powerpc-4xx/conf/bblayers.conf DEBUG: Adding layer /home/rajive/git/eldk/meta DEBUG: LOAD /home/rajive/git/eldk/meta/conf/layer.conf DEBUG: Adding layer /home/rajive/git/eldk/meta-yocto DEBUG: LOAD /home/rajive/git/eldk/meta-yocto/conf/layer.conf DEBUG: Adding layer /home/rajive/git/eldk/meta-eldk DEBUG: LOAD /home/rajive/git/eldk/meta-eldk/conf/layer.conf DEBUG: LOAD /home/rajive/git/eldk/meta/conf/bitbake.conf DEBUG: CONF conf/bitbake.conf:670: including conf/site.conf DEBUG: CONF file 'conf/site.conf' not found DEBUG: CONF conf/bitbake.conf:671: including conf/auto.conf DEBUG: CONF file 'conf/auto.conf' not found DEBUG: CONF conf/bitbake.conf:672: including conf/local.conf DEBUG: LOAD conf/local.conf DEBUG: CONF conf/bitbake.conf:673: including conf/build/i686-linux.conf DEBUG: CONF file 'conf/build/i686-linux.conf' not found DEBUG: CONF conf/bitbake.conf:674: including conf/target/INVALID-oe-linux.conf DEBUG: CONF file 'conf/target/INVALID-oe-linux.conf' not found DEBUG: CONF conf/bitbake.conf:675: including conf/machine/generic-powerpc-4xx.conf DEBUG: LOAD /home/rajive/git/eldk/meta-eldk/conf/machine/generic-powerpc-4xx.conf DEBUG: CONF /home/rajive/git/eldk/meta-eldk/conf/machine/generic-powerpc-4xx.conf:8: including conf/machine/include/tune-ppc440e.inc DEBUG: BB /home/rajive/git/eldk/meta/conf/machine/include/tune-ppc440e.inc: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/conf/machine/include/tune-ppc440e.inc DEBUG: CONF /home/rajive/git/eldk/meta/conf/machine/include/tune-ppc440e.inc:3: including conf/machine/include/powerpc/arch-powerpc.inc DEBUG: BB /home/rajive/git/eldk/meta/conf/machine/include/powerpc/arch-powerpc.inc: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/conf/machine/include/powerpc/arch-powerpc.inc DEBUG: CONF conf/bitbake.conf:676: including conf/machine-sdk/i686.conf DEBUG: LOAD /home/rajive/git/eldk/meta/conf/machine-sdk/i686.conf DEBUG: CONF conf/bitbake.conf:677: including conf/distro/eldk.conf DEBUG: LOAD /home/rajive/git/eldk/meta-eldk/conf/distro/eldk.conf DEBUG: CONF conf/bitbake.conf:678: including conf/distro/defaultsetup.conf DEBUG: LOAD /home/rajive/git/eldk/meta/conf/distro/defaultsetup.conf DEBUG: CONF /home/rajive/git/eldk/meta/conf/distro/defaultsetup.conf:1: including conf/distro/include/default-providers.inc DEBUG: BB /home/rajive/git/eldk/meta/conf/distro/include/default-providers.inc: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/conf/distro/include/default-providers.inc DEBUG: CONF /home/rajive/git/eldk/meta/conf/distro/defaultsetup.conf:2: including conf/distro/include/default-versions.inc DEBUG: BB /home/rajive/git/eldk/meta/conf/distro/include/default-versions.inc: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/conf/distro/include/default-versions.inc DEBUG: CONF /home/rajive/git/eldk/meta/conf/distro/defaultsetup.conf:3: including conf/distro/include/default-distrovars.inc DEBUG: BB /home/rajive/git/eldk/meta/conf/distro/include/default-distrovars.inc: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/conf/distro/include/default-distrovars.inc DEBUG: CONF /home/rajive/git/eldk/meta/conf/distro/defaultsetup.conf:4: including conf/distro/include/world-broken.inc DEBUG: BB /home/rajive/git/eldk/meta/conf/distro/include/world-broken.inc: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/conf/distro/include/world-broken.inc DEBUG: CONF /home/rajive/git/eldk/meta/conf/distro/defaultsetup.conf:7: including conf/distro/include/tcmode-default.inc DEBUG: BB /home/rajive/git/eldk/meta/conf/distro/include/tcmode-default.inc: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/conf/distro/include/tcmode-default.inc DEBUG: CONF /home/rajive/git/eldk/meta/conf/distro/include/tcmode-default.inc:65: including conf/distro/include/as-needed.inc DEBUG: BB /home/rajive/git/eldk/meta/conf/distro/include/as-needed.inc: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/conf/distro/include/as-needed.inc DEBUG: CONF /home/rajive/git/eldk/meta/conf/distro/defaultsetup.conf:10: including conf/distro/include/tclibc-eglibc.inc DEBUG: BB /home/rajive/git/eldk/meta/conf/distro/include/tclibc-eglibc.inc: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/conf/distro/include/tclibc-eglibc.inc DEBUG: CONF conf/bitbake.conf:679: including conf/documentation.conf DEBUG: LOAD /home/rajive/git/eldk/meta/conf/documentation.conf DEBUG: CONF conf/bitbake.conf:680: including conf/sanity.conf DEBUG: LOAD /home/rajive/git/eldk/meta/conf/sanity.conf DEBUG: CONF conf/bitbake.conf:681: including conf/abi_version.conf DEBUG: LOAD /home/rajive/git/eldk/meta/conf/abi_version.conf DEBUG: BB :0: inheriting classes/base.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/base.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/base.bbclass DEBUG: BB :0: inheriting classes/patch.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/patch.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/patch.bbclass DEBUG: BB :0: inheriting classes/staging.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/staging.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/staging.bbclass DEBUG: BB :0: inheriting classes/mirrors.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/mirrors.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/mirrors.bbclass DEBUG: BB :0: inheriting classes/utils.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/utils.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/utils.bbclass DEBUG: BB :0: inheriting classes/utility-tasks.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/utility-tasks.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/utility-tasks.bbclass DEBUG: BB :0: inheriting classes/metadata_scm.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/metadata_scm.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/metadata_scm.bbclass DEBUG: BB :0: inheriting classes/buildstats.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/buildstats.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/buildstats.bbclass DEBUG: BB :0: inheriting classes/logging.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/logging.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/logging.bbclass DEBUG: BB :0: inheriting classes/add_machine_symlinks.bbclass DEBUG: BB /home/rajive/git/eldk/meta-eldk/classes/add_machine_symlinks.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta-eldk/classes/add_machine_symlinks.bbclass DEBUG: BB :0: inheriting classes/package_ipk.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/package_ipk.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/package_ipk.bbclass DEBUG: BB :0: inheriting classes/package.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/package.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/package.bbclass DEBUG: BB :0: inheriting classes/packagedata.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/packagedata.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/packagedata.bbclass DEBUG: BB :0: inheriting classes/prserv.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/prserv.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/prserv.bbclass DEBUG: BB :0: inheriting classes/image-mklibs.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/image-mklibs.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/image-mklibs.bbclass DEBUG: BB :0: inheriting classes/image-prelink.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/image-prelink.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/image-prelink.bbclass DEBUG: BB :0: inheriting classes/insane.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/insane.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/insane.bbclass DEBUG: BB :0: inheriting classes/debian.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/debian.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/debian.bbclass DEBUG: BB :0: inheriting classes/devshell.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/devshell.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/devshell.bbclass DEBUG: BB :0: inheriting classes/terminal.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/terminal.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/terminal.bbclass DEBUG: BB :0: inheriting classes/sstate.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/sstate.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/sstate.bbclass DEBUG: BB :0: inheriting classes/license.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/license.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/license.bbclass DEBUG: BB :0: inheriting classes/sanity.bbclass DEBUG: BB /home/rajive/git/eldk/meta/classes/sanity.bbclass: handle(data, include) DEBUG: LOAD /home/rajive/git/eldk/meta/classes/sanity.bbclass DEBUG: Clearing SRCREV cache due to cache policy of: clear DEBUG: Using cache in '/opt/eldk-5.1/build/eldk-rel-v5.1-2012-01-02-8281cbd-powerpc-4xx/tmp/cache/bb_codeparser.dat' for codeparser cache ERROR:? Poky'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 install following missing utilities: C++ Compiler (g++),makeinfo ERROR: Execution of event handler 'check_sanity_eventhandler' failed I have followed the eldk document step by step. Can you please help me Thanks Rajive _______________________________________________ eldk mailing list eldk at lists.denx.de http://lists.denx.de/mailman/listinfo/eldk From wd at denx.de Thu Feb 2 19:44:52 2012 From: wd at denx.de (Wolfgang Denk) Date: Thu, 02 Feb 2012 19:44:52 +0100 Subject: [ELDK] eldk-5.1 powerpc-4xx building problem In-Reply-To: <1328194721.12687.YahooMailClassic@web160801.mail.bf1.yahoo.com> References: <1328194721.12687.YahooMailClassic@web160801.mail.bf1.yahoo.com> Message-ID: <20120202184452.3913811F9E53@gemini.denx.de> Dear rajive gupta, In message <1328194721.12687.YahooMailClassic at web160801.mail.bf1.yahoo.com> you wrote: > > I did this with yum install and had following messages > > sudo yum install g++ > [sudo] password for rajive: > Loaded plugins: langpacks, presto, refresh-packagekit > Setting up Install Process > No package g++ available. > Error: Nothing to do > [rajive at vehicle-rcs eldk-rel-v5.1-2012-01-02-8281cbd-powerpc-4xx]$ sudo yum install textinfo > Loaded plugins: langpacks, presto, refresh-packagekit > Setting up Install Process > No package textinfo available. > Error: Nothing to do You packagenames may be different. Bitbake compalins that it's missing "g++" and "makeinfo", so search for these: -> yum provides "*/bin/g++" "*/bin/makeinfo" ... gcc-c++-4.6.2-1.fc16.i686 : C++ support for GCC Repo : fedora Matched from: Filename : /usr/bin/g++ ... texinfo-4.13a-15.fc15.i686 : Tools needed to create Texinfo format documentation files Repo : fedora Matched from: Filename : /usr/bin/makeinfo So try: sudo yum -y install gcc-c++ texinfo Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de But it's real. And if it's real it can be affected ... we may not be able to break it, but, I'll bet you credits to Navy Beans we can put a dent in it. -- deSalle, "Catspaw", stardate 3018.2 From rajive_26 at yahoo.com Tue Feb 7 22:01:23 2012 From: rajive_26 at yahoo.com (rajive gupta) Date: Tue, 7 Feb 2012 13:01:23 -0800 (PST) Subject: [ELDK] eldk-5.1 powerpc-4xx building problem In-Reply-To: <20120202184452.3913811F9E53@gemini.denx.de> Message-ID: <1328648483.98706.YahooMailClassic@web160801.mail.bf1.yahoo.com> Hi? Please can you guide me or send a link to document , how to create powerpc ramdisk (uRamdisk) image in ELDK-5.1. ?I need to create basic file system on powerpc 405 board. Thanks Rajive From lpetroli at gmail.com Wed Feb 8 04:06:25 2012 From: lpetroli at gmail.com (Lorenzo Petroli) Date: Wed, 8 Feb 2012 01:06:25 -0200 Subject: [ELDK] ISSUE: core-image-lsb-sdk.bb, do_rootfs Message-ID: Hi there! After quite some time trying to build a generic-mips-softfloat image (I made my own scripts for mips softfloat), I think I am almost there. However, while executing TASK 5079 of 5081, it fails to find libstdc++. Can you help me with that? Of course there are lots of things i can tell about this issue. 1?) This is the command line I typed to build the images (it helps you understand what type of configuration I have): MACHINE=generic-mips-softfloat IMAGES="core-image-lsb-sdk" ~/eldk/meta-eldk/tools/eldk-build.sh 2?) For some reason that I don't understand, libstdc++.so* are installed at {anything}/usr/lib/*nof* instead of just {anything}/usr/lib. What is this nof concept anyway? 2.1?) During build, many packets looked for libstdc++ at {sysroot}/usr/lib. So I manually created symlinks for libstdc++ there. 2.2?) I really suspect that's the problem. But since I have no knowledge so far of why there's this NOF subdir, I am not confident on how to properly solve the problem. 3?) I have attached to this email the log file about the error. Hope you find it useful. In summary, I would appreciate if you could help me solve the problem, and teach me about this NOF subdir, why it is there, and so on. Thank you very much guys. Looking forward to task 5081 of 5081 ;o) Lorenzo -------------- next part -------------- A non-text attachment was scrubbed... Name: log.do_rootfs.25762 Type: application/octet-stream Size: 675731 bytes Desc: not available URL: From wd at denx.de Wed Feb 8 09:14:00 2012 From: wd at denx.de (Wolfgang Denk) Date: Wed, 08 Feb 2012 09:14:00 +0100 Subject: [ELDK] ISSUE: core-image-lsb-sdk.bb, do_rootfs In-Reply-To: References: Message-ID: <20120208081400.1B5F9193BB56@gemini.denx.de> Dear Lorenzo, In message you wrote: > > After quite some time trying to build a generic-mips-softfloat image (I > made my own scripts for mips softfloat), I think I am almost there. > However, while executing TASK 5079 of 5081, it fails to find libstdc++. Efforts always go up exponentially as you are approaching completion of the task ;-) > 2?) For some reason that I don't understand, libstdc++.so* are installed at > {anything}/usr/lib/*nof* instead of just {anything}/usr/lib. What is this > nof concept anyway? NOF = No Floating Point Support = soft-float. MIPS is set up for a multilib configuration. This is needed because otherwise (with a hard-float only setup), attempts to build U-Boot would run into issues like this: mips-linux-ld: Warning: ...sysroots/mips-linux/usr/lib/mips-linux/4.6.1/libgcc.a(_lshrdi3.o) uses hard float, u-boot uses soft float For details see commit commit fb62301 "meta-eldk: add support for generic mips machine" in our ELDK repository, especially the MULTILIB_* settings in meta/recipes-devtools/gcc/gcc-4.6/t-mips.patch When building for a soft-float only target, you probably don't want to use a multilib configuration. > 2.1?) During build, many packets looked for libstdc++ at {sysroot}/usr/lib. > So I manually created symlinks for libstdc++ there. I think this is a consequence of incorrect multilib setup. > 2.2?) I really suspect that's the problem. But since I have no knowledge so > far of why there's this NOF subdir, I am not confident on how to properly > solve the problem. > > 3?) I have attached to this email the log file about the error. Hope you > find it useful. You might also want to check recent contributions to OE-core, especially this commit: commit 26630a9f37b04e215eff9b8e63414b6b2066d6fa Author: Andreas Oberritter Date: Thu Feb 2 14:00:34 2012 +0100 tune-mips32.inc: Add mips32-nf and mips32el-nf tune-mips32.inc only lists mips32 CPUs with hardware FPU. Extend it to list CPUs without hardware FPU, too. Signed-off-by: Andreas Oberritter See http://thread.gmane.org/gmane.comp.handhelds.openembedded.core/15036 Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de So we follow our wandering paths, and the very darkness acts as our guide and our doubts serve to reassure us. - Jean-Pierre de Caussade, eighteenth-century Jesuit priest From wd at denx.de Wed Feb 8 09:20:34 2012 From: wd at denx.de (Wolfgang Denk) Date: Wed, 08 Feb 2012 09:20:34 +0100 Subject: [ELDK] eldk-5.1 powerpc-4xx building problem In-Reply-To: <1328648483.98706.YahooMailClassic@web160801.mail.bf1.yahoo.com> References: <1328648483.98706.YahooMailClassic@web160801.mail.bf1.yahoo.com> Message-ID: <20120208082034.70F77B6F26@gemini.denx.de> Dear rajive gupta, In message <1328648483.98706.YahooMailClassic at web160801.mail.bf1.yahoo.com> you wrote: > > Please can you guide me or send a link to document , how to create powerpc > ramdisk (uRamdisk) image in ELDK-5.1. ?I need to create basic file system > on powerpc 405 board. To create custom file system images you have to provide respective bitbake recipies. You can probably use meta/recipes-core/images/core-image-minimal.bb and meta/recipes-core/images/core-image-minimal-initramfs.bb as reference. For details, please see http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#ref-images http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html http://www.yoctoproject.org/docs/1.0/poky-ref-manual/poky-ref-manual.html Of course you can also try starting with the existing file system images, say for example ftp://ftp.denx.de/pub/eldk/5.1/targets/powerpc-4xx-softfloat/core-image-minimal-generic-powerpc-4xx-softfloat.tar.gz and manually add/remove files there. Finally, you can try and use HOB, which provides a graphical user interface for BitBake; see http://www.yoctoproject.org/projects/hob Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de CONSUMER NOTICE: Because of the "Uncertainty Principle," It Is Impossible for the Consumer to Find Out at the Same Time Both Precisely Where This Product Is and How Fast It Is Moving. From adwords-noreply at google5489846.com Mon Feb 13 23:28:38 2012 From: adwords-noreply at google5489846.com (Ad Words) Date: Mon, 13 Feb 2012 17:28:38 -0500 Subject: [ELDK] Check your Ad Words account Status Message-ID: <71DBB392F8804B29A5B609A8E9F714F0@emergency> Sch?nen Tag, Wenn Sie Zugang zu einem Computer, und bis zu drei Stunden freie Zeit pro Woche. Sie k?nnen zahlen, bekommen m? Sie wollen aus einem Teil oder vollst?ndig online arbeiten von zu Hause aus und nutzen Sie w? Jede Woche bezahlt werden? Wenn ja, dann lesen Sie bitte sorgf? Valid. ?ber: ? Honeywell International ist ein diversifiziertes Technologie-und Produktionsunternehmen F Shaker, bedient Kunden weltweit mit Produkten und Dienstleistungen, Luft-und Raumfahrt, Steuerungstechnologien en Geb ude, der Benutzer privathe und Industrie, der Automobil -? , Turbolader und Spezialmaterialien. Mit dem Wechsel von den Wurzeln bis ins Jahr 1885 Honeywell Bett? Ftigt mehr als 100.000 Menschen in 95 L?. Unter der F?hrung von Pr?sident und CEO Dave Cote wir uns auf unsere f?nf Initiativen f konzentrieren? Wachstum, Produktivit?t T, Cash, People und Moderatoren, Honeywell Operating System und Funktionale Materialien Transformation. Position: Wir suchen aktuell f?r einen Teil oder Vollzeit-Mitarbeiter f? Eine wachsende unserer Debitorenbuchhaltung. Durch umfangreiche demografische Forschung, haben wir eine F? Er entdeckte das ungenutzte menschliche Ressourcen, die f? R einen oder anderen Grund, m? Brauchen Sie die Freiheit von zu Hause aus zu arbeiten. Wenn das klingt wie Sie, lesen Sie bitte weiter und erw?hnt? Systems, Teil unserer Gesellschaft Family. Als Teil unserer laufenden Multi Level Marketing Network, suchen wir Menschen, die f kann? R arbeiten wir als unsere Vertreter. Sie k?nnen k? Leicht von 700 bis 2.000 ? oder mehr in einer Woche durch die f Arbeit? R uns als Auftragnehmer in Ihrer Position sind Sie f? Eine Sammlung von Zahlungen im Namen unserer Partner und Small Business-Organisationen, die unter registriert sind. Wenn das klingt wie ihr Traumberuf? Nun, es ist sicherlich f? R 10.000 + aktuelle Mitglieder, die von 700 bis 2.000 ? pro Woche online mit diesem System sind. Ben bemerkt, dass jede Form der Geldanlage f?r Sie? Ist in dieser Aufgabe angenommen und dauert nur 1-3 Stunden pro Woche. Das Aufgabengebiet: F die Position Forderungen Offizier f?hrte zu folgenden Aufgaben?: Coordinate Zahlungen von unseren Kunden, Zahlungen entgegenzunehmen, die in Form von zertifizierten Scheck oder Bankwechsel kommen. Verarbeiten Sie Zahlungen an Ihre Bank und betreibt 90% der Mittel erhalten regul?re Besch?ftigung? S Amt als angegeben. Die restlichen 10% ist Ihr Lohn. Von dieser Position aus m? Sie m?ssen viel Zeit auf w? F?r mit einem guten Einkommen. L?hne: Der Auftragseingang in der Form von Anzahlungen von Kunden, Sie bis zu 10% sind, ist F die Kosten f?r die Schlie?ung der Verarbeitung Western Union? T in Bezug auf jedes lokale Unternehmen? Accounting Office. Dar?ber hinaus erhalten Sie ein monatliches Gehalt von 1000 Euro, die am Ende eines jeden Monats, zuz kommt? Wie die andere Anreize und Verg?nstigungen einschlie?lich Steuerbefreiungen. Interessierte Kandidaten Interessierte Bewerber sollten reagieren: Vollst?ndig? 'S Vollst?ndiger Name Vollst?ndige Adresse der Wohnung Adressen Mobile Phone E-Mail Treten Sie mit uns f?r mehr zu Information an der eMail in Verbindung: donnag15 at aol.com Also das ist eine unserer Firma k Job zur Verf?gung gestellt? Sie erreichen? E-Mail mit einem Letter of Approval, wenn das Management entscheidet, dass Sie ein Kandidat sind. Bitte geben Sie uns den besten Weg um Sie zu kontaktieren, um Ihre E-Mail zu beantworten. Wir freuen uns auf? ?ber Ihr Interesse an Honeywell International Inc. BITTE BEACHTEN SIE: Helfen Sie uns zu k?mpfen? Mitigation. Wir schliefen ?hnlichkeit? Sie ftig jeden Vorschlag zu ergreifen? Bei uns zu diesem Vorschlag an uns, damit wir entsprechende Ma? Ergriffen werden, um es zu geben, unabh?ngig von jeder E-Mail mit der Bitte f?r die Daten Ihrer Kreditkarte und Geld und in der N?he? Lich beachten Sie, dass diese Transaktion ohne Risiko, und wenn eine Klage unter den reservierten Bank Betrieb 2005.Alle von Ihnen werden vertraulich behandelt und f? r den Zweck der Verwendung Ihrer Besch? Ftigung. Dies steht im Einklang mit U. S. Data Protection Act 1998. Herzlich George Harrison Treten Sie mit uns f?r mehr zu Information an der eMail in Verbindung: donnag15 at aol.com