Re: [PATCH] Add Tru64/OSF1 support in Makefile

From: Brandon Casey <brandon.casey.ctr@nrlssc.navy.mil>
Date: May 21, 2010, 20:45 UTC
Message-ID: <Bo_XNJQjQnJja3BLqR-rv4YxKSSFpcSLegtSIJn8boisM3ilazwT7w@cipher.nrlssc.navy.mil>
In-Reply-To: <4BD1B5E5.6030307@spacetec.no>

Hi Tor, I've been out of town for a few weeks...

On 04/23/2010 09:59 AM, Tor Arntsen wrote:

Show 13 quoted lines

> On 03/31/10 18:29, Brandon Casey wrote:
> 
>> Can you run the test suite with this ksh?  If it suffers from
>> the same exit status behavior of ksh on IRIX and SunOS, then
>> I have a patch which allows the test suite to run.
> 
> I've run a test (make test -k) on Tru64 V5.1 on today's version of Git (08641d02) plus 
> your  ksh test patch. I haven't done any analysis yet of the tests which failed, but I'll
> start looking at some of them later (particularly the first one that failed, a 'tar'
> test).
> 
> Below is a diff between the output from a run on Linux and the Tru64 one
> (instead of a full log), just to illustrate which ones failed.

I skimmed through the log and it looks like the failures are mostly related to tar and iconv. Possibly your tar is too old, or does not support some option that git is using. The iconv failures related to ISO8859-1 are a little strange since that encoding is very common. Some implementations of iconv can produce a listing of the encodings that are supported. You could check for support for ISO 8859-1.

Many of the other differences are just because some tests were skipped on the Tru64 run that were not skipped on Linux. The tests were skipped because some required binary was missing, like gpg or cvs.

Looks like you were able to run most of the test suite which is good.

> (Is this log too much to post inline? If yes, then I'll use an attachment for any 
> future logs)

I think it was fine.

-brandon