From: Boyd Lynn Gerber <gerberb@zenez.com>
To: Aidan Van Dyk <aidan@highrise.ca>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Compile fix for SCO OPenServer
Date: Wed, 30 Jul 2008 18:32:12 -0600 [thread overview]
Message-ID: <alpine.LNX.1.10.0807301831320.13032@xenau.zenez.com> (raw)
In-Reply-To: <20080731001112.GP10399@yugib.highrise.ca>
On Wed, 30 Jul 2008, Aidan Van Dyk wrote:
> * Boyd Lynn Gerber <gerberb@zenez.com> [080730 20:00]:
> > So what do you think we need to have. I really do not see the need for
> > __OPENSERVER__. Do you?
>
> No, I think I saw that long ago, when I said:
> > Sorry, a bit premature on my end...
>
> With SNPRINTF_RETURNS_BOGUS and NO_MKDTEMP and CFLAGS set for make, I
> don't need any source code changes to compile on SCO.
>
> And as long as I have GNU bash and diff available, the test suite passes
> as well. Well, all except for t9500-gitweb-standalone-no-errors.sh:
> [Thu Jul 31 00:08:46 2008] gitweb.perl: -T and -B not implemented on filehandles at /u/aidan/git/t/trash directory/../../gitweb/gitweb.perl line 2444.
>
> Perl claims:
> This is perl, v5.8.8 built for i586-pc-sysv5
>
> But again, I don't plan on running gitweb on this SCO box either...
OK, thanks, I did not want to not respond if things were needed.
Thanks,
--
Boyd Gerber <gerberb@zenez.com>
ZENEZ 1042 East Fort Union #135, Midvale Utah 84047
next prev parent reply other threads:[~2008-07-31 0:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 17:21 [PATCH] Compile fix for SCO OpenServer Aidan Van Dyk
2008-07-30 18:49 ` Compile fix for SCO OPenServer Aidan Van Dyk
2008-07-30 20:01 ` Junio C Hamano
2008-07-30 20:09 ` Boyd Lynn Gerber
2008-07-30 20:18 ` Junio C Hamano
2008-07-30 20:43 ` Aidan Van Dyk
2008-07-30 21:28 ` Boyd Lynn Gerber
2008-07-30 22:56 ` Aidan Van Dyk
2008-07-30 23:30 ` Boyd Lynn Gerber
2008-07-30 23:44 ` Aidan Van Dyk
2008-07-31 0:00 ` Boyd Lynn Gerber
2008-07-31 0:11 ` Aidan Van Dyk
2008-07-31 0:32 ` Boyd Lynn Gerber [this message]
2008-07-30 20:13 ` Boyd Lynn Gerber
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=alpine.LNX.1.10.0807301831320.13032@xenau.zenez.com \
--to=gerberb@zenez.com \
--cc=aidan@highrise.ca \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).