MobileRead Forums - View Single Post

knc1 · 07-19-2012, 11:30 AM

The one we have (say: Thanks Rob) is a gcc-4.2 tool-chain built against uClibc.
Which is just fine for building static linked utilities.

So this one will be a gcc-4.7 tool-chain built against glibc (which may or may not work for producing kindle native applications). Maybe, if we are lucky, and the wind is blowing from the correct direction. If it doesn't, I will have to go back to the most recent gcc-4.6 compiler release.

Will include the C and C++ and C# front-ends.
Will ignore the Ada, Cobal, Fortran, VHDL, etc, etc, etc at my own request.

Sorry, no C# - that is one of the few languages that gcc does not do.

And all of this is going on as a "native build" within our QEMU-1.1.1 emulated environment.
If it seems I am always at the keyboard when someone posts here -
Well, just try to remember how slow a 300Mhz machine is.

Thank goodness, nobody wants OpenOffice on a Kindle.

07-19-2012, 11:30 AM	#52
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	The one we have (say: Thanks Rob) is a gcc-4.2 tool-chain built against uClibc. Which is just fine for building static linked utilities. So this one will be a gcc-4.7 tool-chain built against glibc (which may or may not work for producing kindle native applications). Maybe, if we are lucky, and the wind is blowing from the correct direction. If it doesn't, I will have to go back to the most recent gcc-4.6 compiler release. Will include the C and C++ and C# front-ends. Will ignore the Ada, Cobal, Fortran, VHDL, etc, etc, etc at my own request. Sorry, no C# - that is one of the few languages that gcc does not do. And all of this is going on as a "native build" within our QEMU-1.1.1 emulated environment. If it seems I am always at the keyboard when someone posts here - Well, just try to remember how slow a 300Mhz machine is. Thank goodness, nobody wants OpenOffice on a Kindle. Last edited by knc1; 07-19-2012 at 11:56 AM.