[android-building] Re: Build error for pixel 3 XL kernel
Which repo did you sync, when you built? This reminds me of https://partner-android-review.googlesource.com/1089911 On Thursday, January 17, 2019 at 6:36:19 PM UTC-6, shjeep...@gmail.com wrote: > > Hi, > I'm try to build pixel3 xl kernel w/ this command > $sh build/build.sh > But facing below error, any idea on how to fix it? > > VDSOSYM include/generated/vdso-offsets.h > VDSOC32 arch/arm64/kernel/vdso32/vgettimeofday.o > LDS arch/arm64/kernel/vdso32/vdso.lds > VDSOA32 arch/arm64/kernel/vdso32/sigreturn.o > HOSTCC arch/arm64/kernel/vdso32/../../../arm/vdso/vdsomunge > > */..//bin/as: unrecognized option '-mfloat-abi=soft'clang-5.0: error: > assembler command failed with exit code 1 (use -v to see invocation)* > make[3]: *** > [/home/jiangenj/workspace/pixel3/kernel/private/msm-google/arch/arm64/kernel/vdso32/Makefile:144: > > arch/arm64/kernel/vdso32/sigreturn.o] Error 1 > make[3]: *** Waiting for unfinished jobs > /..//bin/as: unrecognized option '-mfloat-abi=soft' > clang-5.0: error: assembler command failed with exit code 1 (use -v to see > invocation) > make[3]: *** > [/home/jiangenj/workspace/pixel3/kernel/private/msm-google/arch/arm64/kernel/vdso32/Makefile:142: > > arch/arm64/kernel/vdso32/vgettimeofday.o] Error 1 > make[2]: *** [arch/arm64/Makefile:242: vdso_prepare] Error 2 > make[1]: *** [Makefile:152: sub-make] Error 2 > make: *** [Makefile:24: __sub-make] Error 2 > > Thanks > -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-building] Re: How to include prebuilt jars using bp in Android P
I'd suggest combining the two:
java_import {
name: "myPrebuiltJar-prebuilt",
jars: ["myPrebuiltJar.jar"],
}
java_library {
name: "myPrebuiltJar",
static_libs: ["myPrebuiltJar-prebuilt"],
installable: true,
}
On Fri, Jan 18, 2019 at 9:02 AM Ronny Pau wrote:
> I have the same problem too.
>
> I have a prebuilt jar that needs to be brought in, I have tried both
> java_import and java_library directives and neither works. Ideas?
>
> >>> java_import - seems to only create immediates but doesn't actually
> bring the the jar to my target directory
> java_import {
> name: "myPrebuiltJar",
> jars: ["myPrebuiltJar.jar"],
> }
>
> >>> java_library - I see some immediates and the jar in my target
> directory, but callers that makes use of the library do not recognize /
> cannot import my package (build time error)
> java_library {
> name: "myPrebuiltJar",
> srcs: ["myPrebuiltJar.jar"],
> installable: true,
> }
>
> On Wednesday, 5 December 2018 12:26:29 UTC-5, Zoran Jovanovic wrote:
>>
>> Ah, sorry for misunderstanding.
>>
>>
>> Put "installable: true" somewhere under "java_library" in your library's
>> blueprint.
>>
>>
>> Cheers
>>
>> --
>>
>> Zoran Jovanovic
>> SW Architect
>> Sony Mobile Communications Inc.
>> Lund, Sweden
>>
>>
>>
>> From: android-...@googlegroups.com on
>> behalf of Ajay kumar
>> Sent: Wednesday, November 28, 2018 08:51
>> To: Android Building
>> Subject: [android-building] Re: How to include prebuilt jars using bp in
>> Android P
>>
>> Hi Zoran,
>> Thanks for your reply.
>> Our intention is to include this jar in system/frameworks as like
>> frameworks.jar(which has been built on an engineering environment), it has
>> to be used by a system service in frameworks. can you tell me how this can
>> be achievable ??
>>
>> Thanks,
>> Ajay
>>
>> On Tuesday, November 20, 2018 at 9:02:21 PM UTC+5:30, Ajay kumar wrote:
>> Hi
>> Added jar file :
>>
>> this my Android.bp
>>
>> java_import {
>> name: "my-services",
>> jars: ["my-services.jar"],
>> }
>>
>>
>> am getting build error :
>> ninja: error:
>> 'out/target/common/obj/JAVA_LIBRARIES/my-services_intermediates/javalib.jar',
>> needed by
>> 'out/target/product/mydevice/dex_bootjars/system/framework/arm64/boot.art',
>> missing and no known rule to make it
>>
>> I've added my-services in base.mk
Re: [android-building] AOSP build system in general
You can get ninja to print the commands it would run with -t commands. You
can do that in the Android build with:
NINJA_ARGS="-t commands droid" m
droid is the default goal, you can replace it with any other goal you want,
including a module name ("framework"), an installed file ("$(getbuildvar
PRODUCT_OUT)/system/framework/framework.jar"), or an intermediate
("out/soong/.intermediates/frameworks/base/framework/android_common/combined/framework.jar").
On Fri, Jan 18, 2019 at 9:02 AM Robert Durkacz
wrote:
> I thank JBQ for addressing my question. It is phrased as an objection to
> my proposal but I find that it is really in support because it allows me to
> point out that what I am asking for is perfectly normal and possible.
>
> JBQ wrote:
> "There are three main parts to a build system: figuring out what the
> possible commands are, figuring out which of those commands need to run and
> in which order, and actually running them.
>
> "While a shell script would conceivably be able to express the first one,
> it would struggle with some of the the second part (especially around
> incremental builds), and a readable implementation of the third part would
> likely be sequential, resulting in impractically long build times."
>
> I think there are two main parts because the first part is specified by
> the programmer, the one who sets up the build. In 'make' that is called
> the recipes.
> For the programmer who is using that build system, it can be beneficial to
> run the next two parts separately because this gives visibility and
> accessibility when things go wrong or to do something a little different to
> what the original programmer might have thought of (including transferring
> to a different build system).
> make can do the second part separately with the -n option. It produces a
> script, which can be executed, thereby doing the third part separately and
> allowing any amount of intervention between parts two and three.
>
> It is quite true that the script is just a sequence of commands and does
> not reflect make's option (-j) to execute commands in parallel processes. I
> would class it is an interesting question whether you could retain
> parallelism somehow while going through a script as an intermediate step. I
> would not think of it as such an obstacle to give up the script option
> entirely.
>
> If a script is too much to expect then at least a transcript of the
> commands that the build system executes would be almost as good if these
> could be captured and turned into a script.
>
> Android not so long ago would have used make. Whatever benefits were
> gained by going to a new and seemingly complex system, did they really
> require throwing away these beneficial features of make that give a
> programmer a way to take control of the build process?
>
>
>>
>>> --
>> --
>>
>> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
--
--
You received this message because you are subscribed to the "Android Building"
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en
---
You received this message because you are subscribed to the Google Groups
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to android-building+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [android-building] Re: How to include prebuilt jars using bp in Android P
I have the same problem too.
I have a prebuilt jar that needs to be brought in, I have tried both
java_import and java_library directives and neither works. Ideas?
>>> java_import - seems to only create immediates but doesn't actually
bring the the jar to my target directory
java_import {
name: "myPrebuiltJar",
jars: ["myPrebuiltJar.jar"],
}
>>> java_library - I see some immediates and the jar in my target
directory, but callers that makes use of the library do not recognize /
cannot import my package (build time error)
java_library {
name: "myPrebuiltJar",
srcs: ["myPrebuiltJar.jar"],
installable: true,
}
On Wednesday, 5 December 2018 12:26:29 UTC-5, Zoran Jovanovic wrote:
>
> Ah, sorry for misunderstanding.
>
>
> Put "installable: true" somewhere under "java_library" in your library's
> blueprint.
>
>
> Cheers
>
> --
>
> Zoran Jovanovic
> SW Architect
> Sony Mobile Communications Inc.
> Lund, Sweden
>
>
>
> From: android-...@googlegroups.com <
> android-...@googlegroups.com > on behalf of Ajay kumar <
> ajayre...@gmail.com >
> Sent: Wednesday, November 28, 2018 08:51
> To: Android Building
> Subject: [android-building] Re: How to include prebuilt jars using bp in
> Android P
>
> Hi Zoran,
> Thanks for your reply.
> Our intention is to include this jar in system/frameworks as like
> frameworks.jar(which has been built on an engineering environment), it has
> to be used by a system service in frameworks. can you tell me how this can
> be achievable ??
>
> Thanks,
> Ajay
>
> On Tuesday, November 20, 2018 at 9:02:21 PM UTC+5:30, Ajay kumar wrote:
> Hi
> Added jar file :
>
> this my Android.bp
>
> java_import {
> name: "my-services",
> jars: ["my-services.jar"],
> }
>
>
> am getting build error :
> ninja: error:
> 'out/target/common/obj/JAVA_LIBRARIES/my-services_intermediates/javalib.jar',
> needed by
> 'out/target/product/mydevice/dex_bootjars/system/framework/arm64/boot.art',
> missing and no known rule to make it
>
> I've added my-services in base.mk
