Re: coreutils build on OSF/1 4.0d

[Jim Meyering]

Bruno Haible <address@hidden> wrote:

> Jim Meyering wrote:
>> > 1) "Make: bad lock name" errors when 'make' enters the src directory.
>> > This was already reported in
>> > http://lists.gnu.org/archive/html/bug-coreutils/2004-02/msg00062.html
>>
>> I think using bash is one way to work around that.
>> The problem is with the program named `['.
>
> I used GNU make instead of /usr/bin/make as a workaround. Yes, the problem
> was with the '[': After I removed the mention of [$(EXEEXT) in the list of
> programs and the corresponding rule, the error of 'make' disappeared.

Thanks.  I've documented that:

        * README: Document the OSF/1 4.0d build failure and work-around.
        Reported by Bruno Haible.
        diff --git a/README b/README

index cff225d..236b2d5 100644
--- a/README
+++ b/README
@@ -97,6 +97,18 @@ Here is one possible patch to correct the problem:
 +#ifndef __LP64__


+************************
+OSF/1 4.0d build failure
+------------------------
+
+If you use /usr/bin/make on an OSF/1 4.0d system, it will fail due
+to the presence of the "[" target.  That version of make appears to
+treat "[" as some syntax relating to locks.  To work around that,
+the best solution is to use GNU make.  Otherwise, simply remove
+all mention of "[$(EXEEXT)" from src/Makefile.
+
+
+
 **********************
 Running tests as root:
 ----------------------