Re: [android-building] Lots of 'Disallowed PATH tool "manpath"...' when building Android Q

2019-11-18 Thread Michael Goffioul
re/Modules/init/bash, which is causing >> arbitrary bash code that can use any binary to be run on every >> non-interactive bash shell startup. >> >> On Mon, Nov 18, 2019 at 9:50 AM Michael Goffioul < >> michael.goffi...@gmail.com> wrote: >> >>> Y

Re: [android-building] Lots of 'Disallowed PATH tool "manpath"...' when building Android Q

2019-11-18 Thread Michael Goffioul
low through is always > trying to call manpath? Let me know what you find, we've definitely been > shrinking this list on master. > > - Dan > > On Thu, Nov 14, 2019 at 3:54 PM Michael Goffioul < > michael.goffi...@gmail.com> wrote: > >> I'm using Fedora 30 to build

[android-building] Unable to download content during build

2019-10-16 Thread Michael Goffioul
I have several custom modules that download content (if not already present) during build, with wget. This uses additional rules in the corresponding Android.mk files. These used to work in Pie, but in Q the rule fail with "Name or service not found". Running the exact same command outside the

Re: [android-building] Unable to download content during build

2019-10-16 Thread Michael Goffioul
s used. Probably wget or external connections are blocked. > > BR, K > > Get Outlook for Android <https://aka.ms/ghei36> > > -- > *From:* android-building@googlegroups.com < > android-building@googlegroups.com> on behalf of Michael Goffio

[android-building] Missing dep libraries in generated apex

2019-10-03 Thread Michael Goffioul
Hi, I'm trying to build Android Q (for android-x86, 32-bits) and I'm having a problem in the generated apex for com.android.media.swcodec, where there are a bunch of libraries missing in $TARGET_OUT/system/apex/com.android.media.swcodec/lib/. The directory does contain various deps like

[android-building] Re: Missing dep libraries in generated apex

2019-10-04 Thread Michael Goffioul
On Thursday, October 3, 2019 at 3:53:13 PM UTC-4, Michael Goffioul wrote: > > Hi, > > I'm trying to build Android Q (for android-x86, 32-bits) and I'm having a > problem in the generated apex for com.android.media.swcodec, where there > are a bunch of libraries missing in > $T

[android-building] Re: Dex2oat failed to compile a boot image

2020-03-30 Thread Michael Goffioul
android.system.OsConstants.initConstants() in an unstarted non-transactional runtime On Mon, Mar 30, 2020 at 6:59 PM Michael Goffioul wrote: > On Mon, Mar 30, 2020 at 6:52 PM Michael Goffioul < > michael.goffi...@gmail.com> wrote: > >> I'm still experimenting with android-r-prev

Re: [android-building] Re: Dex2oat failed to compile a boot image

2020-03-31 Thread Michael Goffioul
ld and new projects. > > - Dan > > On Mon, Mar 30, 2020 at 10:10 PM Guoyin Chen > wrote: > >> There are quite a lot of build error with android-preview-2 build. I >> think google have several wrong tag on different gits. >> >> On Tuesday, March 31, 2020 at 8:41

[android-building] Disallowed PATH tool "m4", but used by flex

2020-03-30 Thread Michael Goffioul
I'm experimenting with android-r-preview-2 and found a problem compiling mesa, which didn't occur with android-10. The error occurs when running flex: 23:56:24 Disallowed PATH tool "m4" used: []string{"m4", "-P"} 23:56:24 See

Re: [android-building] Cannot build android-platform-12.1.0_r4

2022-06-15 Thread Michael Goffioul
referenced in the r4 manifest[2]. > > > > [1] > https://android.googlesource.com/platform/packages/apps/Car/libs/+/refs/tags/android-12.1.0_r4/androidx-car/Android.bp > > [2] > https://android.googlesource.com/platform/manifest/+/refs/heads/android-12.1.0_r4/default.xml#832 &g

[android-building] Cannot build android-platform-12.1.0_r4

2022-06-14 Thread Michael Goffioul
Soong fails with the following error: error: frameworks/opt/car/setupwizard/library/main/Android.bp:20:1: "car-setup-wizard-lib" depends on undefined module "androidx.car_car-resources-partially-dejetified" >From what I can see, the code in packages/apps/Car/libs/androidx-car/ has been moved to

[android-building] Re: dex2oatd fails due to unexpected mmap address

2022-07-28 Thread Michael Goffioul
I forgot to mention the Android version is 7.1.2. On Tue, Jul 26, 2022 at 2:34 PM Michael Goffioul wrote: > Hi, > > I've been compiling an arm64 firmware (for AMLogic chipset) on the same > Fedora-based system for a couple of years now. Today, after rebuilding from > s

