• State Accepted Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 3 replies
  • Subscribers 26 subscribers
  • Views 5485 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 in reply to Ruben

    Hi Ruben,

    Thank you for coming back to me. That's very helpful.

    On your raised points:

    • Total available RAM is 3.8GB
    • Size of disk is 457GB of which available 292GB (with space already taken up by previous repo installation/downloading steps)

     I have attached a relevant snapshot from the system journal for if it helps you to deduce any further info on the failure:

      

    It's good to know you/Arm have an optimisation in the works for resource constraint machines. Would this come under Linaro's gitlab when it's made available?

    Would I stand a better chance if I had a go at the build script on a machine with 8GB RAM available? Or it's subject to the overall configuration?    

    Kind regards,

    George

Reply
  • 0 in reply to Ruben

    Hi Ruben,

    Thank you for coming back to me. That's very helpful.

    On your raised points:

    • Total available RAM is 3.8GB
    • Size of disk is 457GB of which available 292GB (with space already taken up by previous repo installation/downloading steps)

     I have attached a relevant snapshot from the system journal for if it helps you to deduce any further info on the failure:

      

    It's good to know you/Arm have an optimisation in the works for resource constraint machines. Would this come under Linaro's gitlab when it's made available?

    Would I stand a better chance if I had a go at the build script on a machine with 8GB RAM available? Or it's subject to the overall configuration?    

    Kind regards,

    George

Children
  • +1 Arm Employee Badge in reply to GeoDSbD

    Hi George,

    The system journal output confirms that the build failure is caused by the "OOM killer".

    While the 292GB of disk space should certainly be sufficient for the build, 3.8GB of RAM wouldn't be enough unfortunately.

    > Would I stand a better chance if I had a go at the build script on a machine with 8GB RAM available?

    The official minimum requirement at the moment is 16GB RAM.
    It certainly depends on the overall configuration and it might work with 8GB RAM, however it would be difficult to guarantee that in general case.

    Kind regards,
    Ruben