Build Failure with /bin/bash: line 1: meson: command not found

[Viralblack]

Followed both build guides for AOSP and the additional installation instructions, configured a new Ubuntu 24 explicitly for this purpose.

Following that trail it appeared meson is incorrectly configured, attempted a few different ways to correctly configure it but all seemed to point in the same direction. When running the installs for the environment given, this warning appears.

Attempted a few routes to resolve, didnt seemingly change anything. Potentially more environment/user error, just unsure what direction to go in.

[Viralblack]

The error in installation also takes place if using Debian 12 as base, it appears on the second line of step 2 with the python modules.

[Viralblack]

From the second line of the installation of pip3 elements, I used pipx to install them and jinja, pyyaml, and dataclasses post the same error of it being an externally managed environment. Will still continue to see if pipx remediates the compile error

[Viralblack]

Wider and more prolific failures across the board with Debian as opposed to Ubuntu

[Viralblack]

Made forward progress, rebuilt the environment (after double checking Ubuntu is the recommended build environment for AOSP and triple checking their requirements) and worked to remediate the MESON dependency first. I followed a few of the recommended solutions, pipx did not work for me, but venv did appear to allow for the implementation of MESON, so I pip installed all the sources from the earlier step in the virtual environment for pip and continued the build. It ran, but then said MESON was disallowed.

The error cited the path tools section as why MESON cant be used, per its statements.

Will be attempting to see if I can set the workaround variable.

[Viralblack]

Steps I followed to circumvent externally managed warning outlined here https://stackoverflow.com/questions/75608323/how-do-i-solve-error-externally-managed-environment-every-time-i-use-pip-3

[Viralblack]

Adding the tool to the soong config allowed MESON to run, but its now complaining about MAKO, another second level build tool added by this build's requirements specifically.

[shouvik007]

hi, I have faced the same issue. I don't think it because of any meson build issue. This is because of some memory issue. just give the below commands before your make command. surely this will solve the issue. better to do make clean once (if your build is corrupted)

sudo swapoff -a
sudo dd if=/dev/zero of=/swapfile bs=1G count=32
sudo mkswap /swapfile
sudo swapon /swapfile
grep SwapTotal /proc/meminfo

[Viralblack]

hi, I have faced the same issue. I don't think it because of any meson build issue. This is because of some memory issue. just give the below commands before your make command. surely this will solve the issue. better to do make clean once (if your build is corrupted)

sudo swapoff -a sudo dd if=/dev/zero of=/swapfile bs=1G count=32 sudo mkswap /swapfile sudo swapon /swapfile grep SwapTotal /proc/meminfo

Gave it a shot this morning, with my setup that occupied 100% of the drive no matter how much I expanded the partition. I additionally tried setting the build environment to 64gb from 32gb and it didnt change, for better or worse.