[android-building] dex2oatd fails due to unexpected mmap address

2022-07-28 Thread Michael Goffioul
Hi, I've been compiling an arm64 firmware (for AMLogic chipset) on the same Fedora-based system for a couple of years now. Today, after rebuilding from scratch, I faced the following error. Would anybody have any insight on what is going on? [100% 2/2] build

[android-building] Re: dex2oatd fails due to unexpected mmap address

2022-07-28 Thread Michael Goffioul
Goffioul wrote: > I forgot to mention the Android version is 7.1.2. > > On Tue, Jul 26, 2022 at 2:34 PM Michael Goffioul < > michael.goffi...@gmail.com> wrote: > >> Hi, >> >> I've been compiling an arm64 firmware (for AMLogic chipset) on the same >> Fedora-

Re: [android-building] Re: dex2oatd fails due to unexpected mmap address

2022-08-24 Thread Michael Goffioul
On Sun, Aug 14, 2022 at 8:30 AM Michael Goffioul wrote: > > > On Thu, Jul 28, 2022 at 8:58 PM 'Dan Willemsen' via Android Building < > android-building@googlegroups.com> wrote: > >> Have you tried to reproduce with a newer version of Android? Android 7 is >>

Re: [android-building] Re: dex2oatd fails due to unexpected mmap address

2022-08-24 Thread Michael Goffioul
On Thu, Jul 28, 2022 at 8:58 PM 'Dan Willemsen' via Android Building < android-building@googlegroups.com> wrote: > Have you tried to reproduce with a newer version of Android? Android 7 is > about 6 years old, so I wouldn't be expecting any changes to it. > > You may want to talk to your

[android-building] Cannot build Android 13 with audio.a2dp.default module

2022-09-13 Thread Michael Goffioul
I'm using a source tree derived from manifest android-13.0.0_r4. The build also adds audio.a2dp.default to PRODUCT_PACKAGES. The ckati step then fails with the following error: build/make/core/tasks/platform_availability_check.mk:37: warning: Following modules are requested to be installed. But

Re: [android-building] Re: Android 13 Released - main.mk:2011:error:missing separator

2022-09-14 Thread Michael Goffioul
It turned out the problem was caused by the presence of a file in PRODUCT_COPY_FILES that contains a comma in its filename. This interferes with the macro expansion of make. We'll have to test the proposed commit, but from a first inspection, I think the problem will still be present, as the

Re: [android-building] Cannot build Android 13 with audio.a2dp.default module

2022-09-14 Thread Michael Goffioul
the mainline > module instead. > > - Dan > > On Tue, Sep 13, 2022 at 6:11 PM Michael Goffioul < > michael.goffi...@gmail.com> wrote: > >> I'm using a source tree derived from manifest android-13.0.0_r4. The >> build also adds audio.a2dp.default to PRODUCT_PACKAG

[android-building] Re: External camera service for 64 bits

2023-01-10 Thread Michael Goffioul
orks fine on 32 bits, falls flat on 64 bits. Not sure if anybody at Google is reading this, but you might wanna have a look at that more closely. Michael. On Thu, Sep 29, 2022 at 3:09 PM Michael Goffioul wrote: > Is there a particular reason to keep the external camera service a 32-bit &

Re: [android-building] Re: External camera service for 64 bits

2023-01-12 Thread Michael Goffioul
On Wed, Jan 11, 2023 at 2:32 AM 'enh' via Android Building < android-building@googlegroups.com> wrote: > On Tue, Jan 10, 2023 at 5:17 PM Michael Goffioul < > michael.goffi...@gmail.com> wrote: > >> Well, it turns out I believe there's invalid code in the external ca

[android-building] Is AVX2 now a mandatory ABI requirement for x86 platforms?

2023-11-14 Thread Michael Goffioul
Since this commit, webrtc audio processing module is compiled with AVX2 enabled. https://cs.android.com/android/_/android/platform/external/webrtc/+/b5b78192e10ba90978fb8228e7eb9fcf75c83f0c This makes the module fail to load on platforms that do not support AVX2. E.g. generates SIGILL at a

Re: [android-building] Is AVX2 now a mandatory ABI requirement for x86 platforms?

2024-04-29 Thread Michael Goffioul
Hello? Anybody out there? On Tue, Dec 19, 2023 at 9:29 AM Michael Goffioul wrote: > Any update on this? I guess that now that the cat's out of the bag, it'll > be difficult to put it back in, and AVX2 is a de facto ABI requirement. > > > On Tue, Nov 14, 2023 at 1:13 PM 'e