Mark Mitchell wrote: > Understood. Out of curiousity, do you eventually build a bfin-uclinux > compiler, once you've built uClibc, or do you just use the bfin-elf > compiler on uClinux?
We build up several versions of uClibc with bfin-elf, and then we build two additional separate toolchains: bfin-uclinux and bfin-linux-uclibc. The former produces flat binaries (a very simple binary format), while the latter produces ELF FD-PIC binaries (using the -mfdpic), which behave essentially like normal ELF binaries and support shared libraries and dynamic loading. In the past we used to allow -mfdpic with the bfin-uclinux toolchain, but the gcc build system didn't cope too well and we couldn't get it to build shared libraries for one set of multilibs and not for the other, so we split things up. We also need a bfin-elf toolchain, and while bare hardware applications can't use -mfdpic or -mid-shared-library, in the past it hasn't hurt to provide these multilibs, and it allows us to build up uClibc quite easily. I guess I could try to build up C-only versions of bfin-uclinux and bfin-linux-uclibc first and use them for building uClibc, although I'm certain to get complaints about how the build script suddenly takes so much longer, and it all seems somewhat more complicated than necessary. Bernd -- This footer brought to you by insane German lawmakers. Analog Devices GmbH Wilhelm-Wagenfeld-Str. 6 80807 Muenchen Sitz der Gesellschaft Muenchen, Registergericht Muenchen HRB 40368 Geschaeftsfuehrer Thomas Wessel, William A. Martin, Margaret Seif
