Ralf Hemmecke wrote:
> Though pretty much unix-related, I find this a good rule of thumb.
>
> http://www.gnu.org/software/make/manual/make.html#Utilities-in-Makefiles
>
> But otherwise there should be "configure" to figure out the machine
> differences.
>
> Ralf
I think that is an excellent link. It's a shame more people do not use it.
1) Don't use any special features of ksh or bash.
Seems good to me.
2) The configure script and the Makefile rules for building and installation
should not use any utilities directly except these:
cat cmp cp diff echo egrep expr false grep install-info
ln ls mkdir mv pwd rm rmdir sed sleep sort tar test touch true
I would disagree about 'tar', as several systems have more than one 'tar'
program and they are not all compatible.
3) Use the following make variables to run those programs:
$(AR) $(BISON) $(CC) $(FLEX) $(INSTALL) $(LD) $(LDCONFIG) $(LEX)
$(MAKE) $(MAKEINFO) $(RANLIB) $(TEXI2DVI) $(YACC)
Seems logical to me. I would also add 'tar' to that list, and obviously CXX.
Dave
>
> On 10/20/2009 12:04 PM, David Kirkby wrote:
>> Only a few days ago you agreed we would not have RM, CP and other very
>> basic commands set as environment variables.
>>
>> IMHO, if someone wants 'rm -f' they should type it. Looking in the
>> packages now, 95+% of people use 'rm' or 'rm -f' rather than '$(RM)"
>> so I think it would be better to drop the use of such an environment
>> variable.
>>
>> Dave
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
