2008-04-08 08:56:55     errors with complining the u-boot1.1.6

Document created by Aaronwu Employee on Sep 17, 2013
Version 1Show Document
  • View in full screen mode

2008-04-08 08:56:55     errors with complining the u-boot1.1.6

Pafone Lee (CHINA)

Message: 53841    HI,everyone

 

I'm new with bf and uclinux,now I have a question and need your help.

 

I have installed the latest toolchain,(blackfin-toolchain-08r1-8.i386.rpm)

 

But when I complined the uboot-1.1.6,errors were found

 

bfin-uclinux-ld -g  -Ttext 0x1000 \

 

 

 

                        -o hello_world -e _hello_world hello_world.o libstubs.a \

 

 

 

                        -L. -lgcc

 

 

 

/opt/uClinux/bfin-uclinux/bin/bfin-uclinux-ld.real:can not found -lgcc

 

 

 

And I have saw familar problems asked in the forum,some one said that the uclib must to be installed.

 

But the docs did not mention about it,should I install the uclib,and which uclib should I install?

 

blackfin-toolchain-uclibc-full-08r1-8.i386.rpm or blackfin-toolchain-uclibc-default-08r1-8.i386.rpm?what the content uclibs contains and what differences between them?

 

best rgd.

TranslateQuoteReplyEditDelete

 

 

2008-04-08 10:38:52     Re: errors with complining the u-boot1.1.6

Mike Frysinger (UNITED STATES)

Message: 53845    if you dont install a uclibc package, your toolchain is incomplete and broken

 

the release notes explains things:

http://blackfin.uclinux.org/gf/project/toolchain/frs/?action=FrsReleaseView&release_id=375

QuoteReplyEditDelete

 

 

2008-04-09 04:09:15     Re: errors with complining the u-boot1.1.6

Pafone Lee (CHINA)

Message: 53885   

 

Thank you , Mike.

 

I have installed the default uclib and the problem was sovled.But now I have another problem .

 

start.s: Assembler messages:

 

start.s:49: Error: parse error. Input text was entry.

 

start.s:49: Error:

 

start.s:52: Error: parse error. Input text was LO.

 

start.s:52: Error:

 

start.s:53: Error: parse error. Input text was HI.

 

start.s:53: Error:

 

start.s:63: Error: parse error. Input text was LO.

 

start.s:63: Error:

 

start.s:64: Error: parse error. Input text was HI.

 

start.s:64: Error:

 

start.s:66: Error: parse error. Input text was HI.

 

start.s:66: Error:

 

start.s:73: Error: parse error. Input text was serial_early_init.

 

start.s:73: Error:

 

start.s:74: Error: parse error. Input text was serial_early_set_baud.

 

...

 

make[1]: *** [start.o] error 1

 

make[1]: Leaving directory `/root/dspwork/uboot/cpu/blackfin'

 

make: *** [cpu/blackfin/start.o] error 2

 

Is it the as of bfin do not have the keyworlds such as entry,LO,and HI?

 

What I should do to deal with it?

 

 

 

best rgd.

 

 

 

 

TranslateQuoteReplyEditDelete

 

 

2008-04-09 12:16:45     Re: errors with complining the u-boot1.1.6

Mike Frysinger (UNITED STATES)

Message: 53936    there is no "start.s" file anywhere which means you probably created it

QuoteReplyEditDelete

 

 

2008-04-09 22:46:56     Re: errors with complining the u-boot1.1.6

Pafone Lee (CHINA)

Message: 53952   

 

Thx

 

The fact is I didn't creat any file myself.

 

I just did as follows:

 

make distclean

 

make bf533-ezkit_config

 

make

 

And I checked,the start.S did exist in 'u-boot-1.1.6-2008R1\cpu\blackfin'

 

Is there any problem to untar the tar file with winrar,I use the winrar to untar the u-boot which I downloaded from net.

 

start.S

TranslateQuoteReplyEditDelete

 

 

2008-04-09 22:56:26     Re: errors with complining the u-boot1.1.6

Mike Frysinger (UNITED STATES)

Message: 53955    start.s is not the same thing as start.S

 

you should never unpack a tar file in Windows as it will simply screw things up.  do it properly in Linux using tar.

QuoteReplyEditDelete

 

 

2008-04-11 04:04:49     回复: Re: errors with complining the u-boot1.1.6

Pafone Lee (CHINA)

Message: 54073   

 

Thanks a lot. Now I can make the uboot successfully.

 

Here are some suggestion for new guys,

 

do all the things in Linux, if you unpack a packeged file with winrar , the file ext name may be changed. ie. start.S to start.s

 

Thanks very much for Mike's help.

Attachments

Outcomes