Just for let people know, as people have asked me either personally, or indirectly in other threads:
I have stalled my efforts for the devtools project until a 2.6.16+ kernel and new glibc (2.4) is ported to the ls-pro platform (the glibc port meaning for stock/openlink firmwares....not FreeLink or GenLink). The reason is the stock firmware uses a development glibc and a non-standard gcc in order to can experiment new Arm abi (eabi) support. The eabi is fully supported in linux-2.6.16 and in glibc-2.4+ . I personally believe its better to produce a cleaner set of tools w/ clean/full eabi support, and to remove all the development/experimental stuff. I hope you all understand my reasons for delaying my "arm-tools" project.
I am aware that the latest package found in the DEV section does not compile everything correctly. The list of bugs include partially broken includes, bison, libtool, and seg-faults cause by gcc. Some of the issues can/have been fixed in various other threads. Time permitting, I may produce an intermittent release of arm-tools (pre "clean" release) that will include fixes that I and others have discovered.
Also, I know some have expressed confusion with the arm-tools package as to when it ought to be used. The package is primarily designed for the stock, modified-stock, and OpenLink firmwares. FreeLink and GenLink use different toolchains, and consequently have there own accompanying native toolsets (devtools). There are some similarities among the three major variants in their toolchains (i.e. current GenLink uses stock glibc), but users should use toolchains designed for the specific firmware as each firmwares are different operating systems.
I appreciated the community's understanding and express my apologies for the inconveniences.
Thanks and Kindest Regards,
Jon aka jonli447