789040 - No busybox on the b2g otoro device (again)

Status: RESOLVED INCOMPLETE

(Firefox OS Graveyard :: GonkIntegration, defect)

Description

[Justin Lebar (not reading bugmail)]

glandium added to the wiki [1]:

> As of August 7, 2012, building B2G builds busybox. Symbolic links for commands are 
> however not enabled by default. They can be enabled by adding the following to .config:
>
>    export BB_ADD_SYMLINKS=true

However, I grep'ed my whole b2g directory and didn't find any file containing BB_ADD_SYMLINKS.  So I think this doesn't work any longer.

Separately, I've been unable to chmod 777 files I've uploaded onto the device -- perhaps this is part of how we're locking it down? -- which keeps me from uploading busybox manually.

[1] https://intranet.mozilla.org/B2G_Team/Otoro

Comment 1

[Mike Hommey [:glandium]]

See https://github.com/mozilla-b2g/b2g-manifest/commit/8277d33c341cbe6517e643b9ec9a1be1b1ba8dd6

Comment 2

[Justin Lebar (not reading bugmail)]

mwu, what do we need to do to revert the change in comment 1?  Do you know what was going wrong with the BB build on MacOS?

Comment 3

[Michael Wu [:mwu]]

I think there were some header issues - possibly something missing.

chmod 777 should still work on eng builds, which all otoro builds should be unless you go out of your way to change it. Just make sure you do a adb remount first.

Comment 4

[Mike Hommey [:glandium]]

(In reply to Justin Lebar [:jlebar] from comment #2)
> mwu, what do we need to do to revert the change in comment 1?  Do you know
> what was going wrong with the BB build on MacOS?

The problem is Kconfig, which doesn't build on something other than linux.

Comment 5

[John Ford [:jhford] CET/CEST Berlin Time]

I think we're turning off otoro