Thread: Geekmaster's adventures in K1 spelunking
View Single Post
Old 05-07-2016, 09:32 AM   #44
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by knc1 View Post
I don't recall any of what you quoted - mine "just worked".
Those quotes were from a link on the page you linked. Sadly, that armv5b toolchain also built code that does not work on my k1 (not found and/or segfault issues).

I noticed that tcc configure supports options for armv4 (and also cross compiling). Time to play with that for a bit, though I will still need a real gcc...

I am not sure why we seem to need a unique toolchain for each device we intend to support. There MUST be some compile flags to set to generate armv4 code on a modern device -- I feel like such a noob slogging in this toolchain muckery (too much time in the mainframe COBOL and MS windows development worlds).
geekmaster is offline   Reply With Quote