• State Accepted Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 3 replies
  • Subscribers 26 subscribers
  • Views 5317 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Build script failed: nano Android stack

GeoDSbD

Dear Morello Technical Forum,

I followed the walkthrough video from Linaro (https://www.morello-project.org/resources/morello-platform-model-and-android-stack-walkthrough/) to install and bring up the nano Android stack on the Morello FVP.

Everything went as expected until I reached the Android stack build step where I received a FAILED message, as per the below snapshot:

"soong bootstrap failed with: exist status 1

ninja: build stopped: subcommand failed." 

My host machine is a 2006 MacBook running Ubuntu 20.04.2 LTS. 

Any help you could provide will be gratefully received.

Many thanks,

George

(Digital Security by Design Programme)

Parents
  • 0

    Hi George,

    The build process appears to be unexpectedly interrupted ("killed") by the operating system.

    This most commonly happens when there is not enough free memory available for the system to operate correctly. The operating system mechanism responsible for that is called "OOM killer" ("out-of-memory killer")


    Could you please clarify the amount of RAM available in the system and amount of free disk space on the partition where the build is started?

    It should be possible to figure out these details with the help of the following command lines on an Ubuntu system:

    # amount of RAM available
free -h

# amount of free disk space (when run from within the source tree directory)
df -h .

     

    When "OOM killer" interrupts a process, it would normally report relevant details at the system journal, which is available via:

    journalctl -r

    This information might be helpful to understand the failure.

    There is a prototype of optimisation for building the nanodroid stack. The optimisation isn't published yet, however once it is published - it might potentially help with this via reducing the required amount of RAM and of free disk space.



    Best regards,
    Ruben

Reply
  • 0

    Hi George,

    The build process appears to be unexpectedly interrupted ("killed") by the operating system.

    This most commonly happens when there is not enough free memory available for the system to operate correctly. The operating system mechanism responsible for that is called "OOM killer" ("out-of-memory killer")


    Could you please clarify the amount of RAM available in the system and amount of free disk space on the partition where the build is started?

    It should be possible to figure out these details with the help of the following command lines on an Ubuntu system:

    # amount of RAM available
free -h

# amount of free disk space (when run from within the source tree directory)
df -h .

     

    When "OOM killer" interrupts a process, it would normally report relevant details at the system journal, which is available via:

    journalctl -r

    This information might be helpful to understand the failure.

    There is a prototype of optimisation for building the nanodroid stack. The optimisation isn't published yet, however once it is published - it might potentially help with this via reducing the required amount of RAM and of free disk space.



    Best regards,
    Ruben

Children