Hi, I have been testing building Cactus on CentOS 7, and with the right packages installed, there doesn't seem to be a need for paths etc to be specified in the optionlist. I have committed a centos.cfg optionlist to simfactory, but there is nothing really specific to CentOS in there.
I would like to be able to configure on new machines without an optionlist; between the Cactus autoconf and known_architectures, and the thorns' configure scripts, much of what we normally put in optionlists shouldn't really be necessary. An optionlist should only be needed for specifying paths to software that are nonstandard, and for quickly overriding CFLAGS etc for specific machines where Cactus doesn't get the options right. With all the "content" in the simfactory optionlists, much of it copy and pasted, corrections in one won't be applied to the others. It would be better for these things to be set in a central place; i.e. the code. What are peoples' thoughts on this? -- Ian Hinder http://members.aei.mpg.de/ianhin
_______________________________________________ Users mailing list [email protected] http://cactuscode.org/mailman/listinfo/users
