So... another small niggle with the build (not sure if auto-tools suffers the same issue)... I ran the cmake build on a machine with an old version of proton installed (0.2)... This caused the build to fail as it detected proton but clearly 0.2 is not a version that the code builds against. Is there any way to fix the CMake build so that if the version of the dependency is inadequate it does not attempt to build the optional parts which depend on the (inadequate) version?
Meanwhile I'll try to uninstall proton to see if it gets further... -- Rob On 25 March 2013 21:07, Fraser Adams <[email protected]> wrote: > Thanks Gordon, that was driving me nuts over the weekend :-) > > The good news then is that aside from the slightly irritating need to do > "sudo ldconfig" after "make install" cmake does appear to work on my Ubuntu > system. > > Is there any way to get cmake to do what "sudo ldconfig" does as part of > its "make install". Is what I'm seeing just an Ubuntu quirk? I've got > /usr/local/lib in my /etc/ld.so.conf.d/libc.conf and cmake installs to > /usr/local/lib > > BTW +1 from me on "keep it but remove that option (and perhaps add in some > commented out examples of common settings?) " > > Frase > > > On 25/03/13 19:15, Gordon Sim wrote: > >> On 03/25/2013 06:56 PM, Fraser Adams wrote: >> >>> This thread went quiet at the weekend :-) >>> >>> does anyone have any thoughts on the "Bad argument: >>> |cluster-mechanism=DIGEST-MD5 ANONYMOUS|" issue. As I say below when I >>> did cmake on 0.20 I had a working install once I'd worked out the sudo >>> ldconfig thing but cmake of 0.21 on trunk gives an install that barfs >>> with that error. >>> >> >> That is an option that is no longer supported (the entire cluster module >> has been removed). Looks like it just hasn't been removed from the sample >> conf file installed. >> >> In fact, that is the only option in that file at present. I'm not sure >> whether it is better to remove the file altogether or keep it but remove >> that option (and perhaps add in some commented out examples of common >> settings?) >> >> >> ------------------------------**------------------------------**--------- >> To unsubscribe, e-mail: >> [email protected].**org<[email protected]> >> For additional commands, e-mail: [email protected] >> >> > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > [email protected].**org<[email protected]> > For additional commands, e-mail: [email protected] > >
