From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>, <randall.s.becker@rogers.com>
Cc: <git@vger.kernel.org>
Subject: RE: [PATCH v4 3/4] Bring NonStop platform definitions up to date in git-compat-util.h
Date: Wed, 24 Jan 2018 15:49:46 -0500 [thread overview]
Message-ID: <001601d39554$e19d24c0$a4d76e40$@nexbridge.com> (raw)
In-Reply-To: <xmqq1sifdmf3.fsf@gitster.mtv.corp.google.com>
On January 24, 2018 3:36 PM, Junio C Hamano wrote:
> randall.s.becker@rogers.com writes:
>
> > From: "Randall S. Becker" <rsbecker@nexbridge.com>
> >
> > Add correct FLOSS (NonStop platform emulation) definitions into
> > git-compat-util.h to allow correct emulation of non-platform
> > behaviour. Also added NSIG definition that is not explicitly supplied
> > in signal.h on platform.
> >
> > Signed-off-by: Randall S. Becker <rsbecker@nexbridge.com>
> > ---
> > git-compat-util.h | 15 +++++++++++++++
> > 1 file changed, 15 insertions(+)
> >
> > diff --git a/git-compat-util.h b/git-compat-util.h index
> > 68b2ad531..fb3ef0dcf 100644
> > --- a/git-compat-util.h
> > +++ b/git-compat-util.h
> > @@ -378,6 +378,21 @@ static inline char *git_find_last_dir_sep(const
> > char *path) #define find_last_dir_sep git_find_last_dir_sep #endif
> >
> > +#ifdef __TANDEM
> > +#if !defined(_THREAD_SUPPORT_FUNCTIONS) &&
> !defined(_PUT_MODEL_)
> > +/* #include <floss.h(floss_read,floss_write,floss_fsync,floss_fork)>
> > +*/
> > +/* #include <floss.h(floss_fork)> */
> > +#endif
>
> The above adds a conditional no-op? That's confusing...
We are trying to make PUT work with git on NonStop. I can't tell you how
much of a pain it is. This is a placeholder for others (outside our group)
to know where to muck. I can remove it if you don't want it there.
> > +#include <floss.h(floss_execl,floss_execlp,floss_execv,floss_execvp)>
> > +#include <floss.h(floss_getpwuid)>
> > +#if ! defined NSIG
> > +/* NonStop NSE and NSX do not provide NSIG. SIGGUARDIAN(99) is the
> highest
> > + known, by detective work using kill -l as a list is all signals
> > + instead of signal.h where it should be. */ # define NSIG 100
> > +#endif #endif
> > +
> > #if defined(__HP_cc) && (__HP_cc >= 61000) #define NORETURN
> > __attribute__((noreturn)) #define NORETURN_PTR
next prev parent reply other threads:[~2018-01-24 20:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-21 23:41 [PATCH v4 0/4] Force pipes to flush immediately on NonStop platform randall.s.becker
2018-01-21 23:42 ` [PATCH v4 1/4] Add tar extract install options override in installation processing randall.s.becker
2018-01-24 20:33 ` Junio C Hamano
2018-01-24 22:01 ` Todd Zullinger
2018-01-24 22:27 ` Randall S. Becker
2018-01-24 23:39 ` Ramsay Jones
2018-01-21 23:42 ` [PATCH v4 2/4] Define config options required for the HPE NonStop NSX and NSE platforms randall.s.becker
2018-01-24 21:19 ` Junio C Hamano
2018-01-24 21:49 ` randall.s.becker
2018-01-21 23:42 ` [PATCH v4 3/4] Bring NonStop platform definitions up to date in git-compat-util.h randall.s.becker
2018-01-24 20:36 ` Junio C Hamano
2018-01-24 20:49 ` Randall S. Becker [this message]
2018-01-24 21:17 ` Junio C Hamano
2018-01-24 21:45 ` Junio C Hamano
2018-01-24 21:51 ` Randall S. Becker
2018-01-21 23:42 ` [PATCH v4 4/4] Add intptr_t and uintptr_t to regcomp.c for NonStop platform randall.s.becker
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='001601d39554$e19d24c0$a4d76e40$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=randall.s.becker@rogers.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).