[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Actually no, looks like I did have some errors right at the end ...

/home/carvsdriver/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: error: /home/carvsdriver/cm10/output/cm10/target/product/skyrocket/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/SurfaceFlinger.o: multiple definition of 'android::Singleton<qdutils::QCCompositionType>::sLock'
/home/carvsdriver/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/carvsdriver/cm10/output/cm10/target/product/skyrocket/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/DisplayHardware/HWComposer.o: previous definition here
/home/carvsdriver/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: error: /home/carvsdriver/cm10/output/cm10/target/product/skyrocket/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/SurfaceFlinger.o: multiple definition of 'android::Singleton<qdutils::QCCompositionType>::sInstance'
/home/carvsdriver/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/carvsdriver/cm10/output/cm10/target/product/skyrocket/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/DisplayHardware/HWComposer.o: previous definition here
[B]collect2: ld returned 1 exit status[/B]
make: *** [/home/carvsdriver/cm10/output/cm10/target/product/skyrocket/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/LINKED/libsurfaceflinger.so] [B]Error 1[/B]
make: *** Waiting for unfinished jobs....
carvsdriver@ubuntu:~/cm10$

---------- Post added at 10:38 AM ---------- Previous post was at 10:16 AM ----------

Hmmm ... went back through the steps, looks like I'm missing the platform tools from the SDK. Installing them now and will give it another rip.

---------- Post added at 10:41 AM ---------- Previous post was at 10:38 AM ----------

Beats me dude, I'm just following the steps to get a clean first build before I start digging into it and breaking stuff on purpose.

I get lots of warnings along the entire build process - something I tend to see in other C projects I build, so I mostly ignore them.

Is it normal in this case?

Also, I think the build mostly worked, I have what looks like all of the final files built ...

carvsdriver@ubuntu:~/cm10/output/cm10/target/product/skyrocket$ ls -l
total 5376
-rw-rw-r-- 1 carvsdriver carvsdriver 22925 Oct 12 20:40 clean_steps.mk
drwxrwxr-x 2 carvsdriver carvsdriver 4096 Oct 12 17:04 data
drwxrwxr-x 3 carvsdriver carvsdriver 4096 Oct 12 18:32 device
drwxrwxr-x 3 carvsdriver carvsdriver 4096 Oct 12 18:31 external
drwxrwxr-x 2 carvsdriver carvsdriver 4096 Oct 12 18:30 fake_packages
-rwxrwxr-x 1 carvsdriver carvsdriver 5099328 Oct 12 17:17 kernel
drwxrwxr-x 16 carvsdriver carvsdriver 4096 Oct 12 19:26 obj
-rw-rw-r-- 1 carvsdriver carvsdriver 595 Oct 12 20:40 previous_build_config.mk
-rw-rw-r-- 1 carvsdriver carvsdriver 336070 Oct 12 19:26 ramdisk.img
drwxrwxr-x 4 carvsdriver carvsdriver 4096 Oct 12 18:33 recovery
drwxrwxr-x 9 carvsdriver carvsdriver 4096 Oct 12 18:33 root
drwxrwxr-x 4 carvsdriver carvsdriver 4096 Oct 12 18:33 symbols
drwxrwxr-x 8 carvsdriver carvsdriver 4096 Oct 12 19:26 system