Additional fuel for this discussion-- the Windows build now fails as well unless you specify "configure --disable-gnutls".
On 4/28/10 2:53 PM, DRC wrote: > There are a couple of problems with this, as I see it: > > 1) GNU TLS support is enabled by default, so if GNU TLS isn't installed > on the system (which is the case for non-Linux systems, generally), then > configure fails. Our build should not require GNU TLS, nor should it > require that the user explicitly specify --disable-gnutls. > > 2) The PKG_CHECK_MODULES macro isn't generally available on all systems. > Not just OS X, as it turns out. A Google search of several forums > seems to indicate that it isn't present on FreeBSD as well. > > 3) The PKG_CHECK_MODULES macro always generates a fatal condition if GNU > TLS isn't available. > > > I believe that the behavior should be as follows: > > -- A mechanism other than PKG_CHECK_MODULES should be used to detect the > presence of GNU TLS (AC_CHECK_LIB or AC_CHECK_HEADER, probably.) > > -- If GNU TLS is present, then it should be enabled by default. If it > is not present, then it should be disabled by default. > > -- If GNU TLS is present, then the user can specify --disable-gnutls to > disable it. > > > An alternative solution: > > -- PKG_CHECK_MODULES should be made non-fatal, if possible, or ... > -- Enabling GNU TLS support should not be the default. > > -- A local version of PKG_CHECK_MODULES should be included in our build > for use on systems that do not provide it. > > > How to go about doing any of the above is left as an exercise for the > reader. > > DRC ------------------------------------------------------------------------------ _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
