public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Joachim Schmitz" <jojo@schmitz-digital•de>
To: <git@vger•kernel.org>
Cc: <rsbecker@nexbridge•com>
Subject: RE: Porting git to HP NonStop
Date: Fri, 10 Aug 2012 17:04:06 +0200	[thread overview]
Message-ID: <003a01cd7709$63725260$2a56f720$@schmitz-digital.de> (raw)

> From: git-owner@vger•kernel.org [mailto:git-owner@vger•kernel.org] On
> Behalf Of Joachim Schmitz
> Sent: Friday, August 10, 2012 5:01 PM
> To: git@vger•kernel.org
> Cc: rsbecker@nexbridge•com
> Subject: RE: [PATCH v2] add tests for 'git rebase --keep-empty'
> 
> Hi folks
> 
> I'm a brand new subscriper of this mailing list, so please forgive if I
violate
> some protocol or talk about things that had been discussed to death
earlier.

Ahrgl, 1st mistake: wrong subject, sorry

> I'm currently in the process of porting git (1.7.11.4 for now) to the HP
NonStop
> platform and found several issues:
> 
> - HP NonStop is lacking poll(), git is making quite some use of it.
> My Solution: I 'stole' the implementation from GNUlib, which implements
> poll() using select().
> Git should either provide its own poll(), not use it at all or resort to
using
> GNUlib, what do you think?.
> 
> - HP NonStop is lacking getrlimit(), fsync(), setitimer() and memory
mapped IO.
> For now I've commented out the part that used getrlimit() and use a home
> brewed implementation for fsync(), setitimer() and mmap().
> 
> - git makes use of some C99 features or at least feature that are not
availabe in
> C89, like 'inline'
> C89 is the default compiler on HP NonStop, but we also habe a c99
compiler, so
> telling configure to search for c99  should help here.
> 
> - libintl and libiconv sem to get linked in the wrong order, resulting in
> unresolved symbols.
> I've just moved the "ifndef NO_GETTEXT" section of Makefile to above the
> "ifdef NEEDS_LIBICONF" section.
> 
> - HP NonStop doesn't have stat.st_blocks, this is used in
builtin/count-objects.c
> around line 45, not sure yet how to fix that.
> 
> - HP NonStop doesn't have stat.st_?time.nsec, there are several places
what an
> "#ifdef USE_NSEC" is missing, I can provide a diff if needed (offending
> files: builtin/fetch-pack.c and read-cache.c).
> 
> - HP NonStop doesn't know SA_RESTART
> I fixed that with a "#define SA_RESTART 0" in the 3 files affected
(builtin/log.c,
> fast-import.c and progress.c)
> 
> - using C99 but not using #include <strings.h> results in compiler errors
due to
> a missing prototype for strcasecmp() I fixed it by adding that to
git-compat-
> util.h
> 
> - HP NonStop doesn't have intptr_t and uintpr_t (in its stdint.h) I added
them to
> git-compat-util.h
> 
> - HP NonStop doesn't need the " #define _XOPEN_SOURCE 600", just like
> __APPLE__, __FreeBSD__ etc, so I added a "&& !defined(__TANDEM) in git-
> compat-util.h
> 
> - there seems to be an issue with compat/fnmatch/fnmatch.c not including
> string.h, seems that HAVE_STRING_H is not #define'd anywhere.
> 
> 
> - Once compiled and installed, a simple jojo@\hpitug:/home/jojo/GitHub $
git
> clone git://github.com/git/git.git fails with:
> /home/jojo/GitHub/git/.git/branches/: No such file or directory After
creating
> those manually it fails because the directory isn't empty,
> catch-22
> After some trial'n'error I found that the culprit seems to be the
subdirectories
> branches, hook and info in /usr/local/share/git-core/templates/, if I
> remove/rename those, the above command works fine.
> I have no idea why that is nor how to properly fix it, anyone out there?
> 
> Bye, Jojo

             reply	other threads:[~2012-08-10 15:04 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-10 15:04 Joachim Schmitz [this message]
2012-08-10 16:27 ` Porting git to HP NonStop Shawn Pearce
2012-08-10 17:32   ` Joachim Schmitz
2012-08-10 17:38     ` Shawn Pearce
2012-08-19  8:57       ` Joachim Schmitz
2012-08-19 17:23         ` Junio C Hamano
2012-08-20 10:22           ` Joachim Schmitz
2012-08-20 14:41             ` Junio C Hamano
2012-08-20 16:09               ` Joachim Schmitz
2012-08-20 16:53                 ` Junio C Hamano
2012-08-22 16:30                   ` Joachim Schmitz
2012-08-22 17:00                     ` Brandon Casey
2012-08-22 17:13                       ` Brandon Casey
2012-08-22 17:18                       ` Joachim Schmitz
2012-08-22 17:23                         ` Brandon Casey
2012-08-22 17:30                           ` Joachim Schmitz
2012-08-22 17:30                       ` Junio C Hamano
2012-08-22 18:01                         ` Joachim Schmitz
2012-08-22 18:24                           ` Junio C Hamano
2012-08-22 18:52                             ` Joachim Schmitz
2012-08-22 17:41                       ` Johannes Sixt
2012-08-22 18:02                         ` Joachim Schmitz
2012-08-22 18:09                           ` Johannes Sixt
2012-08-22 18:18                             ` Joachim Schmitz
2012-08-22 18:09                         ` Brandon Casey
2012-08-22 18:24                           ` Brandon Casey
2012-08-22 18:33                             ` Junio C Hamano
2012-08-22 18:38                               ` Brandon Casey
2012-08-22 20:18                                 ` Joachim Schmitz
2012-08-22 20:49                                   ` Junio C Hamano
2012-08-22 21:05                                     ` Joachim Schmitz
2012-08-22 21:12                                       ` Junio C Hamano
2012-08-22 21:22                                         ` Joachim Schmitz
2012-08-22 21:54                                           ` Junio C Hamano
2012-08-22 18:26                           ` Junio C Hamano
2012-08-10 20:08   ` Joachim Schmitz
2012-08-11  8:20   ` Johannes Sixt
2012-08-14  7:05   ` Joachim Schmitz
2012-08-14 14:56     ` Junio C Hamano

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='003a01cd7709$63725260$2a56f720$@schmitz-digital.de' \
    --to=jojo@schmitz-digital$(echo .)de \
    --cc=git@vger$(echo .)kernel.org \
    --cc=rsbecker@nexbridge$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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