Of course, we don't want as many as parameters. Simply command lines
are absolutely better. But, it is impossible owing to complicated
systems. This is why you supply a lot of option commands.
I think that for most of beginners installation is a big barrier. If
in this stage they had a problem, they couldn't do anything. Mailing
archives could be a source for hints, but are too big and are
disorganized to find the answer for beginner. Illustrate just a few
examples for typical systems in home page is very helpful.
> On Apr 25, 2008, at 1:24 AM, Koun SHIRAI wrote:
>> I understand that it is difficult to fully describe practical
>> notifications for each implementation, because of a lots of OS's and
>> its frequent revisions. In spite of this difficulty, I am wondering
>> why typical examples for configure are not given in, for example,
>> README or homepage. In README, concrete names of systems, such as
>> Linux 32bit with gcc or OSX (10.4), are listed for those systems
>> have been tested. Hence, at least, for these systems, it is possible
>> to provide concrete form for configure command. Even these minimum
>> information is very useful for beginners who do not have any idea
>> which options must be used. This would significantly reduce questions
>> like me.
> Sure -- what do you have in mind? I think the reason we didn't
> include command lines is because in many cases, you don't really need
> many (any?) additional command line flags. For example:
> make all install
> Would give you a default configuration with default compilers (GNU)
> installed into /usr/local.
> Do you have some suggestions for what kind of examples we should
> Jeff Squyres
> Cisco Systems
> users mailing list
Nanoscience and Nanotechnology Center $B7W;;5!%J%N%^%F%j(B
8-1, Mihogaoka, Ibaraki
Osaka 567-0047, JAPAN $B0q(B