Bitbake error: cannot find generic.conf

Thu Jul 10 08:11:49 UTC 2008

Hi James and others, 

Thanks again James, that seems to work! Although on my way through the user manual and the hello world example, I encountered another problem.
When I try to build the hello world using: "bitbake -b org.openembedded.stable/packages/myhelloworld/myhelloworld.bb" the compilation step fails, with the following message:

=========================================================================================================================================
ERROR: function do_compile failed
ERROR: log data follows (/home/programs/devtools/oe/stuff/tmp/work/armv5te-angstrom-linux-gnueabi/myhelloworld-1.0-r0/temp/log.do_compile.30840)
| arm-angstrom-linux-gnueabi-gcc: No such file or directory
=========================================================================================================================================

At first I thought that I made a typo in the .bb file or that the example was just out-of-date. Thus I tried to build something out-of-the-box and (also) mentioned in the user manual: tuxnes.
For this I used the command: "bitbake -b org.openembedded.stable/packages/tuxnes/tuxnes_0.75.bb". As you understand also this failed, with the following trace:

=========================================================================================================================================
ERROR: function do_configure failedjavascript:onSubmitToolbarItemClicked('SendMessage','SendMessageLight.aspx?_ec=1&n=1993185492');
ERROR: log data follows (/home/programs/devtools/oe/stuff/tmp/work/armv5te-angstrom-linux-gnueabi/tuxnes-0.75-r1/temp/log.do_configure.30850)
| automake (GNU automake) 1.9.6
| Written by Tom Tromey .
|
| Copyright 2005 Free Software Foundation, Inc.
| This is free software; see the source for copying conditions.  There is NO
| warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
| AUTOV is 1.9
| NOTE: Executing autoreconf --verbose --install --force --exclude=autopoint -I/home/programs/devtools/oe/stuff/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal-1.9 -I /home/programs/devtools/oe/stuff/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal
| autoreconf: Entering directory `.'
| autoreconf: configure.in: not using Gettext
| autoreconf: running: aclocal -I /home/programs/devtools/oe/stuff/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal-1.9 -I /home/programs/devtools/oe/stuff/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal --force
| autoreconf: configure.in: tracing
| autoreconf: configure.in: not using Libtool
| autoreconf: running: /home/programs/devtools/oe/stuff/tmp/staging/i686-linux/bin/autoconf --include=/home/programs/devtools/oe/stuff/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal-1.9 --include=/home/programs/devtools/oe/stuff/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal --force --warnings=cross
| autoreconf: running: /home/programs/devtools/oe/stuff/tmp/staging/i686-linux/bin/autoheader --include=/home/programs/devtools/oe/stuff/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal-1.9 --include=/home/programs/devtools/oe/stuff/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal --force --warnings=cross
| autoheader: WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot'
| autoheader: WARNING: and `config.h.top', to define templates for `config.h.in'
| autoheader: WARNING: is deprecated and discouraged.
| autoheader:
| autoheader: WARNING: Using the third argument of `AC_DEFINE' and
| autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows one to define a template without
| autoheader: WARNING: `acconfig.h':
| autoheader:
| autoheader: WARNING:   AC_DEFINE([NEED_FUNC_MAIN], 1,
| autoheader:           [Define if a function `main' is needed.])
| autoheader:
| autoheader: WARNING: More sophisticated templates can also be produced, see the
| autoheader: WARNING: documentation.
| autoreconf: running: automake --foreign --add-missing --copy --force-missing --warnings=cross
| automake: unknown warning category `cross'
| Makefile.am: Assembler source seen but `CCAS' is undefined
| Makefile.am:
| Makefile.am: The usual way to define `CCAS' is to add `AM_PROG_AS'
| Makefile.am: to `configure.in' and run `aclocal' and `autoconf' again.
| Makefile.am: Assembler source seen but `CCASFLAGS' is undefined
| Makefile.am:
| Makefile.am: The usual way to define `CCASFLAGS' is to add `AM_PROG_AS'
| Makefile.am: to `configure.in' and run `aclocal' and `autoconf' again.
| autoreconf: automake failed with exit status: 1
| FATAL: autoreconf execution failed.
NOTE: Task failed: /home/programs/devtools/oe/stuff/tmp/work/armv5te-angstrom-linux-gnueabi/tuxnes-0.75-r1/temp/log.do_configure.30850
NOTE: package tuxnes-0.75-r1: task do_configure: failed
ERROR: TaskFailed event exception, aborting
NOTE: package tuxnes-0.75: failed
ERROR: Build of /home/programs/devtools/oe/stuff/org.openembedded.stable/packages/tuxnes/tuxnes_0.75.bb do_configure failed
ERROR: Task 4 (/home/programs/devtools/oe/stuff/org.openembedded.stable/packages/tuxnes/tuxnes_0.75.bb, do_configure) failed
NOTE: Tasks Summary: Attempted 3 tasks of which 3 didn't need to be rerun and 1 failed.
ERROR: '/home/programs/devtools/oe/stuff/org.openembedded.stable/packages/tuxnes/tuxnes_0.75.bb' failed
NOTE: build 200807101000: completed
==================================================================================================================================

What am I doing wrong here? Any help is very much appreciated.

Kind regards,

Joost

----------------------------------------
> Date: Wed, 9 Jul 2008 10:47:13 -0500
> From: jmills at avionpartners.com
> To: openembedded-users at lists.openembedded.org
> Subject: Re: Bitbake error: cannot find generic.conf
> 
> Joost,
> 
> Unless told otherwise, OE will generate the proper cross compilation
> environment for you prior to building your first package.  I always
> run "bitbake nano" as my first bitbake task, ad the nano package is
> preceded by tons of native and cross tool creation.
> 
> There are methods to override this cross compilation step, using the
> ASSUME_PROVIDED mechanisms, but for most OE systems this is not
> needed.
> 
> Of course, you will need to have a compiler on your system in order to
> generate the cross compiler, etc, but that is covered in the  setup
> documentation.
> 
> Hope that helps!
> ~james
> 
> On Wed, Jul 9, 2008 at 10:17 AM, Joost Meijles  wrote:
>>
>> Hi James and others,
>>
>> Thanks James, that did the trick!
>>
>> Something that I don't quite well understand yet is the following: when I build using OE I still have to install the correct cross-compiler by my self?
>> OE does not provide any mechanism to create the cross-compiler? We I started to read about OE, I understood that it would provide me with the correct cross-compiler.
>>
>> Can someone clarify this for me?
>>
>>
>> Kind regards,
>>
>> Joost
>>
>>
>> _________________________________________________________________
>> Download Messenger op je mobiel!
>> http://www.windowslivemobile.msn.com/nl/
>> _______________________________________________
>> Openembedded-users mailing list
>> Openembedded-users at lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users
>>
> 
> _______________________________________________
> Openembedded-users mailing list
> Openembedded-users at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users

_________________________________________________________________
De mooiste afbeeldingen van Angelina Jolie vind je met Live Search
http://search.live.com/images/results.aspx?q=angelina%20jolie&FORM=MIINTM