Quality Team For OZ

[ScottYelich]

ya, could be many errors...
I\'ve seenthis when any part of the chain is missing... usually \"as\" ... (gas?) ... I think I have seen it with bad ld too.
when installing gcc, usually slap in binutils too.


Scott

[Mickeyl]

Another (slightly obvious) reason could just be that arm-linux-gcc is not in your $PATH...  Happened to me more than once

[Anonymous]

# oebuild busybox/busybox_1.00-pre8.oe
NOTE: package busybox-1.00-pre8-r0: task do_fetch started
NOTE: package busybox-1.00-pre8-r0: task do_fetch completed
NOTE: package busybox-1.00-pre8-r0: task do_compile started
ERROR: function do_compile failed
ERROR: see log in /opt/oe/packages/tmp/base/busybox-1.00-pre8-r0/temp/log.do_compile.18440
ERROR: package busybox-1.00-pre8-r0: task do_compile failed
ERROR: TaskFailed event exception, aborting
# cat /opt/oe/packages/tmp/base/busybox-1.00-pre8-r0/temp/log.do_compile.18440


NOTE: make -e MAKEFLAGS= CROSS=arm-linux-
ccache arm-linux-gcc -I./include -Wall -Wstrict-prototypes -Wshadow -Os -fstrict
-aliasing -fomit-frame-pointer -D_GNU_SOURCE -DNDEBUG    -I/opt/oe/packages/tmp/
staging/include -I/opt/oe/packages/tmp/staging/usr/X11R6/include -I/opt/oe/packa
ges/tmp/staging/target/include -fexpensive-optimizations -fomit-frame-pointer -O
2 -c -o libbb/module_syscalls.o libbb/module_syscalls.c
In file included from libbb/module_syscalls.c:26:
/opt/oe/packages/tmp/staging/target/include/sys/syscall.h:32:27: bits/syscall.h:
 No such file or directory
make: *** [libbb/module_syscalls.o] Error 1
FATAL: oemake failed

Why is this file missing?  Something missing?

[Anonymous]

Have you compiled glibc first ?

Richard

[Anonymous]

Yes...
# oebuild glibc/glibc_2.3.2.oe
NOTE: package glibc-2.3.2-r0: task do_fetch started
NOTE: package glibc-2.3.2-r0: task do_fetch completed
NOTE: package glibc-2.3.2-r0: task do_build started
NOTE: package glibc-2.3.2-r0: task do_build completed

[Anonymous]

O.K

I think (from memory) that the header you are missing is part of the uclib which you may need to build first . Sorry I can\'t check at the moment I\'m not near my development PC.
Check the dependency list in the packages directory for busybox.

Richard

[Anonymous]

# oebuild uclibc/uclibc_0.9.26.oe
NOTE: package uclibc-0.9.26-r0: task do_fetch started
NOTE: package uclibc-0.9.26-r0: task do_fetch completed
NOTE: package uclibc-0.9.26-r0: task do_build started
NOTE: package uclibc-0.9.26-r0: task do_build completed

And still get the same error... I\'m just testing, I was able to build the 4 recommended packages, and none after them... Any special step I could\'ve missed? As for stuff needed to be done, is there a task list being created?

[Anonymous]

Sorry can\'t help further until I\'m sat in front of my PC will have a look later for you.

I have made a start on the \"whats required to get compiler working list\" but am bogged down with work at the moment so may take a while.

Richard

[Anonymous]

Thank you!

Good luck in your work!

[Mickeyl]

Hmm... I wouldn\'t build different c libraries. That seriously mixes up things. You better use oemake btw. - that cares about dependencies. I have a function like that in my .bashrc:

Code: [Select]

function oe() { export OEDIR=/usr/local/projects/oe;

                export PATH=$OEDIR/bin:$PATH:/usr/local/arm/3.3.2/bin;

                export PKGDIR=/usr/local/projects/packages; cd $PKGDIR;

                export OEMASK="binutils|uclibc|avr-libc|gcc|initial|qte_2|qtopia|linux";

                export OEFILES=`/bin/ls $PKGDIR/*/*.oe 2>/dev/null|grep -v -E "$OEMASK"`; }

Then I can do \'oemake freedroid\' and all dependencies are automatically built.

[Richjn]

O.k

I\'ve had a chance to look now and Busybox only requires vitrual/libc so should have built o.k.

Mickeyl\'s .bashrc solution is much neater than using a shell script and ensures that your PATH contains everything needed. Just copy his text and replace your own directoiry paths where needed. To run just type oe (sorry obvious but just in case   )

I\'ve been using oebuild as oemake would screw up for me (Might have been me not the script) but maybe the script has been modified to clean things up, I haven\'t tried it for a while. (Guess I will now)

Richard

[Anonymous]

Where did everybody go? Is there things being done in the background? Or did everyone give up?

[vishnja]

http://www.openembedded.org/phpwiki/index..../GettingStarted is the getting started page I was talking about.


Si

working link would be:

http://openembedded.org/oe_wiki/index.php/.../GettingStarted

[Mickeyl]

Quick note before I leave to austria for a week skiing: We have just established the mailing list oe@handhelds.org. Major topics are 1.) Development of the build system OpenEmbedded itself and 2.) Development, Documentation, etc. of device-independent packages (i.e. 90% of what goes into a typical OpenZaurus linux distribution). For device-specific issues, the openzaurus-devel@lists.sf.net still should be the authority.

[Anonymous]

Have fun Mickey!