Re: Add some autoconf warnings

2005-03-18 Thread Alexandre Julliard
Francois Gouget <[EMAIL PROTECTED]> writes: > Maybe a check that there is at least one functional sound system would > be ok? > > if test "$ac_cv_c_opensoundsystem" = "no" -a -z "$ALSALIBS" -a \ > -z "$ARTSC_LIBS" -a -z "$NASLIBS" -a -z "$AUDIOIOLIBS" > then > echo "*** No sound sys

Re: Add some autoconf warnings

2005-03-18 Thread Andreas Mohr
Hi, On Fri, Mar 18, 2005 at 07:01:21PM +0200, Anssi Hannula wrote: > Chris Morgan wrote: > >Given the huge amount of output from configure I think it would make > >sense to print out what was and wasn't supported as far as modules. > >The handful of extra lines would save people from being confus

Re: Add some autoconf warnings

2005-03-18 Thread Anssi Hannula
Chris Morgan wrote: Given the huge amount of output from configure I think it would make sense to print out what was and wasn't supported as far as modules. The handful of extra lines would save people from being confused about whether support was or wasn't built in. Other projects print this dat

Re: Add some autoconf warnings

2005-03-18 Thread Chris Morgan
I had sent in a patch similar to this a while back. I still think it is very useful to warn at least about OpenGL, I recall having to help a lot of people try to debug issues with not having that support. Given the huge amount of output from configure I think it would make sense to print out wha

Re: Add some autoconf warnings

2005-03-18 Thread Francois Gouget
On Fri, 18 Mar 2005, Alexandre Julliard wrote: Francois Gouget <[EMAIL PROTECTED]> writes: I thought I had sent this patch months ago but apparently not. The idea is to warn the user when some often used libraries are missing and is based on the warnings issued for bad Mesa or X configurations. Let

Re: Add some autoconf warnings

2005-03-18 Thread Alexandre Julliard
Francois Gouget <[EMAIL PROTECTED]> writes: > I thought I had sent this patch months ago but apparently not. The > idea is to warn the user when some often used libraries are missing > and is based on the warnings issued for bad Mesa or X > configurations. Let me know if the range of checks should