You do an installation to /usr? Or why is /usr/bin/meinproc used?

Subject: Re:  kivio compile errors while compiling from konstruct

On Friday 12 Dec 2003 12:24, Stephan Binner wrote:
> You do an installation to /usr? Or why is /usr/bin/meinproc used?

I'm installing to the default location: ~/kde3.2beta2. I checked; there's no 
other meinproc. The Makefile has MEINPROC set to /usr/bin/meinproc.

You don't have by change a kdelibs configure or build output at hand describing why meinproc wasn't build?

Subject: Re:  kivio compile errors while compiling from konstruct

On Friday 12 Dec 2003 12:59, Stephan Binner wrote:
> You don't have by change a kdelibs configure or build output at hand
> describing why meinproc wasn't build?

no, sorry. but there's no meinproc in ~/kde3.2beta2/bin/meinproc.

My system is Mandrake 9.2.  I used Konstruct to install to ~/kde3.2-beta2.  Noted failure to install quanta_be (bleeding edge) from tarball and cvs.  Both had the same compile time problem: /usr/bin/meinproc was not finding /home/damon/archive/konstruct/konstruct/kde/kdelibs/work/kdelibs-3.1.94/kdoctools/customization/dtd/kdex.dtd

Relevant information:
$ locate meinproc
/home/damon/archive/konstruct/konstruct/kde/kdebase/work/kdebase-3.1.94/khelpcen ter/htmlsearch/meinproc_wrapper
/home/damon/archive/konstruct/konstruct/kde/kdelibs/work/kdelibs-3.1.94/kdoctool s/meinproc.cpp
/home/damon/archive/konstruct/konstruct/kde/kdelibs/work/kdelibs-3.1.94/kdoctool s/.deps/meinproc.Po
/home/damon/archive/konstruct/konstruct/kde/kdelibs/work/kdelibs-3.1.94/debian/m einproc.sgml
*** quanta sources
/home/damon/src/quanta_be/quanta/quanta/data/scripts/meinproc.kmdr
/home/damon/src/quanta-be-rel-01/quanta/data/scripts/meinproc.kmdr.info
/home/damon/src/quanta-be-rel-01/quanta/data/scripts/meinproc.info
/home/damon/src/quanta-be-rel-01/quanta/data/scripts/meinproc.kmdr
/usr/bin/meinproc

Thanks!
Damon

Created attachment 3690 [details]
bzip2 of config.log from konstruct/kde/kdelibs/work/kdelibs-3.1.94

As requested, relevant config.log attached.

> configure:40636: checking for present bzip2 support
> configure:40639: result: no - disabling doc compiler

You have no bzip2 (development headers) installed.

Subject: Re:  kivio compile errors while compiling from konstruct

On Sunday 14 Dec 2003 18:31, Stephan Binner wrote:
> > configure:40636: checking for present bzip2 support
> > configure:40639: result: no - disabling doc compiler
>
> You have no bzip2 (development headers) installed.

Can that be the cause of meinproc not being installed? In any case, shouldn't 
this be listed somewhere in the configure scripts?

Of course. And it's handled by the configure scripts, the documentation is not installed then. The problem of you both is that you have an older KDE with an older meinproc plus data files installed in a system-wide searched binary path.

Subject: Re:  kivio compile errors while compiling from konstruct

On Sunday 14 Dec 2003 18:54, Stephan Binner wrote:
> Of course. And it's handled by the configure scripts, the documentation is

I mean, configure should just bomb out if it didn't find it...

Thanks!  After installation of missing bzip2 header files, meinproc was sucessfully installed.

File a wish for "configure" to bomb out. :-)

Subject: Re:  kivio compile errors while compiling from konstruct

On Tuesday 16 Dec 2003 21:48, Stephan Binner wrote:
> File a wish for "configure" to bomb out. :-)

This would seem highly unprofessional. Why don't you forward the bug to the 
right place (in this case, the kivio guys)?

IMO, you shouldn't expect the users to know what to do each time. I first 
filed a bug with the kivio product, they asked me to file a bug with 
konstruct. Now, you're asking me to file a bug with kivio again. This is 
stupid and non-sensical. I would expect you to take the bug to its right 
place now... and let the appropriate devels know about this thing.

Is there now some place where to report these problems? I can't build Kopete for the same reason, ie. the configure script doesn't drop the doc building, instead it errors when compiling to the missing .dtd.

> This would seem highly unprofessional.

Then be unprofessional.

> Now, you're asking me to file a bug with kivio again.

I didn't, you can't read. As you didn't read Konstruct README's that links to the "KDE Compilation Requirements", which states that that bzip2 is required, and mentions that you have to install the development headers of the required libraries.

Subject: Re:  kivio compile errors while compiling from konstruct

On Wednesday 17 Dec 2003 12:36, Stephan Binner wrote:
> > This would seem highly unprofessional.
>
> Then be unprofessional.
>
> > Now, you're asking me to file a bug with kivio again.
>
> I didn't, you can't read. As you didn't read Konstruct README's that links
> to the "KDE Compilation Requirements", which states that that bzip2 is
> required, and mentions that you have to install the development headers of
> the required libraries.

... and that would mean this bug wouldn't have been found. I'm trying to help 
the project here, and you're asking me to read the docs which will mask out 
bugs. If some build-depend packages aren't installed, configure _should_ bomb 
out. Reading docs really is no alternative.

Anyways, I see you've reopened and reassigned the bug, that's a good sign.

It's not a bug per se. It's a deficiency of your system combined with an older KDE (including older meinproc + data) installed.

Subject: Re:  configure doesn't bomb out when bzip2 headers are missing

On Wednesday 17 Dec 2003 13:11, Stephan Binner wrote:
> It's not a bug per se. It's a deficiency of your system combined with an
> older KDE (including older meinproc + data) installed.

you mean configure not bailing out on failed dependencies is not a bug?

It disables the part (meinproc) that requires it, doesn't it?
And it doesn't build documentations if it doesn't find meinproc.

That it finds another incompatible meinproc, bad luck.

Related 70111 bug was closed (problem with construct) and this is a 5 years old bug, I think it can be considered closed