>From a quick check it looks the asm for ARM is present, it's just put
directly in the header
x86/mips (and their 64-bit variants) have AsmGetRegs*.S
arm and aarch64 has it in the header file,
see:
https://android.googlesource.com/platform/system/core/+/refs/tags/android-10.0.0_r1/libunwindstack/in
Hello,
On Wed, Dec 23, 2020 at 10:12 PM Roger Shimizu wrote:
> On Wed, Dec 23, 2020 at 5:38 AM Hans-Christoph Steiner
> wrote:
> >
> > Thanks for jumping in Roger! I reviewed it with cdesai, and we thought
> > those libraries were not used on the "host" version, only when built as
> > part of
_1.5.2
New: v1.5.3, v1.5.5, etc.
Regards,
Chirayu Desai
fixed android-framework-23/6.0.1+r72-1
Hi,
I must apologize here, I mixed with src:android-platform-development
with src:android-platform-dalvik. Either way, the issue was still
multilib, and Kai-Chung Yan has fixed that and filed a RFS for this
package. Version r55 should fix it once that is uploaded.
Regards,
Chirayu Desai
On 08
Hi,
This should be fixed in newer versions, we did a multilib move around
6.0.1+r16-1 which had broke some packages.
A newer version, 6.0.1+r55 has been uploaded, is available in testing as
of today.
See https://tracker.debian.org/news/793698
On 08/28/2016 02:40 PM, Lucas Nussbaum wrote:
> Source
Hi,
I have uploaded the patch to upstream's code review system [1]
[1]: https://android-review.googlesource.com/260250
Hi Santiago,
Thanks for reporting the bug.
I've pushed a fix for it to the master branch, http://deb.li/rKfh
RAM was not an issue here.
The buildscripts divided the number of available processors by 2,
however that obviously wouldn't work for a single processor so I added a
check to not do that w
Package: android-sdk
Version: 24.3.3+2
Severity: grave
Justification: renders package unusable
Dear Maintainers,
I'm trying to build a sample app with the SDK by running 'gradle build'. App is
available at [1].
After putting in the files mentioned in Bug #827214, the next failure is:
Execution
Package: android-sdk
Version: 24.3.3+2
Severity: grave
Justification: renders package unusable
Dear Maintainers,
I'm trying to build a sample app with the SDK by running 'gradle build'. App is
available at [1].
This is due to the files 'source.properties' and 'build.prop' missing from
/usr/lib/
Hi,
This problem seems to have been fixed already in the source code.
The issue here is that fastboot doesn't search in the multi-arch path
(/usr/lib/x86_64-linux-gnu/android/) - you can verify that by
installing the 'patchelf' package, and then running 'patchelf
--print-rpath `which fastboot`', w
changes I want to make on top of this (shlib rpath
usage), and I guess we could also merge upstream (r43 is currently
present in the debian repos, r46 is the latest AOSP upstream)
On Fri, Jun 10, 2016 at 10:12 PM, Markus Koschany wrote:
> On 10.06.2016 16:55, Chirayu Desai wrote:
> [...]
>&
On Fri, Jun 10, 2016 at 7:26 PM, Markus Koschany wrote:
> On 10.06.2016 14:15, Chirayu Desai wrote:
> [...]
>> Hi,
>> I have just pushed my changes to apktool and frameworks/base.
>> frameworks/base has some other changes from seamlik (android.jar), so
>> I'
On Fri, Jun 10, 2016 at 4:08 PM, Markus Koschany wrote:
> On Wed, 8 Jun 2016 14:12:33 +0200 Hans-Christoph Steiner
> wrote:
>>
>> framework-res.apk is not included in the SDK, only the OS. Packaging
>> parts of the OS means we are making packages that upstream is not.
>> There are plenty of plac
14 matches
Mail list logo
