Chromium build failure moving from v67.0.3396.107 to v68.0.3440.81

[d...@vittegleo.com]

I'm currently building the 'monochrome_public_apk' target for arm64 android and it has been working fine on v67 branches with the configuration below. After trying to move to v68 I'm hitting the following error:

Done. Made 22472 targets from 1498 files in 7453ms

ninja: Entering directory `out/Default/'

ninja: error: '../../third_party/libsync/src/sync.c', needed by 'obj/third_party/libsync/libsync/sync.o', missing and no known rule to make it

Does anyone have any ideas on what is causing this issue? Any help or pointers would be very appreciated.

These are the steps and configuration that I'm using:

# get chromium source
mkdir -p chromium && cd chromium
fetch --nohooks android --target_os_only=true

cd src

git checkout "68.0.3440.81" -f

git clean -dff

yes | gclient sync --with_branch_heads --jobs 32 -RDf

# install dependencies

echo ttf-mscorefonts-installer msttcorefonts/accepted-mscorefonts-eula select true | sudo debconf-set-selections

sudo ./build/install-build-deps-android.sh

build/linux/sysroot_scripts/install-sysroot.py --arch=i386

build/linux/sysroot_scripts/install-sysroot.py --arch=amd64

mkdir -p out/Default

cat <<EOF > out/Default/args.gn

target_os = "android"

target_cpu = "arm64"

is_debug = false

is_official_build = true

is_component_build = false

symbol_level = 0

ffmpeg_branding = "Chrome"

proprietary_codecs = true

android_channel = "stable"

android_default_version_name = "68.0.3440.81"

android_default_version_code = "344008152"

EOF

gn gen out/Default

ninja -C out/Default/ monochrome_public_apk

[Torne (Richard Coles)]

target_os_only=true isn't supported for android. The android build assumes all the Linux deps are also present.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/9c670782-923d-4abc-bd92-2e36be0a89b5%40chromium.org.

[d...@vittegleo.com]

Thanks so much Richard! This solved my problem.