From: Matt Kraai <kraai@ftbfs.org>
To: Mike Gorchak <mike.gorchak.qnx@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Improve QNX support in GIT
Date: Tue, 26 Feb 2013 09:25:04 -0800 [thread overview]
Message-ID: <20130226172504.GA2271@ftbfs.org> (raw)
Hi Mike,
Mike Gorchak wrote:
> diff --git a/config.mak.uname b/config.mak.uname
> index 8743a6d..2d42ffe 100644
> --- a/config.mak.uname
> +++ b/config.mak.uname
> @@ -527,14 +527,21 @@ ifeq ($(uname_S),QNX)
> HAVE_STRINGS_H = YesPlease
> NEEDS_SOCKET = YesPlease
> NO_FNMATCH_CASEFOLD = YesPlease
> - NO_GETPAGESIZE = YesPlease
> NO_ICONV = YesPlease
> NO_MEMMEM = YesPlease
> - NO_MKDTEMP = YesPlease
> - NO_MKSTEMPS = YesPlease
> NO_NSEC = YesPlease
> - NO_PTHREADS = YesPlease
> NO_R_TO_GCC_LINKER = YesPlease
> - NO_STRCASESTR = YesPlease
> NO_STRLCPY = YesPlease
> + # All QNX 6.x versions have pthread functions in libc
> + # and getpagesize. Leave mkstemps/mkdtemp/strcasestr for
> + # autodetection.
> + ifeq ($(shell expr "$(uname_R)" : '6\.[0-9]\.[0-9]'),5)
> + PTHREAD_LIBS = ""
> + else
> + NO_PTHREADS = YesPlease
> + NO_GETPAGESIZE = YesPlease
> + NO_STRCASESTR = YesPlease
> + NO_MKSTEMPS = YesPlease
> + NO_MKDTEMP = YesPlease
> + endif
> endif
Is there a point to the version checking? I don't know that anyone
has tried to build Git on QNX 4, so adding a case for it seems
misleading.
I didn't realize that QNX 6.3.2 provided getpagesize. Its header
files don't provide a prototype, so when I saw the warning, I assumed
it wasn't available. Since NO_GETPAGESIZE is only used by QNX, if
it's OK to reintroduce the warning, NO_GETPAGESIZE might as well be
removed entirely.
I don't think it's a good idea to just enable thread support. On QNX,
once a process creates a thread, fork stops working. This breaks
commands that create threads and then try to run other programs, such
as "git fetch" with an https remote. If threads are enabled, I think
that the uses of fork need to be audited and, if they can be called
after a thread is created, fixed.
next reply other threads:[~2013-02-26 17:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 17:25 Matt Kraai [this message]
2013-02-26 18:09 ` [PATCH] Improve QNX support in GIT David Michael
2013-02-26 18:36 ` Mike Gorchak
2013-02-26 18:54 ` Mike Gorchak
-- strict thread matches above, loose matches on Subject: below --
2013-02-26 20:13 Matt Kraai
2013-02-26 20:32 ` Mike Gorchak
2013-02-26 20:53 ` Johannes Sixt
2013-02-26 21:02 ` Matt Kraai
2013-02-23 22:02 Mike Gorchak
2013-02-24 7:36 ` Mike Gorchak
2013-02-24 8:46 ` Junio C Hamano
2013-02-24 14:12 ` Mike Gorchak
2013-02-24 21:24 ` Junio C Hamano
2013-02-25 7:14 ` Junio C Hamano
2013-02-25 8:30 ` Mike Gorchak
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=20130226172504.GA2271@ftbfs.org \
--to=kraai@ftbfs.org \
--cc=CAHXAxrMRxKKiEarSQ0fCLt6-zyS=52B+kmZMLDf8SQAGzGbjjQ@mail.gmail.com \
--cc=git@vger.kernel.org \
--cc=mike.gorchak.qnx@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).