There's no a big issue here.. it's just a kind of philosophical question. I've notice that autosetup "./configure" will create a GNUmakefile instead of a Makefile. In my OpenBSD system, bsd make doesn't use the GNUMake file when I type "make". So if I type:
# ./configure # make It will use the orignal Makefile that still is on the repository. So it's pretty easy here to be confused and someone can try to put special flag to the ./configure call with no effect. So seing that.. I've delete the old Makefile and type make again.. Bsd make doesn't use GNUmake file at all.. At least, autosetup have create a BSD compatible make file (even if it's named GNUmakefile). so I can type make -f GNUmakefile and it work fine.. just confusing... May be same kind of confusion may happens on other system. I guess it would be less confusing to generate a makefile named "Makefile" and may be rename the old static Makefile something else. Or may be someone might have a better idea to remove the confusion. -- Martin
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
