from your main build directory (the one that contains build.sh), type the following:
rm -rf backup-flame and then make sure the flame's display timeout is set to "never", since the backup pull will fail if the screen goes off. After that, you can try and re-build (make sure your flame is connected via USB, and that "adb devices" shows the device). - Jon ----- Original Message ----- > $ sudo ./build.sh -j1 > including device/generic/armv7-a-neon/vendorsetup.sh > including device/qcom/common/vendorsetup.sh > > ============================================ > PLATFORM_VERSION_CODENAME=REL > PLATFORM_VERSION=4.3 > TARGET_PRODUCT=flame > TARGET_BUILD_VARIANT=eng > TARGET_BUILD_TYPE=release > TARGET_BUILD_APPS= > TARGET_ARCH=arm > TARGET_ARCH_VARIANT=armv7-a-neon > TARGET_CPU_VARIANT=krait > HOST_ARCH=x86 > HOST_OS=linux > HOST_OS_EXTRA=Linux-3.13.0-30-generic-x86_64-with-Ubuntu-14.04-trusty > HOST_BUILD_TYPE=release > BUILD_ID=JSS15J > OUT_DIR=out > ============================================ > > Blob setup script has changed, re-running > Pulling files from ../../../backup-flame > cat: ../../../backup-flame/system/build.prop: missing file or directory > Pulling "libalsa-intf.so" > cp: impossibile eseguire stat di > "../../../backup-flame/system/lib/libalsa-intf.so": missing file or > directory > Failed to pull libalsa-intf.so. Giving up. > > > Build failed! < > > Build with |./build.sh -j1| for better messages > If all else fails, use |rm -rf objdir-gecko| to clobber gecko and |rm -rf > out| to clobber everything else. > > > I'm stuck here > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
