All of lore.kernel.org
 help / color / mirror / Atom feed
From: "AshishKumar Mishra" <ashishkumar.mishra@bmwtechworks.in>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH v3 0/3] android-tools: migration and cleanup
Date: Fri, 15 May 2026 03:23:46 -0700	[thread overview]
Message-ID: <1575450.1778840626136865406@lists.openembedded.org> (raw)
In-Reply-To: <1575450.1778745762950591364@lists.openembedded.org>

[-- Attachment #1: Type: text/plain, Size: 3699 bytes --]

Hi Khem / Team ,

Able to reproduce the build error with CLANG
Brought meta-clang and tweaked the toolchain / cc / cxx provider as clang
Will work to fix this and share the observation

Sharing the error log to get an feedback just to avoid any gap's in customization

Below is the error :
bake-builds/poky-master/build/tmp/work/cortexa57-oe-linux/android-tools/29.0.6.r14/android-tools=/usr/src/debug/android-tools/29.0.6.r14  -ffile-prefix-map=/home/bti-001003/upstream/bitbake-builds/poky-master/build/tmp/work/cortexa57-oe-linux/android-tools/29.0.6.r14/recipe-sysroot=  -ffile-prefix-map=/home/bti-001003/upstream/bitbake-builds/poky-master/build/tmp/work/cortexa57-oe-linux/android-tools/29.0.6.r14/recipe-sysroot-native=  -pipe -fvisibility-inlines-hidden -std=gnu++20 -UADB_HOST -DADB_HOST=0 -DALLOW_ADBD_DISABLE_VERITY -DALLOW_ADBD_NO_AUTH -DPLATFORM_TOOLS_VERSION='"28.0.2"'  -Isystem/core/diagnose_usb/include  -Isystem/core/adb/daemon/include -Isystem/core/adb/adbconnection/include -Isystem/core/libasyncio/include -Isystem/core/libcutils/include -Isystem/core/libcrypto_utils/include -Isystem/core/liblog/include/ -Isystem/core/libutils/include -Iframeworks/native/libs/adbd_auth/include -Wno-c++11-narrowing  -DPAGE_SIZE=4096 -fPIC -Isystem/coreinclude -Isystem/core/adb -Isystem/core/base/include  -Idebian/out/system/core -Isystem/tools/mkbootimg/include/bootimg -Isystem/core/fs_mgr/include -Isystem/core/fs_mgr/include_fstab -DADB_VERSION='""' -D_GNU_SOURCE -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,-z,relro,-z,now -Wl,-rpath='$ORIGIN/../lib/android' -Wl,-rpath-link='$ORIGIN/../lib/android' -lpthread -Ldebian/out/system/core -Ldebian/out/external/boringssl -lbase -lcrypto_utils -l:libcrypto.a -lcutils -llog -lresolv
| aarch64-oe-linux-clang++: warning: treating 'c-header' input as 'c++-header' when in C++ mode, this behavior is deprecated [-Wdeprecated]
| aarch64-oe-linux-clang++: warning: treating 'c-header' input as 'c++-header' when in C++ mode, this behavior is deprecated [-Wdeprecated]
| aarch64-oe-linux-clang++: warning: treating 'c-header' input as 'c++-header' when in C++ mode, this behavior is deprecated [-Wdeprecated]
| aarch64-oe-linux-clang++: warning: treating 'c-header' input as 'c++-header' when in C++ mode, this behavior is deprecated [-Wdeprecated]
| aarch64-oe-linux-clang++: error: cannot specify -o when generating multiple output files
| make: *** [/home/bti-001003/upstream/bitbake-builds/poky-master/build/tmp/work/cortexa57-oe-linux/android-tools/29.0.6.r14/sources/android-tools-29.0.6.r14/debian/system/core/adbd.mk:84: build] Error 1
| make: Leaving directory '/home/bti-001003/upstream/bitbake-builds/poky-master/build/tmp/work/cortexa57-oe-linux/android-tools/29.0.6.r14/sources/android-tools-29.0.6.r14'
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
ERROR: Task (/home/bti-001003/upstream/bitbake-builds/poky-master/layers/meta-openembedded/meta-oe/recipes-devtools/android-tools/android-tools_29.0.6.r14.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1685 tasks of which 275 didn't need to be rerun and 1 failed.
Summary: 1 task failed:
/home/bti-001003/upstream/bitbake-builds/poky-master/layers/meta-openembedded/meta-oe/recipes-devtools/android-tools/android-tools_29.0.6.r14.bb:do_compile
log: /home/bti-001003/upstream/bitbake-builds/poky-master/build/tmp/work/cortexa57-oe-linux/android-tools/29.0.6.r14/temp/log.do_compile.1623961
Summary: There were 12 WARNING messages.
Summary: There were 2 ERROR messages, returning a non-zero exit code.
~/upstream/bitbake-builds/poky-master/build :
~/upstream/bitbake-builds/poky-master/build :

[-- Attachment #2: Type: text/html, Size: 3945 bytes --]

  reply	other threads:[~2026-05-15 10:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05 15:06 [meta-oe][PATCH v3 0/3] android-tools: migration and cleanup AshishKumar Mishra
2026-05-05 15:06 ` [meta-oe][PATCH v3 1/3] android-tools: remove android-tools 5.x from meta-oe/recipes-devtools AshishKumar Mishra
2026-05-05 15:06 ` [meta-oe][PATCH v3 2/3] android-tools: move android-tools v29.x from dynamic-layers/selinux to meta-oe AshishKumar Mishra
2026-05-05 15:06 ` [meta-oe][PATCH v3 3/3] android-tools: removes selinux dependency from android-tools_29.0.6.r14.bb AshishKumar Mishra
2026-05-07  5:09 ` [meta-oe][PATCH v3 0/3] android-tools: migration and cleanup Ashish Mishra
2026-05-13  6:47   ` AshishKumar Mishra
2026-05-13  6:57     ` [oe] " Gyorgy Sarvari
2026-05-13  7:26       ` Khem Raj
2026-05-13  8:21         ` AshishKumar Mishra
2026-05-13 19:49           ` Khem Raj
2026-05-14  8:02             ` AshishKumar Mishra
2026-05-15 10:23               ` AshishKumar Mishra [this message]
2026-05-15 10:37                 ` [oe] " Gyorgy Sarvari
2026-05-15 13:13                   ` Khem Raj

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1575450.1778840626136865406@lists.openembedded.org \
    --to=ashishkumar.mishra@bmwtechworks.in \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.