When attempting to generate a Qt project in kdevelop 2.1.2 The following message is generated ( May be an upstream bug though ) configure.in:26: warning: do not use m4_patsubst: use patsubst or m4_bpatsubst configure.in:63: error: m4_popdef: undefined macro: AC_Dest ../autoconf/status.m4:831: AC_CONFIG_FILES is expanded from... configure.in:63: the top level Tried to apply the fix from bug #1795 but that didn't help ( same result )
I had the same problem, but it seems to have gone away with the newest kdevelop (2.1.3).
Jeld? Are you still having problems (i.e. with kdevelop 2.1.3, and preferrably with kde 3.0.3)?
No i don't think it happens in 2.1.3
I am wrong. It does give me the same error as in my initial report.
I don't have kdevelop 2.1.3 merged right now... hope to try to reproduce again soon.
I'm getting the same error with kdevelop 2.1.2 and also with the new version kdevelop 2.1.3 the errormessage is exactly the same.
OK, I've installed kdevelop 2.1.3 and I see the error. Ugly... I toyed around with configure.in and discovered, more by accident than anything else, that if you change the last line (in the QT MDI project) from: AC_OUTPUT(Makefile bar/Makefile bar/docs/Makefile bar/docs/en/Makefile ) To: AC_OUTPUT(Makefile,bar/Makefile,bar/docs/Makefile,bar/docs/en/Makefile ) The problem disappears. As to why, I've absolutely no idea. It just seemed that that function call would like comma-separated parameters, so I tried it and it worked. Please test this. I'll look at including a patched cofigure.in in the kdevelop ebuild. I wish the new kdevelop would have a release already - but development on kdevelop 2.2 is apparently abandoned and I'm afraid 3.0 (Gideon) is a long way from even a prerelease...
I tried modifying the tarballs in /usr/share/apps/kdevelop/templates/, but for some reason it doesn't affect the project dirs kdevelop creates - they still have space-separated lines even though I put comma-separated ones in the tarballs. I've no idea why; if I put a comment in the same configure.in file it appears in the project dir. ??? I take this as an indication that I should go to sleep...
The changes to configure.in you proposed did reduce the errormessage. I was lucky to see that this ugly errors did disapear. On my calculator the messages are reduced to a few warnings: configure.in:26: warning: do not use m4_patsubst: use patsubst or m4_bpatsubst configure.in:62: warning: do not use m4_regexp: use regexp or m4bregexp But the project itself is not usable for me, since the configure script fails with following error when executet (shell and also kdevelop) [-- output of ./configure --] ... checking if autom4te-2.53a.cache should be compiled... yes ./configure: autom4te_2.53a.cache_SUBDIR_included=yes: command not found checking if halleluja should be compiled... yes configure: creating ./config.status ./config.status: halleluja/docs/Makefile: No such file or directory config.status: creating Makefile config.status: creating config.h config.status: config.h is unchanged config.status: executing default-1 commands config.status: executing default commands ./config.status: halleluja/Makefile: No such file or directory (don't worry about that project name. I'm meanwhile running out of ideas, so I had to let myself inspire from the holy bible ;-) the missing files are exactly those whe have separeted by commas in the configure.in I could get read of the above warnings if I use WANT_AUTOMAKE_1_6=1 just on the console, this actually shows that kdevelop is calling a different automake. although I've forced it to use different automake by setting the environment variables.
Seems like my fix doesn't work after all. Sigh....
Maybe someone else will have an idea before I do?
would be nice to have a solution at all. It is really driving me mad not to get a solution for it.
I have found the cause of this. Looks like there is an API discrepancy between autoconf 2.5 and 2.1. The last line of configure.in looks like this AC_OUTPUT(file1 file2 file3...) which is bad m4 syntax in itself since it wants commas between macro arguments, but the problem is, autoconf 2.5 wants this to be AC_CONFIG_FILES([ file1 ]) AC_CONFIG_FILES([ file2 ]) ... AC_OUTPUT As soon as I changed the project to this scheme it started working where just putting commas between files will only generate the first file.
Sorry, looks like my last comment got a bit carried away... stupid konqueror :)
I can acknowledge that these settings to work for me. I still get some warnings but these may be due to an other problem, which I can get solved when I manually start aclocal and then restart autoconf and automake. *** Creating configure configure.in:26: warning: do not use m4_patsubst: use patsubst or m4_bpatsubst configure.in:67: warning: do not use m4_regexp: use regexp or m4_bregexp *** Creating config.h template autoheader-2.53a: `config.h.in' is unchanged *** Creating Makefile templates If you haven't done so in a while, run ./configure --help *** success *** Apart of this my kdevelop doesn't run properly since it claims for not beeing able to find mime-types, but since I don't know if this is the right place to ask for. I'll leave it.
While we are at the topic, why doesn't kdevelop install itself into /usr/kde/3?
Because 3rd party (non- kde-base) apps install in /usr so as to be available from all KDE installations on an equal footing. If it installed in /usr/kde/3, then when you installed kde 3.1 in /usr/kde/3.1 it wouldn't see your kdevelop. --- I'm very glad indeed that this has finally been solved. I'll modify the kdevelop ebuild to install updated files to fix this.
is ther a way of pointing kdevelop to kde's mime-types? is the installation directory the problem for the not found mime-types?
No - it works ok hre, as do other kde apps installed in /usr. What are the mimetype errors you're getting, exactly? On startup of kdevelop?
exact, the startup of kdevelopp works actually ok.as soon as I try to open a file kdevelop blames with a widget with "Could not find mime type" "application/octet-stream" "no mime-types installed" and the console gives the error kio (KSycoca): WARNING: Found version 49, expecting version 59 or higher. kio (KSycoca): WARNING: Outdated database found kdevelop: WARNING: KDE detected X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 42 kio (KSycoca): WARNING: Found version 49, expecting version 59 or higher. kio (KSycoca): WARNING: Outdated database found kio (KSycoca): ERROR: No database available! [...] kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found kdevelop: ERROR: filesharelist not found in /usr/kde/3/bin:/bin:/usr/bin:/usr/local/bin:/opt/bin:/opt/opera/bin:/usr/X11R6/bin:/opt/sun-jdk-1.4.0/bin:/opt/sun-jdk-1.4.0/jre/bin:/usr/kde/cvs/bin:/usr/qt/3/bin:/usr/qt/2/bin:/usr/kde/3/bin:/usr/sbin I need to say, that this error occures since I've emerged (upgraded) to kdevelop 2.1.3. I had befor 2.1.2. (also I had gideon running for a few days)
I have to add that any other kde application do work ok. they do not blame about mime-types at all. They are all showing the associatet icons on file open and save. I've also cvs kde 3.1 running. When I use the kde 3.1 kdevelop works fine. so this just doesn't work with kde 3.0.3. Since kde 3.0.3 is the stable version, would be nice to have this one running ok.
OK, I've committed a kdevelop-2.1.3-r1 that installs fixed template tarballs fo the three types of qt projects. Please confirm that it's ok so that we can finally close this bug :-)
Akif: because you compiled kdevelop against kde 3.1, it won't work with 3.0. you have to recompile it against 3.0 (and it'l work with 3.1 too). Do: "KDELIBSDIR=/usr/kde/3 emerge kdevelop" and it should work.
Akif: adding you to cc:, please read my previous comment.
ok, I've emerged the new r1 and it works errorless here. fine ;-)
Should be closed AFAICS.
