From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Evolution-Data-Server borked?
Date: Thu, 11 Aug 2011 12:23:55 +0000 (UTC) [thread overview]
Message-ID: <loom.20110811T141213-340@post.gmane.org> (raw)
Hello,
As part of a update @world,
kde(meta) was upgraded to kde 4.6.5
A large compile ran overnight
(using --skipfirst --resume) to
complete. In the AM today,
I rebooted and ran a
revdep-rebuild to check what needs
to be rebuilt.
during revdep (error-typical of many)
broken /usr/lib64/evolution-data-server-1.2/extensions/libecalbackendfile.so
(requires libicudata.so.46
broken /usr/lib64/libegroupwise-1.2.so.13.0.1 (requires libicudata.so.46
libicui18n.so.46
[ebuild R ] gnome-extra/evolution-data-server-2.32.2-r1
but it fails
upon rebuilding:
(just one of many .la file warnings)
ibtool: link: warning: `/usr/lib/libgio-2.0.la' seems to be moved
libtool: link: warning: `/usr/lib/libgobject-2.0.la' seems to be moved
libtool: link: warning: `/usr/lib/libgmodule-2.0.la' seems to be moved
<snip>
* ERROR: gnome-extra/evolution-data-server-2.32.2-r1 failed (compile phase):
* compile failure
*
* Call stack:
* ebuild.sh, line 56: Called src_compile
* environment, line 3852: Called gnome2_src_compile
* environment, line 2972: Called die
* The specific snippet of code:
* emake || die "compile failure"
Any ideas? I'll be offline for a few hours...
James
next reply other threads:[~2011-08-11 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 12:23 James [this message]
2011-08-11 13:03 ` [gentoo-user] Re: Evolution-Data-Server borked? James
2011-08-11 13:11 ` James
2011-08-12 19:41 ` walt
2011-08-13 4:30 ` James
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=loom.20110811T141213-340@post.gmane.org \
--to=wireless@tampabay.rr.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