[Android Builders Collective] mslatter:
I'm not sure if anyone can help as I've worked on this for literally weeks and as soon as I get over one wall, I hit another. This time I 'feel' like I'm close, but can't find anything online because the AT&T LG3 d850 seems to be a difficult device to build for.

I have literally installed Ubuntu 14.04 5 times from scratch. On the last one, I decided to use a virtualbox I found on XDA and cloned my setup so I could wipe (6 or 7 times) and start fresh easily. I got almost as close as I am now, but couldn't get the VM to recognize the USB, while my regular machine saw it just fine....so I deleted the VM and am back on a clean install of Ubuntu 14.04, with 8 cores and 16 gig of RAM.

I followed the instructions I found here: http://xdaforums.com/chef-central/android/tutorial-compile-lollipop-ubuntu-t2929410 except I used Slims repo of:

repo init -u git://github.com/SlimRoms/platform_manifest.git -b lp5.0-caf

I also added this to the slim_manifes.xml (which is all that's in it at this point)

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="SlimRoms/device_lge_d850" path="device/lge/d850" remote="github" revision="lp5.0" />
<project name="SlimRoms/device_lge_g3-common" path="device/lge/g3-common" remote="github" revision="lp5.0" />
<project name="SlimRoms/kernel_lge_g3" path="kernel/lge/g3" remote="github" revision="lp5.0" />
<project name="SlimRoms/device_qcom_common" path="device/qcom/common" remote="github" revision="lp5.0" />
<project name="TheLoonyBin/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="lp5.0" />
<project name="TheLoonyBin/proprietary_vendor_qcom" path="vendor/qcom" remote="github" revision="lp5.0" />
<project name="TheLoonyBin/proprietary_vendor_broadcom" path="vendor/broadcom" remote="github" revision="lp5.0" />
</manifest>

I didn't follow the "How to Add a Device To The List" exactly because I found my device under: /home/building/slim/device/lge/d850

Although, tonight I decided to run the './extract-files.sh' from my phone while in that d850 directory, the script seemed to run with out error, but I'm still getting the same Make error.

Breakfast d850 no longer errors out, nice clean box of info.

Lunch (then selecting the d850-userdebug - can't remember the number) runs with no errors either.

However, the 'make clean' or 'brunch' (I tried both) errors out after a BUNCH of processing, with the same closing of:

Export includes file: external/libxml2/Android.mk -- /home/building/slim/out/target/product/d850/obj/STATIC_LIBRARIES/libxml2_intermediates/export_includes
Import includes file: /home/building/slim/out/target/product/d850/obj/SHARED_LIBRARIES/libnfc-nci_intermediates/import_includes
Import includes file: /home/building/slim/out/target/product/d850/obj/STATIC_LIBRARIES/libxml2_intermediates/import_includes
Export includes file: packages/apps/Nfc/nci/jni/Android.mk -- /home/building/slim/out/target/product/d850/obj/SHARED_LIBRARIES/libnfc_nci_jni_intermediates/export_includes
make: *** No rule to make target `/home/building/slim/out/target/product/d850/obj/SHARED_LIBRARIES/libpac_intermediates/export_includes', needed by '/home/building/slim/out/target/product/d850/obj/SHARED_LIBRARIES/libjni_pacprocessor_intermediates/import_includes'. Stop.
make: *** Waiting for unfinished jobs....
warning: [options] bootstrap class path not set in conjunction with -source 1.6
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 warning
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

Now I did have an error of " no private recovery resources for target_device d850" earlier this evening, but from re-doing repos and re-doing breakfast e.t.c., that error no longer appears....not sure if that's related to it?

I thought I could do this with out help, but if anyone can point me in the right direction, I'd appreciate it very much! Just trying to get it together before 5.1 comes out....

Thanks in advance.