Re: How to ignore the “Scanning binaries for linking errors“ for cross platform toolchains

[Joshua Root]

On 2016-11-30 00:03 , Martin Krischik wrote:
> Hello Joshue,
>
> Joshua Root schrieb:
>> On 2016-11-24 05:28 , Martin Krischik wrote:
>>> Hello
>>>
>>> Just wanted to bring the android port up to date when noticed the the
>>> “Scanning binaries for linking errors” has been upgraded from warning to
>>> error.
>>>
>>> That is a bit of a problem as the android port is toolchain for cross
>>> platform development and as such contains several libraries for other
>>> platforms.
>>>
>>> Those libraries will, of course, always fail the link test. Any ideas
>>> what can be done?
>>
>> For rev-upgrade to try to do anything about these libraries they would
>> have to be (a) Mach-O and (b) an architecture that the host machine can
>> run. Is that really the case for the Android SDK?
>
> I finally managed to get useful error message. Had to set
> «revupgrade_mode report». And the three files reported are from the
> emulator:
>
> DEBUG: Marking
> /opt/local/share/java/android-sdk-macosx/tools/qemu/darwin-x86_64/qemu-system-mips64el
> as broken
> DEBUG: Marking
> /opt/local/share/java/android-sdk-macosx/tools/qemu/darwin-x86_64/qemu-system-x86_64
> as broken
> --->  Found 3 broken file(s), matching files to ports
> --->  Found 1 broken port(s):
>      android @24.4.1
>
> /opt/local/share/java/android-sdk-macosx/tools/qemu/darwin-x86_64/qemu-system-aarch64
>
> /opt/local/share/java/android-sdk-macosx/tools/qemu/darwin-x86_64/qemu-system-mips64el
>
> /opt/local/share/java/android-sdk-macosx/tools/qemu/darwin-x86_64/qemu-system-x86_64
>
>>From the “x86_64” inside the directory name one might think them to be
> of the correct architecture while the mips64el from the filename does
> not sound as promising.

OK, so they're shipping a copy of qemu. I assume it would be for running 
on the host to test your android programs; mips64el etc. would be the 
arch being emulated.

How are these binaries linked? Can you run them?

- Josh