From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "beanhuo@micron.com" <beanhuo@micron.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"dgilbert@interlog.com" <dgilbert@interlog.com>
Cc: "hare@suse.de" <hare@suse.de>
Subject: Re: [RFC] sg3_utils: sgp_dd: work around on pthread_cancel for android
Date: Fri, 22 Dec 2017 18:24:51 +0000 [thread overview]
Message-ID: <1513967090.2579.13.camel@sandisk.com> (raw)
In-Reply-To: <e5c8b6616ea7487d83087da7623576ae@SIWEX5A.sing.micron.com>
On Fri, 2017-12-22 at 17:00 +0000, Bean Huo (beanhuo) wrote:
> case "${host}" in
> + *-*-android*)
> + AC_DEFINE_UNQUOTED(SG_ON_ANDROID, 1, [sg3_utils on android])
> + AC_DEFINE_UNQUOTED(SG_LIB_LINUX, 1, [sg3_utils on linux])
> + AC_SUBST([os_cflags], [''])
> + AC_SUBST([os_libs], ['']) ;;
> *-*-linux-gnu*)
> AC_DEFINE_UNQUOTED(SG_LIB_LINUX, 1, [sg3_utils on linux])
> AC_SUBST([os_cflags], [''])
> @@ -79,6 +84,7 @@ AM_CONDITIONAL(OS_OSF, [echo $host_os | grep '^osf' > /dev/null])
> AM_CONDITIONAL(OS_SOLARIS, [echo $host_os | grep '^solaris' > /dev/null])
> AM_CONDITIONAL(OS_WIN32_MINGW, [echo $host_os | grep '^mingw' > /dev/null])
> AM_CONDITIONAL(OS_WIN32_CYGWIN, [echo $host_os | grep '^cygwin' > /dev/null])
> +AM_CONDITIONAL(OS_ANDROID, [echo $host_os | grep 'android' > /dev/null])
Hello Bean,
Please consider to use AC_CHECK_FUNC([pthread_cancel]) or similar to check the
availability of pthread_cancel(). Explicit distro checks are much harder to maintain
than checks for individual functions.
Thanks,
Bart.
next prev parent reply other threads:[~2017-12-22 18:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 17:00 [RFC] sg3_utils: sgp_dd: work around on pthread_cancel for android Bean Huo (beanhuo)
2017-12-22 18:24 ` Bart Van Assche [this message]
2017-12-23 0:43 ` Douglas Gilbert
-- strict thread matches above, loose matches on Subject: below --
2017-12-23 10:19 Bean Huo (beanhuo)
2017-12-23 13:29 ` Bart Van Assche
2017-12-26 22:21 Bean Huo (beanhuo)
2018-01-02 16:40 ` Bart Van Assche
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=1513967090.2579.13.camel@sandisk.com \
--to=bart.vanassche@wdc.com \
--cc=beanhuo@micron.com \
--cc=dgilbert@interlog.com \
--cc=hare@suse.de \
--cc=linux-scsi@vger.kernel.org \
/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