Geoffrey Lee wrote: >>exactly... this is what was causing it... >> >> >> > >Being able to build this without having a whole pile of BuildRequires >installed on the machine is admittedly nice but we should fix qt3 on the >alpha also :) > I'm working on it :-/
>>>I seem to see that right now in the patch the qt-gui is disabled by default? >>>That's not very fair, giving one toolkit any preference over another one. >>> >>> >>> >>Put the qt_gui on "1" by default. >> >> >> > > >I want to put out a new unixODBC anyway, the libs packaged is b0rked. >(required X11, gODBCConfig libs was the culprit). > > > >>>so: my preference is: >>> >>>if this is done then we do it for gtk-gui as well (just several more lines >>>of conditional defines and it should be ok) >>> >>> >>> >>This might be more difficult since the gnome-libs-devel is needed by >>configure (configure hangs without it, while with qt3-devel is continues). >> >> >> > > >Strange. In the main ODBC configure script or in the gODBCConfig script? > Don't know... just saw that it borked & decided to add gnome-libs-devel. But gnome-libs-devel doesn't install on the alpha at the moment due to a number of old glib / gtk+ libs that are still hanging around... >AFAIK only gODBCConfig would require such a thing. (and it does). > >If you could test it in your minimal build environement it would be great, >because the cluster in Paris has way too much installed for anyone to tell >the difference. > Just put the src.rpm in /mirrors/new_alpha/SRPMS/ and it'll get built. output should show up in /misc/linux/mandrake/buildout/new_alpha/alpha/ of course, with the old glib / gtk+ libs... it won't get far :-( >Maybe I can hold off the upload for the time being so that we can see if >we can disabled the Gtk+ (sic, I mean Gnome) config application? > Sure! Stefan
