On 1/7/07, Rob Savoye <[EMAIL PROTECTED]> wrote:
Ivan Krstić wrote: > Rob has posted here before. Adding him to CC to make sure he spots this > thread. Nope, hadn't seen this thread. You can grab the initial tarball from http://gnash.lulu.com/olpc. I added the crude patch I made to the config files. While this works for me Ubuntu 6.10 Edgy -> OLPC, it should also work on any GNU/Linux host, as I tried to include all the stuff GCC depends on at runtime. Use the "i386-olpc-linux" as your config triplet. Install the tarball in /usr/local. i386-olpc-linux-gcc is the compiler to use. I also added C++ support, since Gnash is written in C++. I cross compile by setting the additional configure arguments --prefix=/usr/local/olpc --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --target=i386-olpc-linux. I hear rumors somebody is adding Geode specific optimizations to GCC, if so, then this should actually be geode-olpc-linux, but I guess I'll worry about it when it shows up in GCC CVS. For now, I just treat it as the "manufacturer" field of the config triplet and build a stock linux tool chain. The main advantage of doing it this way is it keeps your host libraries from contaminating the cross build, which should avoid weird problems down the road. At some other time, we'd need to figure out how to keep all the libraries and headers up to date in the cross tool chain.
IIRC the new gcc 4.3 has geode specfic optimizations using -mtune=geode and -march=geode Is the crosstool really necessary if the "normal" gcc creates geode tuned x86 binaries just by using a switch? regards Manish Regmi
_______________________________________________ Devel mailing list [email protected] http://mailman.laptop.org/mailman/listinfo/devel
