[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [microblaze-uclinux] uclinux and pthreads



Hi Joshua,

Joshua Moore-Oliva wrote:

> I have read through those files and now the whole readme.txt makes a little more sense..  Up until now I had only extracted the microblaze elf tools and tried to 
> compile with those.  I thought that the rest was only required if I was actually downloading programs to the fpga.
> 
> After my enlightenment, am I correct to assume that I first must follow every step in the readme.txt to generate a kernel for ucLinux, and then reference into that built and 
> configured kernel to compile a user app as per the wiki instructions?

Well you at least need a configured kernel and uClinux-dist (where the 
libraries live).  You don't actually need to build the kernel, but you 
will need to build the libs.

It's possible to build an gcc toolchain to directly output uclinux 
executables (so that "mb-uclinux-gcc -o myapp myapp.c" would work as 
expected), but it's not trivial.  Since every microblaze system can be 
different, with different CPU support for mul/div/FPU and so on, you 
need different versions of the libraries to link against.  This 
combinational explosion of options requires the EDK to distribute around 
20 versions of the newlib library, each built with different CPU options.

It's easier just to rebuild the libs from source each time you change 
the CPU, and this is supported by default in the uClinux-dist build 
architecture.

Cheers,

John

___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/