Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Errors #2

Open
lucasponez opened this issue Jun 15, 2019 · 0 comments
Open

Errors #2

lucasponez opened this issue Jun 15, 2019 · 0 comments

Comments

@lucasponez
Copy link

platform_testing/libraries/flicker/Android.mk: error: flickerlib (JAVA_LIBRARIES android-arm64) missing layerspro
tosnano (JAVA_LIBRARIES android-arm64)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real p
roblems until later in the build.
platform_testing/libraries/flicker/test/Android.mk: error: FlickerLibTest (APPS android-arm64) missing layersprot
osnano (JAVA_LIBRARIES android-arm64)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real p
roblems until later in the build.
build/make/core/main.mk:850: error: exiting from previous errors.
19:45:04 ckati failed with: exit status 1
make: *** [build/make/core/main.mk:21: run_soong_ui] Error 1
real 1m12.850s
user 1m58.304s
sys 0m22.330s
DennySPB pushed a commit that referenced this issue Oct 18, 2021
@Rashed97 @DennySPB
build: Automatically replace old-style kernel header includes with ne…
a49b52f 
…w header lib

This is a combination of 3 commits.
This is the 1st commit message:

build: add kernel header dependency if module uses kernel headers

Many of the QCOM components use kernel headers, but don't declare
the dependency on them.  This is fine in CAF because of the way they
build the boot.img before anything else.  In CM, we don't build the
boot.img the same, so we run into a race between the kernel build &
these modules... and the modules lose.

Warn about modules that have this missing dependency, and add it for
them so we don't have to modify each Android.mk.

Change-Id: I95f1e47b5ef440f6f5d8f64a0c3f38d9572e839e

============================================================================
This is the commit message #2:

build: Switch kernel header inclusion

The build is switching to the target INSTALLED_KERNEL_HEADERS to
declare dependencies on kernel headers.

Change-Id: I913e74681b02dfcf1eaed3d1e47ff4ab2300b12d

============================================================================
This is the commit message #3:

build: Automatically replace old-style kernel header includes with new header lib

Since we do this via soong and the result is a header library, just replace all
legacy include paths that point to the old header location with calls to the new
header library. Since we no longer have the legacy include, we can also remove
the additional dependency.

This reverts commit fa79821.

Change-Id: I716955534e50831e6568ca01e480aa8b90075d92
Signed-off-by: DennySPb <[email protected]>
DennySPB pushed a commit that referenced this issue Sep 27, 2022
@Rashed97 @DennySPB
build: Automatically replace old-style kernel header includes with ne…
0a602dc 
…w header lib

This is a combination of 3 commits.
This is the 1st commit message:

build: add kernel header dependency if module uses kernel headers

Many of the QCOM components use kernel headers, but don't declare
the dependency on them.  This is fine in CAF because of the way they
build the boot.img before anything else.  In CM, we don't build the
boot.img the same, so we run into a race between the kernel build &
these modules... and the modules lose.

Warn about modules that have this missing dependency, and add it for
them so we don't have to modify each Android.mk.

Change-Id: I95f1e47b5ef440f6f5d8f64a0c3f38d9572e839e

============================================================================
This is the commit message #2:

build: Switch kernel header inclusion

The build is switching to the target INSTALLED_KERNEL_HEADERS to
declare dependencies on kernel headers.

Change-Id: I913e74681b02dfcf1eaed3d1e47ff4ab2300b12d

============================================================================
This is the commit message #3:

build: Automatically replace old-style kernel header includes with new header lib

Since we do this via soong and the result is a header library, just replace all
legacy include paths that point to the old header location with calls to the new
header library. Since we no longer have the legacy include, we can also remove
the additional dependency.

This reverts commit fa79821.

Change-Id: I716955534e50831e6568ca01e480aa8b90075d92
Signed-off-by: DennySPb <[email protected]>
DennySPB pushed a commit that referenced this issue Sep 27, 2022
@rmcc @DennySPB
Add BOARD_CUSTOM_BOOTIMG_MK support
0c0e4fe 
This is a combination of 2 commits.
This is the 1st commit message:

    Add BOARD_CUSTOM_BOOTIMG_MK support

    Simplified version of the previous implementation. Recovery's ramdisk
    is spun off from the main recovery target again to allow overriding
    just the image-generation step

    [mikeioannina]: Squash cm-13.0 changes and adapt to N

    Change-Id: I058d214f0cf2d05b7621b369ef1f8a983c3ac258

