public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] 回复:[PATCH v1] include/mk/env_post.mk: enable __ANDROID__ definition for Android build
Date: Mon, 22 Apr 2019 00:10:30 +0200	[thread overview]
Message-ID: <20190421221030.GA11307@x230> (raw)
In-Reply-To: <aafe58ce-e74d-b350-4e91-445683c120fc@xiaopeng.com>

Hi Sandeep, Zhengwang,

> > I don't know why autotools fails preadv and pwritev detection with AC_CHECK_FUNCS.
> > I considered it as problem of my setup, but maybe it's an autotools bug.

> I also encountered this issue, but I temporarily walked around it by
> applying the following patch.

> ==================

> $ git diff testcases/
> diff --git a/testcases/commands/ldd/datafiles/Makefile
> b/testcases/commands/ldd/datafiles/Makefile
> index d8bcf5c..74fbe50 100644
> --- a/testcases/commands/ldd/datafiles/Makefile
> +++ b/testcases/commands/ldd/datafiles/Makefile
> @@ -30,7 +30,7 @@ CLEAN_TARGETS         += *.obj $(LDD_SO_FILES)
>         $(CC) $(CFLAGS) -shared -o $@ $^

>  lddfile.out: main.o $(LDD_SO_FILES)
> -       $(CC) $(CFLAGS) -O -o $@ $?
> +       $(CC) $(CFLAGS) $(LDFLAGS) -O -o $@ $?
What is this change for?

>  INSTALL_DIR            := testcases/data/ldd01

> diff --git a/testcases/kernel/syscalls/Makefile
> b/testcases/kernel/syscalls/Makefile
> index 45a00cf..27c2e7a 100644
> --- a/testcases/kernel/syscalls/Makefile
> +++ b/testcases/kernel/syscalls/Makefile
> @@ -43,6 +43,8 @@ FILTER_OUT_DIRS       += \
>         sched_getaffinity sched_setaffinity sendmsg setgroups setns sighold
> \
>         sigrelse sigsuspend sigtimedwait sigwait sigwaitinfo stime \
>         setdomainname sethostname symlinkat ulimit ustat vfork vhangup
> vmsplice
> +
> +FILTER_OUT_DIRS += preadv pwritev
Yes, that fixes build. But manually disabling features in config.h enables these
tests to be build.

Kind regards,
Petr

  reply	other threads:[~2019-04-21 22:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09  4:05 [LTP] [PATCH v1] include/mk/env_post.mk: enable __ANDROID__ definition for Android build Zhengwang Ruan
2019-04-09 16:45 ` [LTP] 回复:[PATCH " =?unknown-8bit?b?6Ziu5q2j5pe6?=
2019-04-10 14:16   ` Petr Vorel
2019-04-11  3:38     ` =?unknown-8bit?b?6Ziu5q2j5pe6?=
2019-04-11 16:27     ` Sandeep Patil
2019-04-11 17:37       ` Petr Vorel
2019-04-11 23:40         ` Petr Vorel
2019-04-12  4:45           ` =?unknown-8bit?b?6Ziu5q2j5pe6?=
2019-04-12  6:28             ` Petr Vorel
2019-04-12 16:15               ` =?unknown-8bit?b?6Ziu5q2j5pe6?=
2019-04-12 19:48                 ` Sandeep Patil
2019-04-16 12:27                   ` =?unknown-8bit?b?6Ziu5q2j5pe6?=
2019-04-17 16:39                     ` Sandeep Patil
2019-04-17 17:06                       ` Petr Vorel
2019-04-19 15:49                         ` =?unknown-8bit?b?6Ziu5q2j5pe6?=
2019-04-21 22:10                           ` Petr Vorel [this message]
2019-04-23 17:28                             ` =?unknown-8bit?b?6Ziu5q2j5pe6?=
2019-04-23 20:38                               ` Petr Vorel
2019-04-12  3:09       ` =?unknown-8bit?b?6Ziu5q2j5pe6?=
2019-04-24  9:14 ` [LTP] [PATCH " Petr Vorel
2019-04-24 19:23   ` Steve Muckle
2019-04-24 20:19     ` Petr Vorel
2019-04-25  3:08     ` =?unknown-8bit?b?6Ziu5q2j5pe6?=

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=20190421221030.GA11307@x230 \
    --to=pvorel@suse.cz \
    --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