From: Chris Jones <cjones@sutus.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-boot for MIPS problems compiling...
Date: Thu, 16 Sep 2004 11:07:15 -0700 [thread overview]
Message-ID: <20040916180715.GW32080@qworks.ca> (raw)
In-Reply-To: <1095327467.14046.19.camel@fortress>
Lief;
On Thu, Sep 16, 2004 at 11:37:48AM +0200, Leif Lindholm wrote:
> Could you give a more detailed description of your problems?
>
> I had some problems finding working versions of gcc/binutils, but
> finally succeeded with binutils 2.13 and gcc 3.2.3.
<SNIP>
> Leif
Thanks so much for your quick reply. I was going to do some work on this
board as well independently in attempt to see if I can't get the machine to
boot from an ide HDD. I'll keep bugging you for the patches offline,
but for the benefit of everyone else I'll elaborate a little more here:
Cross-compiling from x86 using: a custom built (crosstool) toolchain
gcc3.3.2-glibc2.3.2-binutils-2.15; I get this error:
make[1]: Leaving directory `/home/cjones/dev/boot/u-boot-1.1.1/post/cpu'
mipsel-unknown-linux-gnu-gcc -Wa,-gstabs -D__ASSEMBLY__ -g -Os
-D__KERNEL__ -DTEXT_BASE=0xbfc00000
-I/home/cjones/dev/boot/u-boot-1.1.1/include -fno-builtin -ffreestanding
-nostdinc -isystem /usr/lib/gcc-lib/i486-linux/3.3.4/include -pipe
-DCONFIG_MIPS -D__MIPS__ -mips32 -c -o cpu/mips/start.o
/home/cjones/dev/boot/u-boot-1.1.1/cpu/mips/start.S
/home/cjones/dev/boot/u-boot-1.1.1/cpu/mips/start.S: Assembler messages:
/home/cjones/dev/boot/u-boot-1.1.1/cpu/mips/start.S:246: Error: Cannot
branch to undefined symbol.
/home/cjones/dev/boot/u-boot-1.1.1/cpu/mips/start.S:251: Error: Cannot
branch to undefined symbol.
/home/cjones/dev/boot/u-boot-1.1.1/cpu/mips/start.S:263: Error: Cannot
branch to undefined symbol.
make: *** [cpu/mips/start.o] Error 1
I've seen other people compiling for the Au1x00 series have this similar
problem.
Not unsurprisingly while compiling natively with a similar toolchain:
gcc-3.2.3,glibc-2.3.2,binutils-2.15 I get the same errors.
I know my toolchain is not BAD as I can perfectly build and execute the
resulting kernel; however, it may not be compatible with they way things
are done in u-boot.
Perhaps Wolfgang or the people at DENX could put some input into their
toolchain version(s). I suppose I should just download it and check it out.
But I would really like to be in control of my own toolchain.
Cheers,
-=chris
--
Chris Jones | Software Developer | Sutus, Inc.
t: +1.604.987.8866 x 2204 | e: cjones at sutus.com
next prev parent reply other threads:[~2004-09-16 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 20:30 [U-Boot-Users] U-boot for MIPS problems compiling Chris Jones
2004-09-16 9:37 ` Leif Lindholm
2004-09-16 18:07 ` Chris Jones [this message]
2004-09-16 23:28 ` Wolfgang Denk
2004-09-21 1:34 ` Chris Jones
2004-09-21 5:31 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040916180715.GW32080@qworks.ca \
--to=cjones@sutus.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox