bug-coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: test failures building 5.93 and hpux compiler patch


From: Peter O'Gorman
Subject: Re: test failures building 5.93 and hpux compiler patch
Date: Thu, 17 Nov 2005 07:58:51 -0600
User-agent: Mutt/1.5.6+20040907i

On Wed, Nov 16, 2005 at 10:30:43AM +0100, Jim Meyering wrote:
> Peter O'Gorman <address@hidden> wrote:
 
> The sort failures all correspond to tests using -c that should
> have exited successfully.  Can you use a debugger to see what's
> going wrong?

Okay ... several hours and a headache later..
In sort.c's check function there is a variable named nonunique, which is
declared as type bool. The code later does a compare:
if (<bool,true> <= (int)-1) error
xlc decided that the comparison was true. The solution is to declare
nonunique as an int type.

> 
> The cp/fail-perm failures are because HPUX appears to fail with EACCES
> rather than EPERM.  I've tweaked that test script to accept their
> differing diagnostic.  Patch below.  Would you please confirm that
> it fixes the problem?

It fixes it. Thanks.

> 
> Regarding the date failures, would you please try running a few
> of the commands manually, e.g.,
> env TZ=UTC+4 ./date -u -d '08/01/97 6:00' '+%D,%H:%M'
> ./date -u -d '08/01/97 6:00 UTC +4 hours' '+%D,%H:%M'

% ./date
Thu Nov 17 07:50:57 CST 2005
% ./date -u
zsh: segmentation fault (core dumped)  ./date -u

Adding -u seems to cause a segfault. Unfortunately, I've spent too much
time at this already, so can't really investigate further. Note that all
the replecement functions are being used on this platform, localtime,
tzset, putenv etc.

> Thanks for all of that work.
> Can you get newer versions of those compilers from HP
> or use gcc instead?
> 
> Is there a strong argument for continuing to use HP's compilers?

Yet another dependency not installed on the base system (shared libgcc). 
Okay, I understand.

Thanks,
Peter







reply via email to

[Prev in Thread] Current Thread [Next in Thread]