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 22:27:20 +0200 [thread overview]
Message-ID: <20120321222720.0c65e696@khamul.example.com> (raw)
In-Reply-To: <4F6A10AE.40606@libertytrek.org>
On Wed, 21 Mar 2012 13:32:30 -0400
Tanstaafl <tanstaafl@libertytrek.org> wrote:
> On 2012-03-21 12:09 PM, Alan McKinnon <alan.mckinnon@gmail.com> 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@gmail.com
prev parent reply other threads:[~2012-03-21 20:29 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
2012-03-21 17:32 ` Tanstaafl
2012-03-21 20:27 ` Alan McKinnon [this message]
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=20120321222720.0c65e696@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