This is the commit message #2:

    build: Handle custom boot images properly

    When a pre-built image should be used, it should be stored in the
    target files zip so that it can be used with external signing
    processes.

    Original-Change-Id: I2661af9ac58af30bb9314b552775046d3abf44e0
    Change-Id: I10b3bd0bb33489b8ffb26d16d002f8dd6ff405ad

[aleasto]
  Rewritten for R, where the recovery ramdisk is created via
  make dependencies, rather than $(call)s

[mainey]
  Adapt to new flag INTERNAL_RECOVERY_RAMDISK_FILES_TIMESTAMP

Change-Id: I058d214f0cf2d05b7621b369ef1f8a983c3ac258
Signed-off-by: Joey Huab <[email protected]>
Signed-off-by: DennySPb <[email protected]>
DennySPB pushed a commit that referenced this issue Nov 9, 2022
@android-build-merge-worker-robot
platform/build/make - T is now 33 #2 am: a84dc6c
b2795d9 
Original change: https://googleplex-android-review.googlesource.com/c/platform/build/+/18083390

Change-Id: I53847261967eb9d7f69a269efd972b86d65ec919
Signed-off-by: Automerger Merge Worker <[email protected]>
DennySPB pushed a commit that referenced this issue Dec 19, 2022
@android-build-merge-worker-robot
platform/build/make - T is now 33 #2 am: a84dc6c am: b2795d9
ff791c1 
Original change: https://googleplex-android-review.googlesource.com/c/platform/build/+/18083390

Change-Id: I3ce1fd2760e346c2d7d0641526daeb41a1f320fc
Signed-off-by: Automerger Merge Worker <[email protected]>
DennySPB pushed a commit that referenced this issue Nov 30, 2023
@Rashed97 @DennySPB
build: Automatically replace old-style kernel header includes with ne…
254b1b0 
…w header lib

This is a combination of 3 commits.
This is the 1st commit message:

build: add kernel header dependency if module uses kernel headers

Many of the QCOM components use kernel headers, but don't declare
the dependency on them.  This is fine in CAF because of the way they
build the boot.img before anything else.  In CM, we don't build the
boot.img the same, so we run into a race between the kernel build &
these modules... and the modules lose.

Warn about modules that have this missing dependency, and add it for
them so we don't have to modify each Android.mk.

Change-Id: I95f1e47b5ef440f6f5d8f64a0c3f38d9572e839e

============================================================================
This is the commit message #2:

build: Switch kernel header inclusion

The build is switching to the target INSTALLED_KERNEL_HEADERS to
declare dependencies on kernel headers.

Change-Id: I913e74681b02dfcf1eaed3d1e47ff4ab2300b12d

============================================================================
This is the commit message #3:

build: Automatically replace old-style kernel header includes with new header lib

Since we do this via soong and the result is a header library, just replace all
legacy include paths that point to the old header location with calls to the new
header library. Since we no longer have the legacy include, we can also remove
the additional dependency.

This reverts commit fa79821.

Change-Id: I716955534e50831e6568ca01e480aa8b90075d92
Signed-off-by: DennySPb <[email protected]>
DennySPB pushed a commit that referenced this issue Nov 30, 2023
@rmcc @DennySPB
Add BOARD_CUSTOM_BOOTIMG_MK support
7398e40 
This is a combination of 2 commits.
This is the 1st commit message:

    Add BOARD_CUSTOM_BOOTIMG_MK support

    Simplified version of the previous implementation. Recovery's ramdisk
    is spun off from the main recovery target again to allow overriding
    just the image-generation step

    [mikeioannina]: Squash cm-13.0 changes and adapt to N

    Change-Id: I058d214f0cf2d05b7621b369ef1f8a983c3ac258

This is the commit message #2:

    build: Handle custom boot images properly

    When a pre-built image should be used, it should be stored in the
    target files zip so that it can be used with external signing
    processes.

    Original-Change-Id: I2661af9ac58af30bb9314b552775046d3abf44e0
    Change-Id: I10b3bd0bb33489b8ffb26d16d002f8dd6ff405ad

[aleasto]
  Rewritten for R, where the recovery ramdisk is created via
  make dependencies, rather than $(call)s

[mainey]
  Adapt to new flag INTERNAL_RECOVERY_RAMDISK_FILES_TIMESTAMP

Change-Id: I058d214f0cf2d05b7621b369ef1f8a983c3ac258
Signed-off-by: Joey Huab <[email protected]>
Signed-off-by: DennySPb <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lucasponez