Bugzilla – Bug 301
Minor configure bugs with -disable/enable-povray and -disable-spec
Last modified: 2004-04-16 16:18:53
You need to log in before you can comment on or make changes to this bug.
A couple of minor things: 1. If you specify --disable-povray, and the /home/vadve/shared/benchmarks/povray31 directory exists, povray is not disabled. 2. If you specify --enable-povray, the configure script sets the path to povray to be "yes", which is not particularly useful. Instead, configure should print an error message "you must specify a path to povray" or some such. 3. If the path specified to --enable-povray is not correct, we don't notice it. We should check that it exists and issue an error message if not. All of these apply to spec as well. -Chris
Fixed for povray. I leave spec as an exercise to the interested reader (how hard can it be to copy and paste... :-) http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20040412/013735.html http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20040412/013736.html But if no one else gets around to it I will finish this up, later.
Hi Brian, It looks like you broke povray. In particular, USE_POVRAY is no longer set by default on our systems... -Chris
Ok, want to give the spec stuff a try? I assume povray is working OK for you.
Seems to work! Thanks Brian! -Chris
Ok, now spec95 and spec2000 (and povray) can all be configured and tested automatically. The rest of the patches (except configure regeneration) are here: http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20040412/013768.html http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20040412/013844.html Thanks for the feedback.