about mb-gcc error???

what's wrong with following error????

[root@184pc140 bin]# ./mb-gcc hello.c /home/devel/uclinux/bin/mb_tools/bin/../lib/gcc/microblaze/ 3.4.1/../../../../microblaze/lib/libc.a(write.o): In function `write': write.o(.text+0x34): undefined reference to `outbyte' write.o(.text+0x58): undefined reference to `outbyte' /home/devel/uclinux/bin/mb_tools/bin/../lib/gcc/microblaze/ 3.4.1/../../../../microblaze/lib/libc.a(read.o): In function `read': read.o(.text+0x2c): undefined reference to `inbyte' collect2: ld returned 1 exit status
Reply to
kobelai15
Loading thread data ...

Hi, There's nothing wrong with the error. Quite the contrary. It shows you that the linker (ld) is able to do correct checks of the used references in your compiled object codes. Furthermore it is so kind to inform you about missing ones and that it can't proceed it's work unless YOU provide consistent sources and/or libraries to work with. ;-)

So where do you think outbyte and inbyte come from? The linker wants to know. You have to tell it.

Good luck Eilert

snipped-for-privacy@gmail.com schrieb:

Reply to
backhus

In EDK, please set your STDIN and STDOUT to whatever RS232 UART's that you have.

-- parag

Reply to
beeraka

inbyte and outbyte are provided by the Xilinx low level libxil.a library file. However, by invoking gcc from the command line with no extra options (like link path etc), the linker has been unable to find this.

What are you trying to do? Build a C app for MicroBlaze in standalone mode, or for Linux? If you are building Linux apps, grab PetaLinux (developer.petalogix.com) which includes a standalone MicroBlaze Linux toolchain - you can just do

microblaze-uclinux-gcc -o hello hello.c

and it will magincally produce a Linux-ready binary.

Regards,

John

Reply to
John Williams

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.