MobileRead Forums - View Single Post

geekmaster · 05-06-2016, 12:45 PM

I tried building gcc from the amazon source code for my K1, but it errored out during the compile -- perhaps a configuration error. So I tried another prebuilt toolchain:
https://github.com/samsheff/Amazon-K...ross-Toolchain

However, a "hello world" built with that segfaults on my K1. Windows toolchains are much more backwards compatible. Why does linux need a specific flavor of a specific version of a toolchain (and even with specific flags, for kernel builds)? How do sane people figure out which specific set of options?

There is too much to read and too little time. And as I said, the tcc for kindles creates code that also does not work on my K1. What is so different about an armv5 that all the existing kindle binaries either are not recognized as executable, or get "illegal instruction", or segfault? I need to put this aside for a bit, and go outdoors before it starts snowing again...

05-06-2016, 12:45 PM	#32
geekmaster Carpe diem, c'est la vie. Posts: 6,433 Karma: 10773670 Join Date: Nov 2011 Location: Multiverse 6627A Device: K1 to PW3	I tried building gcc from the amazon source code for my K1, but it errored out during the compile -- perhaps a configuration error. So I tried another prebuilt toolchain: https://github.com/samsheff/Amazon-K...ross-Toolchain However, a "hello world" built with that segfaults on my K1. Windows toolchains are much more backwards compatible. Why does linux need a specific flavor of a specific version of a toolchain (and even with specific flags, for kernel builds)? How do sane people figure out which specific set of options? There is too much to read and too little time. And as I said, the tcc for kindles creates code that also does not work on my K1. What is so different about an armv5 that all the existing kindle binaries either are not recognized as executable, or get "illegal instruction", or segfault? I need to put this aside for a bit, and go outdoors before it starts snowing again...