2009-01-02 05:26:50 kick start problem
Rui Cao (SINGAPORE)
Message: 67289
Hi, Guys,
I was trying to kick start my BlackFin uCLinux proj.
and I followed the instruction in the pdf document come with the 533-Stamp board.
when trying to compile uCLinux,
I got error msg as follow
[root@localhost uClinux-dist]# make xconfig
config/mkconfig > config.in
make -C /home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist/config/scripts tkparse
make[1]: Entering directory `/home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist/config/scripts'
make[1]: `tkparse' is up to date.
make[1]: Leaving directory `/home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist/config/scripts'
ARCH=dummy /home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist/config/scripts/tkparse < config.in > config.tmp
cat /home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist/config/scripts/header.tk >> ./config.tk
cat config.tmp >> config.tk
rm -f config.tmp
echo "set defaults \"/dev/null\"" >> config.tk
echo "set help_file \"config/Configure.help\"" >> config.tk
cat /home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist/config/scripts/tail.tk >> config.tk
chmod 755 config.tk
make: wish: Command not found
make: *** [xconfig] Error 127
what is the 'wish' command here? how to solve this? Is there any problem with the makefile?
QuoteReplyEditDelete
2009-01-02 05:36:26 Re: kick start problem
Mike Frysinger (UNITED STATES)
Message: 67290
you cant use TCL/TK unless you actually install the packages on your development system
please read the documentation:
http://docs.blackfin.uclinux.org/doku.php?id=installing_linux
QuoteReplyEditDelete
2009-01-04 09:51:00 Re: kick start problem
Rui Cao (SINGAPORE)
Message: 67330
Hi, Mike,
thanks for the hint.
I will try updating everything first
QuoteReplyEditDelete
2009-01-04 22:37:22 Re: kick start problem
Rui Cao (SINGAPORE)
Message: 67343
Hi, Mike,
I hv installed a few packets that might be missing previously.
And it compiled at first, then a source file error came in. here's the snap-shot.
[root@localhost uClinux-dist]# make xconfig
config/mkconfig > config.in
make -C /home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist/config/scripts tkparse
make[1]: Entering directory `/home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist/config/scripts'
make[1]: `tkparse' is up to date.
make[1]: Leaving directory `/home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist/config/scripts'
ARCH=dummy /home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist/config/scripts/tkparse < config.in > config.tmp
cat /home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist/config/scripts/header.tk >> ./config.tk
cat config.tmp >> config.tk
rm -f config.tmp
echo "set defaults \"/dev/null\"" >> config.tk
echo "set help_file \"config/Configure.help\"" >> config.tk
cat /home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist/config/scripts/tail.tk >> config.tk
chmod 755 config.tk
make[1]: Entering directory `/home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist'
make ARCH=bfinnommu CROSS_COMPILE=bfin-elf- -C linux-2.6.x xconfig
make[2]: Entering directory `/home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist/linux-2.6.x'
HOSTCC scripts/kconfig/mconf.o
scripts/kconfig/mconf.c:91: error: static declaration of ‘current_menu’ follows non-static declaration
scripts/kconfig/lkc.h:63: error: previous declaration of ‘current_menu’ was here
make[3]: *** [scripts/kconfig/mconf.o] Error 1
make[2]: *** [xconfig] Error 2
make[2]: Leaving directory `/home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist/linux-2.6.x'
make[1]: *** [linux_xconfig] Error 2
make[1]: Leaving directory `/home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist'
make: *** [xconfig] Error 2
[root@localhost uClinux-dist]#
I tried to fix the conflict definition of 'current_menu', and more errors appeared.
Should I continue fixing them or do I still missing sth here?
QuoteReplyEditDelete
2009-01-04 22:56:09 Re: kick start problem
Mike Frysinger (UNITED STATES)
Message: 67344
from your output:
make ARCH=bfinnommu CROSS_COMPILE=bfin-elf- -C linux-2.6.x xconfig
you're clearly not using the latest release (or anything even close to resembling recent). download 2008R1.5 and try again.
QuoteReplyEditDelete
2009-01-05 01:01:20 Re: kick start problem
Rui Cao (SINGAPORE)
Message: 67348
Yap, it works with the latest package.
thanks, Mike.
QuoteReplyEditDelete
2009-01-05 03:27:27 Re: kick start problem
Rui Cao (SINGAPORE)
Message: 67350
another problem, as expected.
when it came to 'Kernel/Library/Defaults Selection' tab,
for the 'Libc' selection, it says 'Libc is None', unlike before in the old version, which was 'uCLibc'.
Is it ok leave it as 'Libc is None'?
QuoteReplyEditDelete
2009-01-05 07:51:04 Re: kick start problem
Robin Getz (UNITED STATES)
Message: 67381
Rui:
Yes - leave the libc setting to none - it is part of the toolchain, not the uClinux-dist now.
-Robin
QuoteReplyEditDelete
2009-01-05 20:54:44 Re: kick start problem
Rui Cao (SINGAPORE)
Message: 67399
woops...
then I guess, I need to update my tool chain to the latest version, right?
QuoteReplyEditDelete
2009-01-05 21:21:46 Re: kick start problem
Mike Frysinger (UNITED STATES)
Message: 67401
please read the FAQ (Why do I need to use the same version of toolchain/kernel/uClibc/U-boot/uClinux-dist?)
http://docs.blackfin.uclinux.org/doku.php?id=faq
QuoteReplyEditDelete
2009-01-06 00:57:54 Re: kick start problem
Rui Cao (SINGAPORE)
Message: 67415
did anyone face this problem when finally doing a 'make'
bfin-uclinux-gcc -I../libc/include -O2 -pipe -fno-builtin -Wall -DEMBED -D__uClinux__ -isystem /home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist.R1.1-RC3/staging/usr/include -g -DFLOATS=1 -DL_printf ../libc/stdio2/printf.c -c -o printf.o
In file included from ../libc/stdio2/printf.c:27:
../libc/include/stdarg.h:3:28: error: machine/stdarg.h: No such file or directory
In file included from ../libc/stdio2/printf.c:34:
../libc/include/stdio.h:125: error: expected declaration specifiers or ‘...’ before ‘va_list’
../libc/include/stdio.h:126: error: expected declaration specifiers or ‘...’ before ‘va_list’
.....
stdarg.h is simply
#ifndef _STDARG_H
#define _STDARG_H
#include <machine/stdarg.h>
#endif
but I did not see ../machine/ folder
the compiled package version is 2007R1.1-RC3
QuoteReplyEditDelete
2009-01-06 01:02:06 Re: kick start problem
Rui Cao (SINGAPORE)
Message: 67416
the PATH variable was added to the system.
the compilation took around 10 mins, and was stopped at the error shown above.
Here is last paragraph of the msg.
bfin-uclinux-gcc -O2 -pipe -fno-builtin -Wall -DEMBED -D__uClinux__ -isystem /home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist.R1.1-RC3/staging/usr/include -g -isystem /home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist.R1.1-RC3/staging/usr/include -c -o mtherr.o mtherr.c
bfin-uclinux-gcc -I../libc/include -O2 -pipe -fno-builtin -Wall -DEMBED -D__uClinux__ -isystem /home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist.R1.1-RC3/staging/usr/include -g -DFLOATS=1 -DL_printf ../libc/stdio2/printf.c -c -o printf.o
In file included from ../libc/stdio2/printf.c:27:
../libc/include/stdarg.h:3:28: error: machine/stdarg.h: No such file or directory
In file included from ../libc/stdio2/printf.c:34:
../libc/include/stdio.h:125: error: expected declaration specifiers or ‘...’ before ‘va_list’
../libc/include/stdio.h:126: error: expected declaration specifiers or ‘...’ before ‘va_list’
../libc/include/stdio.h:127: error: expected declaration specifiers or ‘...’ before ‘va_list’
../libc/include/stdio.h:129: error: expected declaration specifiers or ‘...’ before ‘va_list’
../libc/include/stdio.h:130: error: expected declaration specifiers or ‘...’ before ‘va_list’
../libc/include/stdio.h:131: error: expected declaration specifiers or ‘...’ before ‘va_list’
../libc/include/stdio.h:132: error: expected declaration specifiers or ‘...’ before ‘va_list’
../libc/stdio2/printf.c:36: error: expected declaration specifiers or ‘...’ before ‘va_list’
../libc/stdio2/printf.c: In function ‘printf’:
../libc/stdio2/printf.c:48: error: ‘va_list’ undeclared (first use in this function)
../libc/stdio2/printf.c:48: error: (Each undeclared identifier is reported only once
../libc/stdio2/printf.c:48: error: for each function it appears in.)
../libc/stdio2/printf.c:48: error: expected ‘;’ before ‘ptr’
../libc/stdio2/printf.c:51: warning: implicit declaration of function ‘va_start’
../libc/stdio2/printf.c:51: error: ‘ptr’ undeclared (first use in this function)
../libc/stdio2/printf.c:52: error: too many arguments to function ‘vfnprintf’
../libc/stdio2/printf.c:53: warning: implicit declaration of function ‘va_end’
make[2]: *** [printf.o] Error 1
make[2]: Leaving directory `/home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist.R1.1-RC3/lib/libm'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/dreamcase/Works/remoteminal/OS_boot/uClinux-dist.R1.1-RC3/lib'
make: *** [subdirs] Error 1
QuoteReplyEditDelete
2009-01-06 01:34:01 Re: kick start problem
Mike Frysinger (UNITED STATES)
Message: 67419
you selected the wrong C library in the toplevel config. really you should upgrade to 2008R1.5 and then it wouldnt be possible to hit this error as we've disabled the code.
QuoteReplyEditDelete
2009-01-06 02:23:29 Re: kick start problem
Rui Cao (SINGAPORE)
Message: 67427
Hi, Mike,
2008R1.5 sounds fine, except one problem.
the uClinux-dist is '2008R1.5-RC3', while the toolchain I downloaded all labled '-toolchain-08r1.5-14.i386.rpm',.
the '-RC3' and '-08R1.5-RC14' doesn't seem tally.
it could just be a confidence problem.
but do they match each other?
QuoteReplyEditDelete
2009-01-06 02:37:15 Re: kick start problem
Mike Frysinger (UNITED STATES)
Message: 67428
the rc status doesnt matter, only the major version
QuoteReplyEditDelete
2009-01-06 03:42:29 Re: kick start problem
Rui Cao (SINGAPORE)
Message: 67433
yes, it compiles now.
thanks, guys.
I will keep you guys posted on my progress.
I made my own BlackFin board.
BF533+Spartan IIIE 1600K, boot up controlled by a silicon lab MCU.
the front-end is to interface with IF input, output is to a 10/100-BaseT ethernet, alternatively it also goes to a video interface to a display daughter card, which was made seperately.
Hardware seems ok, I did a few test c code to test peripherals. Now comes to the OS stage.
Beginer, don't know take how long.