Mailing List Archive: Gentoo: User

Dovecot 2.1.3 fails to compile

Index | Next | Previous | View Threaded

tanstaafl at libertytrek

Mar 21, 2012, 5:38 AM

Post #1 of 7 (257 views)
Permalink

Dovecot 2.1.3 fails to compile

With this error:

In file included from /usr/include/CLucene/StdHeader.h:20:0,
from /usr/include/CLucene.h:11,
from lucene-wrapper.cc:23:
/usr/include/CLucene/SharedHeader.h:18:36: fatal error:
CLucene/clucene-config.h: No such file or directory
compilation terminated.
make[4]: *** [lucene-wrapper.lo] Error 1
make[4]: *** Waiting for unfinished jobs....
make[4]: Leaving directory
`/var/tmp/portage/net-mail/dovecot-2.1.3/work/dovecot-2.1.3/src/plugins/fts-lucene'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/var/tmp/portage/net-mail/dovecot-2.1.3/work/dovecot-2.1.3/src/plugins'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/var/tmp/portage/net-mail/dovecot-2.1.3/work/dovecot-2.1.3/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/var/tmp/portage/net-mail/dovecot-2.1.3/work/dovecot-2.1.3'
make: *** [all] Error 2
* ERROR: net-mail/dovecot-2.1.3 failed (compile phase):
* emake failed

Any ideas?

alan.mckinnon at gmail

Mar 21, 2012, 7:23 AM

Post #2 of 7 (238 views)
Permalink

Re: Dovecot 2.1.3 fails to compile [In reply to]

On Wed, 21 Mar 2012 08:38:42 -0400
Tanstaafl <tanstaafl [at] libertytrek> wrote:

> With this error:
>
> In file included from /usr/include/CLucene/StdHeader.h:20:0,
> from /usr/include/CLucene.h:11,
> from lucene-wrapper.cc:23:
> /usr/include/CLucene/SharedHeader.h:18:36: fatal error:
> CLucene/clucene-config.h: No such file or directory
> compilation terminated.
> make[4]: *** [lucene-wrapper.lo] Error 1
> make[4]: *** Waiting for unfinished jobs....
> make[4]: Leaving directory
> `/var/tmp/portage/net-mail/dovecot-2.1.3/work/dovecot-2.1.3/src/plugins/fts-lucene'
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory
> `/var/tmp/portage/net-mail/dovecot-2.1.3/work/dovecot-2.1.3/src/plugins'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory
> `/var/tmp/portage/net-mail/dovecot-2.1.3/work/dovecot-2.1.3/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory
> `/var/tmp/portage/net-mail/dovecot-2.1.3/work/dovecot-2.1.3'
> make: *** [all] Error 2
> * ERROR: net-mail/dovecot-2.1.3 failed (compile phase):
> * emake failed
>
> Any ideas?
>

Do you have dev-cpp/clucene installed? That missing header come from
there.

Dovecot does depend on (lucene ? >=dev-cpp/clucene-2.3) so you should
have it, I reckon I'd just remerge clucene then dovecot

--
Alan McKinnnon
alan.mckinnon [at] gmail

tanstaafl at libertytrek

Mar 21, 2012, 7:56 AM

Post #3 of 7 (232 views)
Permalink

Re: Dovecot 2.1.3 fails to compile [In reply to]

On 2012-03-21 10:23 AM, Alan McKinnon <alan.mckinnon [at] gmail> wrote:
> On Wed, 21 Mar 2012 08:38:42 -0400 Tanstaafl wrote:
> Do you have dev-cpp/clucene installed? That missing header come from
> there.

Of course (I have the lucene USE flag set for dovecot):

myhst : Wed Mar 21, 08:01:06 : ~
# equery list -p clucene
* Searching for clucene ...
[-P-] [ ] dev-cpp/clucene-0.9.21b-r1:1
[IP-] [ ] dev-cpp/clucene-2.3.3.4-r2:1
myhost : Wed Mar 21, 10:52:49 : ~
#

> Dovecot does depend on (lucene ?>=dev-cpp/clucene-2.3) so you should
> have it, I reckon I'd just remerge clucene then dovecot

When I tried updating dovecot, it *successfully* emerged the clucene
update first (it was already installed), then the dovecot build failed
with the error...

alan.mckinnon at gmail

Mar 21, 2012, 8:53 AM

Post #4 of 7 (237 views)
Permalink

Re: Dovecot 2.1.3 fails to compile [In reply to]

On Wed, 21 Mar 2012 10:56:37 -0400
Tanstaafl <tanstaafl [at] libertytrek> wrote:

> On 2012-03-21 10:23 AM, Alan McKinnon <alan.mckinnon [at] gmail> wrote:
> > On Wed, 21 Mar 2012 08:38:42 -0400 Tanstaafl wrote:
> > Do you have dev-cpp/clucene installed? That missing header come from
> > there.
>
> Of course (I have the lucene USE flag set for dovecot):
>
> myhst : Wed Mar 21, 08:01:06 : ~
> # equery list -p clucene
> * Searching for clucene ...
> [-P-] [ ] dev-cpp/clucene-0.9.21b-r1:1
> [IP-] [ ] dev-cpp/clucene-2.3.3.4-r2:1
> myhost : Wed Mar 21, 10:52:49 : ~
> #
>
> > Dovecot does depend on (lucene ?>=dev-cpp/clucene-2.3) so you should
> > have it, I reckon I'd just remerge clucene then dovecot
>
> When I tried updating dovecot, it *successfully* emerged the clucene
> update first (it was already installed), then the dovecot build
> failed with the error...
>

I see this end emerge world wants to update both packages here. I'll
let them do their thing and see if I get the same results as you (might
take a short while as there's a libreoffice update in the mix too...)

--
Alan McKinnnon
alan.mckinnon [at] gmail

alan.mckinnon at gmail

Mar 21, 2012, 9:09 AM

Post #5 of 7 (234 views)
Permalink

Re: Dovecot 2.1.3 fails to compile [In reply to]

On Wed, 21 Mar 2012 10:56:37 -0400
Tanstaafl <tanstaafl [at] libertytrek> wrote:

> On 2012-03-21 10:23 AM, Alan McKinnon <alan.mckinnon [at] gmail> wrote:
> > On Wed, 21 Mar 2012 08:38:42 -0400 Tanstaafl wrote:
> > Do you have dev-cpp/clucene installed? That missing header come from
> > there.
>
> Of course (I have the lucene USE flag set for dovecot):
>
> myhst : Wed Mar 21, 08:01:06 : ~
> # equery list -p clucene
> * Searching for clucene ...
> [-P-] [ ] dev-cpp/clucene-0.9.21b-r1:1
> [IP-] [ ] dev-cpp/clucene-2.3.3.4-r2:1
> myhost : Wed Mar 21, 10:52:49 : ~
> #
>
> > Dovecot does depend on (lucene ?>=dev-cpp/clucene-2.3) so you should
> > have it, I reckon I'd just remerge clucene then dovecot
>
> When I tried updating dovecot, it *successfully* emerged the clucene
> update first (it was already installed), then the dovecot build
> failed with the error...
>

It's quite simple as it turns out. dev-cpp/clucene changed the name of

/usr/include/CLucene/clucene-config.h

to

/usr/include/CLucene/CLConfig.h

As a quick nasty test I made a symlink, but that produced a gigantic
amount of build errors later on.

I reckon you should file a bug and meanwhile downgrade&mask clucene

--
Alan McKinnnon
alan.mckinnon [at] gmail

tanstaafl at libertytrek

Mar 21, 2012, 10:32 AM

Post #6 of 7 (235 views)
Permalink

Re: Dovecot 2.1.3 fails to compile [In reply to]

On 2012-03-21 12:09 PM, Alan McKinnon <alan.mckinnon [at] gmail> wrote:
> On Wed, 21 Mar 2012 10:56:37 -0400 Tanstaafl wrote:
>> When I tried updating dovecot, it *successfully* emerged the clucene
>> update first (it was already installed), then the dovecot build
>> failed with the error...

> It's quite simple as it turns out. dev-cpp/clucene changed the name of
>
> /usr/include/CLucene/clucene-config.h
>
> to
>
> /usr/include/CLucene/CLConfig.h
>
> As a quick nasty test I made a symlink, but that produced a gigantic
> amount of build errors later on.
>
> I reckon you should file a bug and meanwhile downgrade&mask clucene

Done: https://bugs.gentoo.org/show_bug.cgi?id=409205

Thanks! But I reckon if I'd have looked more closely, I could have
figured that one out for myself - guess I'm just too used to *not* being
able to figure these out myself... ;)

alan.mckinnon at gmail

Mar 21, 2012, 1:27 PM

Post #7 of 7 (233 views)
Permalink

Re: Dovecot 2.1.3 fails to compile [In reply to]

On Wed, 21 Mar 2012 13:32:30 -0400
Tanstaafl <tanstaafl [at] libertytrek> wrote:

> On 2012-03-21 12:09 PM, Alan McKinnon <alan.mckinnon [at] gmail> wrote:
> > On Wed, 21 Mar 2012 10:56:37 -0400 Tanstaafl wrote:
> >> When I tried updating dovecot, it *successfully* emerged the
> >> clucene update first (it was already installed), then the dovecot
> >> build failed with the error...
>
> > It's quite simple as it turns out. dev-cpp/clucene changed the name
> > of
> >
> > /usr/include/CLucene/clucene-config.h
> >
> > to
> >
> > /usr/include/CLucene/CLConfig.h
> >
> > As a quick nasty test I made a symlink, but that produced a gigantic
> > amount of build errors later on.
> >
> > I reckon you should file a bug and meanwhile downgrade&mask clucene
>
> Done: https://bugs.gentoo.org/show_bug.cgi?id=409205
>
> Thanks! But I reckon if I'd have looked more closely, I could have
> figured that one out for myself - guess I'm just too used to *not*
> being able to figure these out myself... ;)
>

No worries :-)

But lets be honest, when you are faced with a zillion lines of gcc
output and an error buried in there somewhere, it's not exactly a walk
in the park to see what is going wrong.

Today I just got lucky and just happened to see the right thing at the
right time.

--
Alan McKinnnon
alan.mckinnon [at] gmail

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads