On Tue, Apr 27, 2010 at 04:10:56PM +0200, Tor Arntsen wrote: > On Tue, Apr 27, 2010 at 15:57, Gary V. Vaughan > <git@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > > Add defaults for Tru64 Unix. ?Without this patch I cannot compile > > git on Tru64 5.1. > > --- > > ?Makefile | ? ?6 ++++++ > > ?1 file changed, 6 insertions(+) > > > > Index: b/Makefile > > =================================================================== > > --- a/Makefile > > +++ b/Makefile > > @@ -734,6 +734,12 @@ EXTLIBS = > > ?# because maintaining the nesting to match is a pain. ?If > > ?# we had "elif" things would have been much nicer... > > > > +ifeq ($(uname_S),OSF1) > > + ? ? ? # Need this for u_short definitions et al > > + ? ? ? BASIC_CFLAGS += -D_OSF_SOURCE > > + ? ? ? NO_STRTOULL = YesPlease > > + ? ? ? NO_NSEC = YesPlease > > +endif > > I'll try your patch for OSF1, Much appreciated :) > but (ref. a patch I sent earlier, in its > first revision) I needed several other changes in order to compile on > 5.1 (I also needed those you have above), e.g. > -D_POSIX_C_SOURCE=1 NO_STRCASESTR = YesPlease NO_STRTOUMAX = YesPlease > NO_STRLCPY = YesPlease NO_MEMMEM = YesPlease NO_UINTMAX_T = YesPlease > NO_C99_FORMAT = YesPlease > and > NO_TCLTK = YesPlease Indeed, I don't mean to imply that this patch is all that is needed for OSF1, merely that the changes it contains benefit only OSF1. Please bear in mind that I build using configure, and may have missed something necessary for a make-only driven build. > because V5.1 comes with tcl/tk 8.2 and gitk refuses to start with > anything older than 8.4. > I had some other too, but those could be worked around by building and > installing own versions of iconv, openssl, zlib, python, expat. Ack. And since that is our business, we do indeed build git against our own packages of relatively cutting edge releases of prerequisite OS software on all our hosts (including all of the above). Cheers, -- Gary V. Vaughan (gary@xxxxxxxxxxxxxxxxxx) -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html