Bug#37870: marked as done (Create new C++ project in kdevelop) by Marc Mutz <mutz at kde.org>

Thu Feb 14 17:34:02 UTC 2002

Your message with subj: Fwd: Re: Bug#37870 acknowledged by developer (Create new C++ project in kdevelop)

--------------Boundary-00=_CY6JIL2RCQ9LZQBTLKIV
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- ----------  Forwarded Message  ----------

Subject: Re: Bug#37870 acknowledged by developer (Create new C++ project =
in kdevelop)
Date: Thu, 14 Feb 2002 15:24:10 +0100
From: "W. Balzer" <Wolfgang.Balzer at dlr.de>
To: Marc Mutz <mutz at kde.org>

Hello,

I was able to solve to problem by myself. While looking into the SuSE
support data base for a completly different problem, I passed by the
following entry:

    http://sdb.suse.de/de/sdb/html/kdevelop_autoconf_73.html

The suggested solution in this entry solved my problem. You may close
the bug report using this information.

Best regards
Wolfgang

Marc Mutz wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>On Thursday 14 February 2002 09:22, you wrote:
>>Dear Stephan,
>>
>>the attached reply has nothing to do with my initial bug report. I
>>have a bug with kdevelop and not kmail, pgp or whatever. According
>>to:
>
><snip>
>
>I've used the wrong number, sorry. But I have already reopened your
> bug report the next day... So if you have had a closer look at the
> bug summary, you would have noticed this ;-)
>
>Marc
>
>- --
>Marc Mutz <mutz at kde.org>
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.0.6 (GNU/Linux)
>Comment: For info see http://www.gnupg.org
>
>iD8DBQE8a4Nb3oWD+L2/6DgRArLSAKCIThik8EKAF3gGYebYpFILl8aCgACbB9D4
>9XsT0ipB5OapQe5ESnaMzPc=3D
>=3DjIDb
>-----END PGP SIGNATURE-----

- -------------------------------------------------------

- --=20
Marc Mutz <mutz at kde.org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8a+T03oWD+L2/6DgRAnHTAKDHlX8ElJ+BGCnY4M/KWgYYi7RYBQCgr7IC
ZSkHUeQSG7jDSeXzkiGvzMY=3D
=3DpC3q
-----END PGP SIGNATURE-----

--------------Boundary-00=_CY6JIL2RCQ9LZQBTLKIV
Content-Type: text/html;
  charset="us-ascii";
  name="Attachment: 1"
Content-Transfer-Encoding: 7bit

<html>
<head>
</head>
<body>
Hello,<br>
<br>
I was able to solve to problem by myself. While looking into the SuSE support
data base for a completly different problem, I passed by the following entry:<br>
<blockquote><a class="moz-txt-link-freetext" href="http://sdb.suse.de/de/sdb/html/kdevelop_autoconf_73.html">http://sdb.suse.de/de/sdb/html/kdevelop_autoconf_73.html</a><br>
  </blockquote>
The suggested solution in this entry solved my problem. You may close the
bug report using this information.<br>
  <br>
Best regards<br>
Wolfgang<br>
  <br>
Marc Mutz wrote:<br>
  <blockquote type="cite" cite="mid:200202141029.01112 at sendmail.mutz.com">
    <pre wrap="">-----BEGIN PGP SIGNED MESSAGE-----<br>Hash: SHA1<br><br>On Thursday 14 February 2002 09:22, you wrote:<br></pre>
    <blockquote type="cite">
      <pre wrap="">Dear Stephan,<br><br>the attached reply has nothing to do with my initial bug report. I<br>have a bug with kdevelop and not kmail, pgp or whatever. According<br>to:<br></pre>
      </blockquote>
      <pre wrap=""><!----><snip><br><br>I've used the wrong number, sorry. But I have already reopened your bug <br>report the next day... So if you have had a closer look at the bug <br>summary, you would have noticed this ;-)<br><br>Marc<br><br>- -- <br>Marc Mutz <a class="moz-txt-link-rfc2396E" href="mailto:mutz at kde.org"><mutz at kde.org></a><br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v1.0.6 (GNU/Linux)<br>Comment: For info see <a class="moz-txt-link-freetext" href="http://www.gnupg.org">http://www.gnupg.org</a><br><br>iD8DBQE8a4Nb3oWD+L2/6DgRArLSAKCIThik8EKAF3gGYebYpFILl8aCgACbB9D4<br>9XsT0ipB5OapQe5ESnaMzPc=<br>=jIDb<br>-----END PGP SIGNATURE-----<br><br><br></pre>
      </blockquote>
      <br>
      </body>
      </html>

--------------Boundary-00=_CY6JIL2RCQ9LZQBTLKIV--

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; 8 Feb 2002 12:29:22 +0000
Received: (qmail 18909 invoked by uid 33); 8 Feb 2002 12:29:22 -0000
Date: 8 Feb 2002 12:29:22 -0000
Message-ID: <20020208122922.18908.qmail at mail.kde.org>
To: submit at bugs.kde.org
Subject: Create new C++ project in kdevelop
From: Wolfgang.Balzer at dlr.de

Package:           kdevelop
Version:           2.0.2 (using KDE 2.2.1 )
Severity:          normal
Installed from:    SuSE
Compiler:          gcc version 2.95.3 20010315 (SuSE)
OS:                Linux (i686) release 2.4.10-SMP
OS/Compiler notes: 

Dear KDE-developers,

when creating a new C++ project in kdevelop the autoconf/automake step generates the following messages:

cat acinclude.m4.in libtool.m4.in >acinclude.m4
aclocal
autoheader
./aclocal.m4:2181: error: m4_defn: undefined macro: _m4_divert_diversion
acfunctions.m4:1108: AM_FUNC_OBSTACK is expanded from...
./aclocal.m4:2181: the top level
autoconf: tracing failed
gmake: *** [all] Error 1
*** fehlgeschlagen ***

The creation of KDE2 application framework works perfectly, but I want to use kdevelop for the development of a general C++ program.

Best regards
Wolfgang

(Submitted via bugs.kde.org)
(Called from KBugReport dialog)