Re: timespec declaration issue on Tru64

[Ralf Wildenhues]

Hello, and sorry for the delay,

* Daniel Richard G. wrote on Mon, Dec 15, 2008 at 02:49:19AM CET:
> 
> Anyway, I was playing around with this a bit more. The compiler is choking 
> somewhere inside the #include<signal.h> at the top of sig2str.c.

This was already fixed, thanks!

[...]
> Everything else builds fine. Although I did run into one curious Make error 
> (using /usr/bin/make):
> 
> ----begin build log excerpt----
> rm -f t-ref-del.sed ref-del.sed
> sed -e '/^#/d' -e 's/@''PACKAGE''@/coreutils/g' ref-del.sin > t-ref-del.sed
> mv t-ref-del.sed ref-del.sed
> Making all in src
> Make: bad lock name:  chcon chgrp chown chmod cp dd dircolors du ginstall 
> link 
> ln dir vdir ls mkdir mkfifo mknod mktemp mv nohup readlink rm rmdir shred 
> stat 
> sync touch unlink cat cksum comm csplit cut expand fmt fold head join groups 
> md5sum nl od paste pr ptx sha1sum sha224sum sha256sum sha384sum sha512sum 
> shuf 
> sort split sum tac tail tr tsort unexpand uniq wc basename date dirname echo 
> env expr factor false id kill logname pathchk printenv printf pwd runcon seq 
> sleep tee test timeout true truncate tty whoami yes base64.  Stop.
> *** Exit 1
> Stop.
> *** Exit 1
> Stop.
> ----end build log excerpt----
> 
> GNU Make got through that without a problem, but... should gmake be a 
> prerequisite for building coreutils?

Oh well.  OSF make chokes upon instances of '[' in the Makefile; it
seems to use it as some internal separator for locks or so.

Jim, it may be possible that the comment deleted in d9903062cf might
have hinted towards this; but it mentioned problems with the shell
rather than with make, and anyway I don't see how OSF make could have
correctly interpreted the file before the change.

I guess the easiest would be to require gmake on Tru64/OSF, the only
other choice I see is to fully remove all instances of [ from target
and dependency lists (thus only rename it at install time), which would
be rather cumbersome.

Cheers,
Ralf