RE: [U-Boot-Users] U-boot for MIPS - problem using latest gcc
First - I downloaded u-boot v1.0
Then - I unzipped it.
Then - I changed CROSS_COMPILE to be the latest MIPS compiler
Then - I did a make dbau1x00_config
Then - I did a make all.
Memsetup.S is definitely in board/dbau1x00/
So - the file is not missing.
You said:
missing or incorrect for your board configuration.
Since it is not missing - it must be "incorrect". What would "incorrect be"?
Thanks much
-----Original Message----- From: Wolfgang Denk [mailto:wd@denx.de] Sent: Wednesday, January 28, 2004 1:56 PM To: Jerry Walden Cc: u-boot-users@lists.sourceforge.net Subject: Re: [U-Boot-Users] U-boot for MIPS - problem using latest gcc
In message <603BA0CFF3788E46A0DB0918D9AA95100A0E2F33@sj580004wcom.int.lantronix.com
you wrote:
Yes. The file board/<yourname>/memsetup.S is missing / incorrect.
I do not understand the response. Are you saying that something is wrong with my file layout? Should I not be compiling this file? Basically - how do I fix the problem?
You got an error because "memsetup" was undefined; "memsetup" gets defined in board/<yourname>/memsetup.S - so obviously this file is missing or incorrect for your board configuration.
Best regards,
Wolfgang Denk
In message 603BA0CFF3788E46A0DB0918D9AA95100A0E2F3D@sj580004wcom.int.lantronix.com you wrote:
First - I downloaded u-boot v1.0
I could ask wy you use an old version, but it does not matter here.
Then - I changed CROSS_COMPILE to be the latest MIPS compiler
See below.
Then - I did a make dbau1x00_config Then - I did a make all. Memsetup.S is definitely in board/dbau1x00/ So - the file is not missing.
Indeed. And actually this is building fine:
-> tar jxf /opt/tarballs/u-boot-1.0.0.tar.bz2 -> cd u-boot-1.0.0 -> MAKEALL dbau1x00 rm -f include/config.h include/config.mk Configuring for dbau1x00 board... net.c: In function `NetStartAgain': net.c:492: warning: integer overflow in expression text data bss dec hex filename 112120 4760 17252 134132 20bf4 u-boot
Since it is not missing - it must be "incorrect". What would "incorrect be"?
Since all of your steps except one work fine here I can only speculate that the problem must be in the step where we do things differently: I use a working compiler.
Seems your toolchain has some problems?
Best regards,
Wolfgang Denk
participants (2)
-
Jerry Walden -
Wolfgang Denk