From koffice Tue Jul 31 15:48:05 2001 From: owner () bugs ! kde ! org (Stephan Kulow) Date: Tue, 31 Jul 2001 15:48:05 +0000 To: koffice Subject: Bug#30017: marked as done (Warning in .configure (Pyton)) by David Faure X-MARC-Message: https://marc.info/?l=koffice&m=99659470403316 Your message with subj: Bug#30017: Warning in .configure (Pyton) On Tuesday 31 July 2001 17:35, Info wrote: > The story was: first of all, it was Python 2.0 on my comp. When > I see this warning first time, I upgrade it to 2.1. Then repead > ./configure, see message again and sent letter to you. Then I > delete the sourse directory with Koffice at all, and switched > on my main work. Ok, so Python 2.0 wouldn't link, but 2.1 does. > Next time when I have a time to try compiling, I unarch tar.gz > again, ./configure - and there was no such warning (and I reply > to you that "I do all this", that means that I successfully > compile Koffice). As I remember, third time machine say "yes" > for the last of libs in list (name contain word "utils"), for > others she say "no". > > By the way - why ./configure does not contain in first lines > (before configuring process) something like: > if test -f config.cache > then rm config.cache > In general, I think than ./configure script must contain option > "--clean" to remove all config files from previous configuring, > and this option must be default. Maybe, it will be useful to > execute "make clean" when this option swithed on. This is > because in most cases user do "./configure" when he want to > compile from the beginning... Send your wishes about autoconf to the autoconf developers. > I think that this information contains in configure/compiler > messages... :-(( I see on console - "something ... no" - and > think that it is enougth for professionals... Well, of course no. That's why we need the config.log entry, to see the missing symbol and try to guess the missing lib. > I am not a programmer, and I understand more less that you. If > you want to get information without such active&direct emailing > - this information must contain in error messages. > > Or put instruction for user to warning message, in manner: > "If you see this message, please, do: > 1.... > 2.... > 3.... > " It says clearly: figure out which lib is missing and THEN write to use about it. -- David FAURE, david@mandrakesoft.com, faure@kde.org http://perso.mandrakesoft.com/~david/, http://www.konqueror.org/ KDE, Making The Future of Computing Available Today has caused the attached bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I'm talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Stephan Kulow (administrator, KDE bugs database) Received: (at submit) by bugs.kde.org; 30 Jul 2001 08:53:47 +0000 Received: (qmail 1502 invoked by uid 33); 30 Jul 2001 08:53:47 -0000 Date: 30 Jul 2001 08:53:47 -0000 Message-ID: <20010730085347.1501.qmail@master.kde.org> To: submit@bugs.kde.org Subject: Warning in .configure (Pyton) From: 5740@mail.ru Package: koffice Version: CVS 20010727 (using KDE 2.1.2 ) Severity: normal Installed from: Mandrake RPMs Compiler: gcc OS: Linux OS/Compiler notes: Russified Mandrake (Spring2001) ./configure ask me to send you the such message: checking for pthread_create in -lpthread... (cached) yes checking for Python directory... (cached) /usr/local checking for Python2.1... header /usr/include/python2.1 library /usr/lib/python2.1/config modules /usr/lib/python2.1 checking if a Python application links... (cached) no checking if Python depends on -lm... (cached) no checking if Python depends on -lpthread... (cached) no checking if Python depends on -ltcl... (cached) no checking if Python depends on -lpthread -lm... (cached) no checking if Python depends on -lpthread -lm -lutil... (cached) no checking if Python depends on -lpthread -lm -ldb-3 -lutil... (cached) no checking if Python depends on -lpthread -ldb-3... (cached) no checking if Python depends on -lpthread -lm -ldb -ltermcap -lutil... (cached) no checking if Python depends on -lpthread -lm -ldb -lutil... (cached) no configure: warning: it seems, Python depends on another library. Pleae use "make LIBPYTHON='-lpython2.1 -lotherlib'" to fix this and contact the authors to let them know about this problem (Submitted via bugs.kde.org)