public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Dovecot 2.1.3 fails to compile
Date: Wed, 21 Mar 2012 18:09:37 +0200	[thread overview]
Message-ID: <20120321180937.7caf53d8@khamul.example.com> (raw)
In-Reply-To: <4F69EC25.70006@libertytrek.org>

On Wed, 21 Mar 2012 10:56:37 -0400
Tanstaafl <tanstaafl@libertytrek.org> wrote:

> On 2012-03-21 10:23 AM, Alan McKinnon <alan.mckinnon@gmail.com> 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@gmail.com




  parent reply	other threads:[~2012-03-21 16:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-21 12:38 [gentoo-user] Dovecot 2.1.3 fails to compile Tanstaafl
2012-03-21 14:23 ` Alan McKinnon
2012-03-21 14:56   ` Tanstaafl
2012-03-21 15:53     ` Alan McKinnon
2012-03-21 16:09     ` Alan McKinnon [this message]
2012-03-21 17:32       ` Tanstaafl
2012-03-21 20:27         ` Alan McKinnon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120321180937.7caf53d8@khamul.example.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox