From: Petr Vorel <petr.vorel@gmail.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 0/3] Build android fixes
Date: Sat, 2 Feb 2019 18:22:46 +0100 [thread overview]
Message-ID: <20190202172245.GA979@x230> (raw)
In-Reply-To: <56309f29-d63c-2975-eb2c-1294f55e37e8@google.com>
Hi Steve,
> How did you come across these issues? We have yet to see them. Did you merge
> tip of LTP into an Android AOSP tree and build it that way?
Any sane person who wants to tests Android kernel uses LTP build inside of AOSP
to get all your custom (not yet upstreamed) fixes, skip non relevant test etc.
But I don't want to store whole AOSP on my disc, so I tried to cross compile
upstream LTP with android standalone toolchain (with make ANDROID=1).
Looking now, you're using lib/tst_safe_sysv_ipc.c in gen.bp and that was missing
in our Makefile.
I thought you might not build tests needing includes, but you do. Do you pass
some flag to compiler?
Compiler used:
$ ~/usr/android-standalone-toolchain.api-27/bin/arm-linux-androideabi-gcc --version
Android (5058415 based on r339409) clang version 8.0.2 (https://android.googlesource.com/toolchain/clang 40173bab62ec746213857d083c0e8b0abb568790) (https://android.googlesource.com/toolchain/llvm 7a6618d69e7e8111e1d49dc9e7813767c5ca756a) (based on LLVM 8.0.2svn)
Target: armv7a-unknown-linux-android27
Thread model: posix
InstalledDir: ~/usr/android-standalone-toolchain.api-27/bin
Kind regards,
Petr
next prev parent reply other threads:[~2019-02-02 17:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 11:28 [LTP] [PATCH 0/3] Build android fixes Petr Vorel
2019-01-30 11:28 ` [LTP] [PATCH 1/3] lib: Add missing <string.h> and <strings.h> includes Petr Vorel
2019-01-30 11:28 ` [LTP] [PATCH 2/3] lib/tst_kernel.c: Use <sys/personality.h> Petr Vorel
2019-01-30 11:28 ` [LTP] [PATCH 3/3] lib: Build tst_path_has_mnt_flags.c also on Android Petr Vorel
2019-01-30 19:01 ` [LTP] [PATCH 0/3] Build android fixes Jan Stancek
2019-02-02 17:22 ` Petr Vorel
2019-01-30 23:02 ` Steve Muckle
2019-02-02 17:22 ` Petr Vorel [this message]
2019-02-04 19:20 ` Sandeep Patil
2019-02-05 0:06 ` Steve Muckle
2019-02-05 1:22 ` Petr Vorel
2019-02-05 23:40 ` Steve Muckle
2019-02-05 0:00 ` Steve Muckle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190202172245.GA979@x230 \
--to=petr.vorel@gmail.com \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox