On Tuesday 04 September 2007 15:34, Michel Meyers wrote: > Kern Sibbald wrote: > > On Tuesday 04 September 2007 13:23, Michel Meyers wrote: > >> Kern Sibbald wrote: > >>> Hello, > >>> > >>> Now that we have just released version 2.2.1, as Murphy's law dictates, > >>> we have a couple of more important bugs that seem to affect only older > >>> systems. > >> > >> [...] > >> > >>> Question: does anyone feel that the 2.2.2 release should have anything > >>> other than Eric's PostgreSQL configure fix, my Director crash fix, and > >>> Scott's new .spec files (already committed)? > >> > >> I would love to see a configure flag that would allow people to specify > >> qwt-qt4 as qwt library and have configure look for that. That would > >> allow an easy workaround for the compilation problems with bat on > >> Debian/Ubuntu systems (just give that flag instead of changing Makefile > >> and bat.pro after the configure). > > > > Uh, maybe the documentation is not complete, but I think what you are > > requesting is what I have provided, particularly with the depkgs-qt > > release, though perhaps not as totally automated as is possible. > > Hmm, OK I must admit I do not reada the docs any more when I compile and > I don't use depkgs at all. I use Debian's source packages to get the > stuff I need as I don't like doing 'out of packaging stuff (I'm actually > contradicting myself as I compile Bacula manually instead of using the > Debian packages ;) ). > > The issue is: Debian has multiple qwts, but only /usr/include/qwt-qt4 > and the library called libqwt-qt4 works for compiling bat. configure > however uses /usr/include/qwt, no matter what one specifies to the > --with-qwt parameter.
Yes, I saw that problem when I was trying all the different systems. My conclusion was that it was a packaging error. The name of the library is libqwt not libqwt-qt4. The packager did not, as far as I can tell, use the standard Debian alternatives methods, which work fine in other cases. Although I didn't explicitly document this, it seems that there are a number of ways to handle it: 1. complain to the packager to get him/her to use the correct name or Debian alternatives as all the other distros have done. 2. Use depkgs-qt (which is what I did from my Mepis distro), 3. specify the include directory using --with-qwt and the incorrectly (IMO) named library using the LIBS environment variable. Since I did not try item 3, I'm not sure it will work. > > Given that we have had several users with this problem in the -users > list, I guess I'm not the only one doing it that way (without depkgs). > > The workaround is to run configure and then go into src/qt-console to > fix the references to qwt in the includes and library sections of > Makefile and bat.pro (replace qwt by qwt-qt4 and compilation works). > > As mentioned before, it is no big deal but some people just expect > configure to find the proper includes or at least allow you to override > them, neither of which seems to work here. I agree, but as I indicated, I think the packaging is incorrect. > I'd contribute a patch, but > alas I am absolutely clueless as to how configure and the likes function > (I'm already happy if I manage to hack a Makefile to do my bidding). I decided not to try to "kludge" the ./configure since it seems to me to be a very unusual case. > > Greetings, > Michel ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
