On Wed, May 6, 2015 at 2:38 PM, Gabriele Svelto <[email protected]>
wrote:
> The script is trying to pull binary blobs from the device.
I understand that. The problem is that the phone and the computer used
for building are thousands of miles apart. Namely, I use a Digital Ocean
instance with fast Interent access. Possibly I could download the blobs
manually, copy them to the build machine, and adapt `build.sh`
accordingly.
> If it's not rooted yet I imagine this isn't the case. What does 'adb
> shell ls -l /system' do if you plug the phone with adb enabled?
shell@msm8610:/ $ ls -l /system
drwxr-xr-x root root 2014-07-08 14:11 b2g
drwxr-xr-x root shell 2014-07-08 13:42 bin
lrw-r--r-- root root 2014-07-08 14:11 build.prop ->
/custpack/build.prop
drwxr-xr-x root root 1970-01-01 01:00 etc
drwxr-xr-x root root 2014-07-08 13:37 fonts
drwxr-xr-x root root 2014-07-08 13:42 lib
drwx------ root root 1970-01-01 01:00 lost+found
drwxr-xr-x root root 2014-07-08 13:28 media
-rw-r--r-- root root 13 2014-07-08 14:11 system.ver
drwxr-xr-x root root 2014-07-08 13:28 tts
drwxr-xr-x root root 2014-07-08 13:28 usr
drwxr-xr-x root shell 2014-07-08 13:41 vendor
drwxr-xr-x root shell 2014-07-08 13:41 xbin
Hm, that shell prompt hints what default config to use when building the
kernel. :-)
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
