Update of bug #46304 (project make):

                Severity:              3 - Normal => 2 - Minor              
                  Status:                    None => Fixed                  
             Open/Closed:                    Open => Closed                 
       Component Version:                     4.0 => 4.1                    
           Fixed Release:                    None => SCM                    
           Triage Status:                    None => Small Effort           
    _______________________________________________________

Follow-up Comment #1:

I don't see any change in built-in rules that could possibly cause this.  I
think the cause is different: Make now sorts the built-in rules in a
consistent, predictable order, and it just so happens that the .C.o rule is
now tried before the .c.o one (and obviously succeeds under
HAVE_CASE_INSENSITIVE_FS).

IOW, that it worked in Make 3.81 was sheer luck, nothing else, an
implementation detail that determined an otherwise undefined behavior.

I have now fixed this in the repository by making COMPILE.C and LINK.C be
synonyms of COMPILE.c and LINK.c when Make is compiled with this option turned
on.

A comment about README.W32: it's not true that we recommend using
HAVE_CASE_INSENSITIVE_FS on MS-Windows.  We just mention this option as one of
those users might wish activating.  I've now modified README.W32 to make this
even more clear.

Thanks.



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?46304>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/


_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make

Reply via email to