Next Previous Table of Contents

### 15. Kérdések és Válaszok

This section addresses questions by users that were answered by the KDevelop Team or by their supporters on the KDevelop mailing list during experiences with the current versions of KDevelop as well as bug reporting in general.

### 15.1 Bug Reporting

Another improvement of KDevelop is the integrated bug-reporting system via email. If you experience a bug, you have the option to send the KDevelop development team a bug report either by your email-client or by the bug-report dialog. All bug-reports are collected on the KDevelop web site and can be reviewed on http://bugs.kde.org//db/pa/lkdevelop.html.

To send bug reports, please use the email address submit@bugs.kde.org. If you want to use KDevelop for direct bug-reporting, choose "Bug Report" from the Help-menu. You are presented the report dialog that lets you enter all necessary information about the bug you found. After pressing "OK", the dialog's contents is sent there automatically.

### 15.2 Where to get Information

Q: I have a question which is not addressed in the FAQ file, nor in the manuals of KDevelop. Where should I turn to ?

A: In any case send all requests that are regarding KDevelop by subscribing to the KDevelop mailing list at kdevelop-request@barney.cs.uni-potsdam.de. Send a mail with an empty header and "subscribe youremailaddres" as contents; then you can participate on the discussions. All questions should go there and will be addressed there as well. If you stick to that, you will get the most help by the developers and all users having the same problems, as well as helping to keep the FAQ up to date.

The KDevelop Homepage at http://www.kdevelop.org also contains a mailing-list archive that allows you to browse the mails already send by the subscribers, so you should look there first as most problems should have been addressed already by the team or other users.

### 15.3 Library and System Problems

Q: Wrong JPEG library version: library is 61, caller expects 62

A: There are 2 ways.

1. When the kdelibs are installed it installs header files for the jpeg libraries, these are version 61, however most distributions (Redhat) use version 62 libraries. To fix this just remove jpeglib.h from /opt/kde/include. The pukka include file for version 62 should then be picked up. However looking at the error message above it may be the other way round, in any case ensure you only have on version of the header file, the library and that they are consistent. It is useful to use the locate command to verify that I have the correct version of a library and header files e.g. updatedb locate libjpeg locate jpeglib
2. You must recompiled kdesupport without jpeg library (./configure --with-libjpeg --with-libgif).

Q:

> `

>     make[2]: Entering directory `/usr/local/src/kdevelop-0.3/po'
>     cd .. && automake --gnu --include-deps po/Makefile
>     aclocal.m4: 2709: `AM_PROG_INSTALL' is obsolete; use `AC_PROG_INSTALL'
>     make[2]: *** [Makefile.in] Error 1

> `

A: Workaround for automake-1.4/automake-2.13 users: Just run "aclocal" manually, then it will compile.

Q: What must i do, if configure said ,that i need giflib23.

A: Try a newer snap of kdesupport, or maybe you have another giflib installed?

Q: How can I convert a KDevelop 0.2 project to a 0.3 one?

A: Please change the AC_OUTPUT in the configure.in to a oneline version

for example: old version:

> `

>     AC_OUTPUT(Makefile \
>     kdevelop/kwrite/Makefile \
>     kdevelop/templates/Makefile
>     )

> `

new version:

> `

>     AC_OUTPUT(Makefile kdevelop/kwrite/Makefile kdevelop/templates/Makefile)

> `

Q: I get the following Linker errors when using SuSE Linux with KDE 1.1, what do I have to do to get KDevelop linked ?

> `

>     /usr/lib/libqt.so:
>     warning: multiple common of `QArrayT<char> type_info node'
>     ckdevelop.o: warning: previous common is here
>     ckdevelop.o: In function `CKDevelop::slotFileSaveAll(void)':
>     ckdevelop.o(.text+0x784): undefined reference to `kdebug(unsigned short,
>     unsigned short, char const *,...)'
>     ckdevelop.o(.text+0x839): undefined reference to `kdebug(unsigned short,
>     unsigned short, char const *,...)'
>     ckdevelop.o(.text+0x89d): undefined reference to `kdebug(unsigned short,
>     unsigned short, char const *,...)'
>     ckdevelop.o: In function `CKDevelop::slotFileSaveAs(void)':
>     ckdevelop.o(.text+0xd28): undefined reference to `kdebug(unsigned short,
>     unsigned short, char const *,...)'
>     ckdevelop.o: In function `CKDevelop::slotFileClose(void)':
>     ckdevelop.o(.text+0x1216): undefined reference to `kdebug(unsigned short,
>     unsigned short, char const *,...)'
>     ckdevelop.o(.text+0x1263): more undefined references to `kdebug(unsigned
>     short, unsigned short, char const     *,...)' follow  collect2: ld returned 1
>     exit status  make[2]: ***
>     [kdevelop] Error 1  make[2]: Leaving directory
>     '/home/LinuXDaten/Programme_Updates_Packete/KDE_Updates/Kdevelop_actual_snapshot/kdevelop-0.3/kdevelop'
>     make[1]: *** [all-recursive] Error 1  make[1]: Leaving directory
>     `/home/LinuXDaten/Programme_Updates_Packete/KDE_Updates/Kdevelop_actual_snapshot/kdevelop-0.3'
>     make: *** [all-recursive-am] Error 2

> `

A: If you have the SuSE rpm´s of KDE-1.1, you must recompile the kdelibs without the patch commited by SuSE and reinstall them or get an updated rpm of the kdelibs from ftp://ftp.suse.com

### 15.4 Usage Questions

Q: I see the KDevelop does not allow for usage of the delete key (or backspace deleting when text is marked).

A: go to "Options"->"Editor" and make sure that "Delete on Input" is enabled, then backspace and delete works.

Q: If I add files to my project, will they be automatically included and compiled ?

A: Yes, they are included in the Makefile.am's then and if you make a "Rebuild All" (./configure updates the Makefiles), your new added files will be included as well.

Q: If I removed a file, I get some weird Linker messages. What is wrong with my project ?

A: If the removed file is a header file, that is automatically processed by automoc (running the Qt-Meta-Object-Compiler automatically on all headers), your removed header is still present as a moc-generated *.moc.cpp file and compiled. Remove the according *.moc.cpp file and rebuild the project.

Next Previous Table of Contents