View Single Post
  #212 (permalink)  
Old 10-16-2010, 06:04 PM
natemcnutty's Avatar
natemcnutty
VIP Member
Offline
Threadstarter
 
Join Date: Nov 2009
Posts: 845
Reputation: 3070
natemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Wirelessly posted (Opera/9.80 (Windows Mobile; Opera Mini/5.1.21594/20.2497; U; en) Presto/2.5.25)

Quote:
Originally Posted by [ACL
]ignore those files for now since they arent working for me.

natemcnutty: what kinda os and version are you using to compile the kernel .. also what toolchain. Reason i ask is because i replicated my entire setup on the autobuild machine and it keeps crashing. Only differences are that my home machine is ubuntu 9.10 64bit while the auto is running 10.10 32bit. This really shouldnt make any difference but i really dont know why else it would cause android to crash.

Also im interested to see if another version would cause android crashes as well. Ive tried my old sense ui build and it runs fine with the nbh from the autobuild so whatever this autobuild machine is doing its just pissing off xdandroid and no other build. Anyone try neopeeks ?
I run 32bit Ubuntu 10.04.1 in a VM at work, and I have Ubuntu 10.10 now at home (just upgraded from 10.04.1). I have tried 3 toolchains: google 4.4.0, codesourcery 2008q3 and 2010q1.

I'll try 9.10 when I get home and see if that makes a difference.
__________________
Reply With Quote