Re: [gentoo-user] Update to dev-libs/icu-51.1 results in borked Dolphin
On Sunday 28 Apr 2013 22:29:27 Alan McKinnon wrote: > On 28/04/2013 23:25, Alan McKinnon wrote: > > On 28/04/2013 22:23, Mick wrote: > >> On Sunday 28 Apr 2013 17:44:25 Alan McKinnon wrote: > >> > >> > >> Then tried to run update world again to update icu to the latest stable > >> version 51.1. It fails straight away: > >> > >> What does this error about autotools mean? > > > > flameeyes, who knows more about this stuff than both of us together, has > > this to say in the thread about tar: > > > > > > "yeah, thanks to some automake update someone did not think about testing > > first before unmasking, a whole bunch of packages are suddenly failing > > with that error. Nothing to see, but versionitis once again hitting a > > couple of innocents. Just go to bugzilla and see the bugs for the last > > 24h. It is a massacre." > > > > > > At some point in your near future and re-sync and remerge will fix all > > your problems. Meanwhile, sit tight and I recommend you do not updates > > until emerge worls tells you there's something for auto* > > Ignore this, it's a change to autotools.eclass so you won't see it in > emerge's list of updates to perform > > https://bugs.gentoo.org/show_bug.cgi?id=467772 Thanks for letting me know. I'll rinse and repeat at a later point. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Update to dev-libs/icu-51.1 results in borked Dolphin
On 28/04/2013 23:25, Alan McKinnon wrote: > On 28/04/2013 22:23, Mick wrote: >> On Sunday 28 Apr 2013 17:44:25 Alan McKinnon wrote: >> Then tried to run update world again to update icu to the latest stable >> version 51.1. It fails straight away: >> >> What does this error about autotools mean? > > > > flameeyes, who knows more about this stuff than both of us together, has > this to say in the thread about tar: > > > "yeah, thanks to some automake update someone did not think about testing > first before unmasking, a whole bunch of packages are suddenly failing > with that error. Nothing to see, but versionitis once again hitting a > couple of innocents. Just go to bugzilla and see the bugs for the last > 24h. It is a massacre." > > > At some point in your near future and re-sync and remerge will fix all > your problems. Meanwhile, sit tight and I recommend you do not updates > until emerge worls tells you there's something for auto* Ignore this, it's a change to autotools.eclass so you won't see it in emerge's list of updates to perform https://bugs.gentoo.org/show_bug.cgi?id=467772 -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] Update to dev-libs/icu-51.1 results in borked Dolphin
On 28/04/2013 22:23, Mick wrote:
> On Sunday 28 Apr 2013 17:44:25 Alan McKinnon wrote:
>> On 28/04/2013 17:46, Mick wrote:
>>> On Sunday 28 Apr 2013 14:50:58 Mick wrote:
On Sunday 28 Apr 2013 13:21:35 Marc Joliet wrote:
> I have to admit, I'm a bit confused. I was going to suggest rebuilding
> QtWebKit, because of the undefined references and other warnings above,
> but I didn't rebuild it myself after upgrading icu, and various KDE
> software I have (that depends on QtWebKit, for example k3b and various
> games) still runs fine.
>
> I would try rebuilding QtWebKit anyway, though.
>>>
>>> That's fixed it. Thanks!
>>>
>>> Does this mean that the new *default* for make.conf should be that
>>> preserve- libs is included in FEATURES, otherwise packages that depend
>>> on older lib files break if older files are removed?
>>
>> I dunno what the default is, but I've used preserve-libs since forever.
>>
>> Not having it doesn't give you less than what you used to have - apps
>> that link to libs which get upgraded always used to break, hence why we
>> had revdep-rebuild. And far years we just dealt with this breakage.
>>
>> preserve-libs just delays the delete of the old lib till the point where
>> nothing uses it anymore.
>
> :-(
>
> This is getting worse!
>
> I downgraded dev-libs/icu to 49.1.2. Then I run @preserve-rebuild and it did
> rebuild a bunch of packages. Everything works fine.
>
> Then tried to run update world again to update icu to the latest stable
> version 51.1. It fails straight away:
>
> What does this error about autotools mean?
flameeyes, who knows more about this stuff than both of us together, has
this to say in the thread about tar:
"yeah, thanks to some automake update someone did not think about testing
first before unmasking, a whole bunch of packages are suddenly failing
with that error. Nothing to see, but versionitis once again hitting a
couple of innocents. Just go to bugzilla and see the bugs for the last
24h. It is a massacre."
At some point in your near future and re-sync and remerge will fix all
your problems. Meanwhile, sit tight and I recommend you do not updates
until emerge worls tells you there's something for auto*
>
> ===
Emerging (1 of 7) dev-libs/icu-51.1
> * icu4c-51_1-src.tgz SHA256 SHA512 WHIRLPOOL size ;-) ... [
> ok ]
Unpacking source...
Unpacking icu4c-51_1-src.tgz to /var/tmp/portage/dev-libs/icu-51.1/work
Source unpacked in /var/tmp/portage/dev-libs/icu-51.1/work
Preparing source in /var/tmp/portage/dev-libs/icu-51.1/work/icu/source ...
> * Applying icu-4.8.1-fix_binformat_fonts.patch ...[
> ok ]
> * Applying icu-4.8.1.1-fix_ltr.patch ... [
> ok ]
> * Running eautoreconf in
> '/var/tmp/portage/dev-libs/icu-51.1/work/icu/source'
> ...
> * Running autoconf ...[
> ok ]
> * ERROR: dev-libs/icu-51.1 failed (prepare phase):
> * internal error: add AC_CONFIG_HEADER to ALL_AUTOTOOLS_MACROS
> *
> * Call stack:
> * ebuild.sh, line 93: Called src_prepare
> * environment, line 2975: Called eautoreconf
> * environment, line 907: Called eautoheader
> * environment, line 829: Called _at_uses_autoheader
> * environment, line 277: Called _at_uses_pkg 'AC_CONFIG_HEADERS'
> 'AC_CONFIG_HEADER' 'AM_CONFIG_HEADERS' 'AM_CONFIG_HEADER'
> * environment, line 309: Called autotools_check_macro
> 'AC_CONFIG_HEADERS'
> 'AC_CONFIG_HEADER' 'AM_CONFIG_HEADERS' 'AM_CONFIG_HEADER'
> * environment, line 484: Called die
> * The specific snippet of code:
> * has ${macro} ${ALL_AUTOTOOLS_MACROS[@]} || die "internal error:
> add ${macro} to ALL_AUTOTOOLS_MACROS";
> *
> * If you need support, post the output of `emerge --info '=dev-
> libs/icu-51.1'`,
> * the complete build log and the output of `emerge -pqv '=dev-
> libs/icu-51.1'`.
> /usr/lib64/portage/bin/isolated-functions.sh: line 215: wait: `internal
> error:
> add AC_CONFIG_HEADER to ALL_AUTOTOOLS_MACROS': not a pid or valid job spec
> * The complete build log is located at '/var/log/portage/dev-
> libs:icu-51.1:20130428-201855.log'.
> * The ebuild environment file is located at '/var/tmp/portage/dev-
> libs/icu-51.1/temp/environment'.
> * Working directory: '/var/tmp/portage/dev-libs/icu-51.1/work/icu/source'
> * S: '/var/tmp/portage/dev-libs/icu-51.1/work/icu/source'
>
Failed to emerge dev-libs/icu-51.1, Log file:
>
'/var/log/portage/dev-libs:icu-51.1:20130428-201855.log'
>
> * Messages for package dev-libs/icu-51.1:
>
> * ERROR: dev-libs/icu-51.1 failed (prepare phase):
> * internal error: add AC_CONFIG_HEADER to ALL_AUTOTOOLS_MACROS
> *
> * Call stack:
> * ebuild.sh, line 93: Called src_prepare
> * environment, line 2975: Called eautoreconf
> * environment, line 907:
Re: [gentoo-user] Update to dev-libs/icu-51.1 results in borked Dolphin
On 4/28/2013 16:23, Mick wrote:
> On Sunday 28 Apr 2013 17:44:25 Alan McKinnon wrote:
>> On 28/04/2013 17:46, Mick wrote:
>>> On Sunday 28 Apr 2013 14:50:58 Mick wrote:
On Sunday 28 Apr 2013 13:21:35 Marc Joliet wrote:
> I have to admit, I'm a bit confused. I was going to suggest
> rebuilding QtWebKit, because of the undefined references
> and other warnings above, but I didn't rebuild it myself
> after upgrading icu, and various KDE software I have (that
> depends on QtWebKit, for example k3b and various games)
> still runs fine.
>
> I would try rebuilding QtWebKit anyway, though.
>>>
>>> That's fixed it. Thanks!
>>>
>>> Does this mean that the new *default* for make.conf should be
>>> that preserve- libs is included in FEATURES, otherwise packages
>>> that depend on older lib files break if older files are
>>> removed?
>>
>> I dunno what the default is, but I've used preserve-libs since
>> forever.
>>
>> Not having it doesn't give you less than what you used to have -
>> apps that link to libs which get upgraded always used to break,
>> hence why we had revdep-rebuild. And far years we just dealt with
>> this breakage.
>>
>> preserve-libs just delays the delete of the old lib till the
>> point where nothing uses it anymore.
>
> :-(
>
> This is getting worse!
>
> I downgraded dev-libs/icu to 49.1.2. Then I run @preserve-rebuild
> and it did rebuild a bunch of packages. Everything works fine.
>
> Then tried to run update world again to update icu to the latest
> stable version 51.1. It fails straight away:
>
> What does this error about autotools mean?
>
> ===
Emerging (1 of 7) dev-libs/icu-51.1
> * icu4c-51_1-src.tgz SHA256 SHA512 WHIRLPOOL size ;-) ...
> [ ok ]
Unpacking source... Unpacking icu4c-51_1-src.tgz to
/var/tmp/portage/dev-libs/icu-51.1/work Source unpacked in
/var/tmp/portage/dev-libs/icu-51.1/work Preparing source in
/var/tmp/portage/dev-libs/icu-51.1/work/icu/source ...
> * Applying icu-4.8.1-fix_binformat_fonts.patch ...
> [ ok ] * Applying icu-4.8.1.1-fix_ltr.patch ...
> [ ok ] * Running eautoreconf in
> '/var/tmp/portage/dev-libs/icu-51.1/work/icu/source' ... * Running
> autoconf ...[
> ok ] * ERROR: dev-libs/icu-51.1 failed (prepare phase): *
> internal error: add AC_CONFIG_HEADER to ALL_AUTOTOOLS_MACROS * *
> Call stack: * ebuild.sh, line 93: Called src_prepare *
> environment, line 2975: Called eautoreconf * environment, line
> 907: Called eautoheader * environment, line 829: Called
> _at_uses_autoheader * environment, line 277: Called
> _at_uses_pkg 'AC_CONFIG_HEADERS' 'AC_CONFIG_HEADER'
> 'AM_CONFIG_HEADERS' 'AM_CONFIG_HEADER' * environment, line 309:
> Called autotools_check_macro 'AC_CONFIG_HEADERS' 'AC_CONFIG_HEADER'
> 'AM_CONFIG_HEADERS' 'AM_CONFIG_HEADER' * environment, line 484:
> Called die * The specific snippet of code: * has ${macro}
> ${ALL_AUTOTOOLS_MACROS[@]} || die "internal error: add ${macro} to
> ALL_AUTOTOOLS_MACROS"; * * If you need support, post the output of
> `emerge --info '=dev- libs/icu-51.1'`, * the complete build log and
> the output of `emerge -pqv '=dev- libs/icu-51.1'`.
> /usr/lib64/portage/bin/isolated-functions.sh: line 215: wait:
> `internal error: add AC_CONFIG_HEADER to ALL_AUTOTOOLS_MACROS': not
> a pid or valid job spec * The complete build log is located at
> '/var/log/portage/dev- libs:icu-51.1:20130428-201855.log'. * The
> ebuild environment file is located at '/var/tmp/portage/dev-
> libs/icu-51.1/temp/environment'. * Working directory:
> '/var/tmp/portage/dev-libs/icu-51.1/work/icu/source' * S:
> '/var/tmp/portage/dev-libs/icu-51.1/work/icu/source'
>
Failed to emerge dev-libs/icu-51.1, Log file:
>
'/var/log/portage/dev-libs:icu-51.1:20130428-201855.log'
>
> * Messages for package dev-libs/icu-51.1:
>
> * ERROR: dev-libs/icu-51.1 failed (prepare phase): * internal
> error: add AC_CONFIG_HEADER to ALL_AUTOTOOLS_MACROS * * Call
> stack: * ebuild.sh, line 93: Called src_prepare *
> environment, line 2975: Called eautoreconf * environment, line
> 907: Called eautoheader * environment, line 829: Called
> _at_uses_autoheader * environment, line 277: Called
> _at_uses_pkg 'AC_CONFIG_HEADERS' 'AC_CONFIG_HEADER'
> 'AM_CONFIG_HEADERS' 'AM_CONFIG_HEADER' * environment, line 309:
> Called autotools_check_macro 'AC_CONFIG_HEADERS' 'AC_CONFIG_HEADER'
> 'AM_CONFIG_HEADERS' 'AM_CONFIG_HEADER' * environment, line 484:
> Called die * The specific snippet of code: * has ${macro}
> ${ALL_AUTOTOOLS_MACROS[@]} || die "internal error: add ${macro} to
> ALL_AUTOTOOLS_MACROS"; *
> ===
>
> Is this a result of me adding preserve-libs without changing
> something in my env? :-/
>
No - see bug - https://bugs.gentoo.org/show_bug.cgi?id=467772
Bunch of package
Re: [gentoo-user] Update to dev-libs/icu-51.1 results in borked Dolphin
On Sunday 28 Apr 2013 17:44:25 Alan McKinnon wrote:
> On 28/04/2013 17:46, Mick wrote:
> > On Sunday 28 Apr 2013 14:50:58 Mick wrote:
> >> On Sunday 28 Apr 2013 13:21:35 Marc Joliet wrote:
> >>> I have to admit, I'm a bit confused. I was going to suggest rebuilding
> >>> QtWebKit, because of the undefined references and other warnings above,
> >>> but I didn't rebuild it myself after upgrading icu, and various KDE
> >>> software I have (that depends on QtWebKit, for example k3b and various
> >>> games) still runs fine.
> >>>
> >>> I would try rebuilding QtWebKit anyway, though.
> >
> > That's fixed it. Thanks!
> >
> > Does this mean that the new *default* for make.conf should be that
> > preserve- libs is included in FEATURES, otherwise packages that depend
> > on older lib files break if older files are removed?
>
> I dunno what the default is, but I've used preserve-libs since forever.
>
> Not having it doesn't give you less than what you used to have - apps
> that link to libs which get upgraded always used to break, hence why we
> had revdep-rebuild. And far years we just dealt with this breakage.
>
> preserve-libs just delays the delete of the old lib till the point where
> nothing uses it anymore.
:-(
This is getting worse!
I downgraded dev-libs/icu to 49.1.2. Then I run @preserve-rebuild and it did
rebuild a bunch of packages. Everything works fine.
Then tried to run update world again to update icu to the latest stable
version 51.1. It fails straight away:
What does this error about autotools mean?
===
>>> Emerging (1 of 7) dev-libs/icu-51.1
* icu4c-51_1-src.tgz SHA256 SHA512 WHIRLPOOL size ;-) ... [
ok ]
>>> Unpacking source...
>>> Unpacking icu4c-51_1-src.tgz to /var/tmp/portage/dev-libs/icu-51.1/work
>>> Source unpacked in /var/tmp/portage/dev-libs/icu-51.1/work
>>> Preparing source in /var/tmp/portage/dev-libs/icu-51.1/work/icu/source ...
* Applying icu-4.8.1-fix_binformat_fonts.patch ...[
ok ]
* Applying icu-4.8.1.1-fix_ltr.patch ... [
ok ]
* Running eautoreconf in '/var/tmp/portage/dev-libs/icu-51.1/work/icu/source'
...
* Running autoconf ...[
ok ]
* ERROR: dev-libs/icu-51.1 failed (prepare phase):
* internal error: add AC_CONFIG_HEADER to ALL_AUTOTOOLS_MACROS
*
* Call stack:
* ebuild.sh, line 93: Called src_prepare
* environment, line 2975: Called eautoreconf
* environment, line 907: Called eautoheader
* environment, line 829: Called _at_uses_autoheader
* environment, line 277: Called _at_uses_pkg 'AC_CONFIG_HEADERS'
'AC_CONFIG_HEADER' 'AM_CONFIG_HEADERS' 'AM_CONFIG_HEADER'
* environment, line 309: Called autotools_check_macro 'AC_CONFIG_HEADERS'
'AC_CONFIG_HEADER' 'AM_CONFIG_HEADERS' 'AM_CONFIG_HEADER'
* environment, line 484: Called die
* The specific snippet of code:
* has ${macro} ${ALL_AUTOTOOLS_MACROS[@]} || die "internal error:
add ${macro} to ALL_AUTOTOOLS_MACROS";
*
* If you need support, post the output of `emerge --info '=dev-
libs/icu-51.1'`,
* the complete build log and the output of `emerge -pqv '=dev-
libs/icu-51.1'`.
/usr/lib64/portage/bin/isolated-functions.sh: line 215: wait: `internal error:
add AC_CONFIG_HEADER to ALL_AUTOTOOLS_MACROS': not a pid or valid job spec
* The complete build log is located at '/var/log/portage/dev-
libs:icu-51.1:20130428-201855.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-
libs/icu-51.1/temp/environment'.
* Working directory: '/var/tmp/portage/dev-libs/icu-51.1/work/icu/source'
* S: '/var/tmp/portage/dev-libs/icu-51.1/work/icu/source'
>>> Failed to emerge dev-libs/icu-51.1, Log file:
>>> '/var/log/portage/dev-libs:icu-51.1:20130428-201855.log'
* Messages for package dev-libs/icu-51.1:
* ERROR: dev-libs/icu-51.1 failed (prepare phase):
* internal error: add AC_CONFIG_HEADER to ALL_AUTOTOOLS_MACROS
*
* Call stack:
* ebuild.sh, line 93: Called src_prepare
* environment, line 2975: Called eautoreconf
* environment, line 907: Called eautoheader
* environment, line 829: Called _at_uses_autoheader
* environment, line 277: Called _at_uses_pkg 'AC_CONFIG_HEADERS'
'AC_CONFIG_HEADER' 'AM_CONFIG_HEADERS' 'AM_CONFIG_HEADER'
* environment, line 309: Called autotools_check_macro 'AC_CONFIG_HEADERS'
'AC_CONFIG_HEADER' 'AM_CONFIG_HEADERS' 'AM_CONFIG_HEADER'
* environment, line 484: Called die
* The specific snippet of code:
* has ${macro} ${ALL_AUTOTOOLS_MACROS[@]} || die "internal error:
add ${macro} to ALL_AUTOTOOLS_MACROS";
*
===
Is this a result of me adding preserve-libs without changing something in my
env? :-/
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] Update to dev-libs/icu-51.1 results in borked Dolphin
On 28/04/2013 17:46, Mick wrote: > On Sunday 28 Apr 2013 14:50:58 Mick wrote: >> On Sunday 28 Apr 2013 13:21:35 Marc Joliet wrote: >>> I have to admit, I'm a bit confused. I was going to suggest rebuilding >>> QtWebKit, because of the undefined references and other warnings above, >>> but I didn't rebuild it myself after upgrading icu, and various KDE >>> software I have (that depends on QtWebKit, for example k3b and various >>> games) still runs fine. >>> >>> I would try rebuilding QtWebKit anyway, though. > > That's fixed it. Thanks! > > Does this mean that the new *default* for make.conf should be that preserve- > libs is included in FEATURES, otherwise packages that depend on older lib > files break if older files are removed? > I dunno what the default is, but I've used preserve-libs since forever. Not having it doesn't give you less than what you used to have - apps that link to libs which get upgraded always used to break, hence why we had revdep-rebuild. And far years we just dealt with this breakage. preserve-libs just delays the delete of the old lib till the point where nothing uses it anymore. -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] Update to dev-libs/icu-51.1 results in borked Dolphin
On Sunday 28 Apr 2013 17:25:06 Neil Bothwick wrote: > On Sun, 28 Apr 2013 16:46:44 +0100, Mick wrote: > > Does this mean that the new *default* for make.conf should be that > > preserve- libs is included in FEATURES, otherwise packages that depend > > on older lib files break if older files are removed? > > That's certainly the default on testing portage. preserve-libs shows up > in emerge --info but is not set in make.cond. OK, it is not in stable as far as this box is concerned: # emerge --info | grep -i preserve # I added it now to my make.conf. I'll check on a second box in a minute to see if things are borked there too. I think until preserve-libs becomes default the older libs should not be removed and the previous approach of asking to run 'revdep-rebuilt --library && rm' should remain. Unless you advise otherwise I will post a bug when I get a minute. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Update to dev-libs/icu-51.1 results in borked Dolphin
On Sun, 28 Apr 2013 16:46:44 +0100, Mick wrote: > Does this mean that the new *default* for make.conf should be that > preserve- libs is included in FEATURES, otherwise packages that depend > on older lib files break if older files are removed? That's certainly the default on testing portage. preserve-libs shows up in emerge --info but is not set in make.cond. -- Neil Bothwick Press button to test: release to detonate. signature.asc Description: PGP signature
Re: [gentoo-user] Update to dev-libs/icu-51.1 results in borked Dolphin
On Sunday 28 Apr 2013 14:50:58 Mick wrote: > On Sunday 28 Apr 2013 13:21:35 Marc Joliet wrote: > > I have to admit, I'm a bit confused. I was going to suggest rebuilding > > QtWebKit, because of the undefined references and other warnings above, > > but I didn't rebuild it myself after upgrading icu, and various KDE > > software I have (that depends on QtWebKit, for example k3b and various > > games) still runs fine. > > > > I would try rebuilding QtWebKit anyway, though. That's fixed it. Thanks! Does this mean that the new *default* for make.conf should be that preserve- libs is included in FEATURES, otherwise packages that depend on older lib files break if older files are removed? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Update to dev-libs/icu-51.1 results in borked Dolphin
On Sunday 28 Apr 2013 13:21:35 Marc Joliet wrote: > I have to admit, I'm a bit confused. I was going to suggest rebuilding > QtWebKit, because of the undefined references and other warnings above, but > I didn't rebuild it myself after upgrading icu, and various KDE software I > have (that depends on QtWebKit, for example k3b and various games) still > runs fine. > > I would try rebuilding QtWebKit anyway, though. I'm going through rebuilding dev-qt/qtwebkit-4.8.4 as I write this. > For the future: assuming you are using stable portage, I would add > "preserve-libs" to FEATURES in make.conf. That way you don't lose old > libraries immediately after upgrades. For example, on my machine portage > gave me an informative message after upgrading world, after which "emerge > @preserved-rebuild" rebuilt (amongst others) webkit-gtk. webkit-gtk is not installed in this box. > I've been running with preserve-libs for several months now (not too long > after it came to stable portage) and it's been working fine for me so far. > I have needed "revdep-rebuild" much less since then. I haven't had any such problem so far, but I have now added "preserve-libs" in my FEATURES just in case. Thanks. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Update to dev-libs/icu-51.1 results in borked Dolphin
Am Sun, 28 Apr 2013 12:48:28 +0100 schrieb Mick : > Updating dev-libs/icu-51.1 uninstalled /usr/lib64/libicuuc.so.49.1.2 and when > I try to start Dolphin I get: > == > There was an error loading the module Dolphin View. > The diagnostics is: > Cannot load library /usr/lib64/kde4/dolphinpart.so: (libicuuc.so.49: cannot > open shared object file: No such file or directory) > == > > Should revdep-rebuild have picked this up, or would this only work if > /usr/lib64/libicuuc.so.49.1.2 had not been removed yet? > > Trying to rebuild dolphin gives: > == > [ 71%] Building CXX object dolphin/src/CMakeFiles/dolphin.dir/dolphin_dummy.o > cd /var/tmp/portage/kde- > base/dolphin-4.10.1/work/dolphin-4.10.1_build/dolphin/src && /usr/bin/x86_64- > pc-linux-gnu-g++ -D_BSD_SOURCE -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -DQT_NO_STL > -DQT_NO_CAST_TO_ASCII -D_REENTRANT -DKDE_DEPRECATED_WARNINGS - > DKDE4_CMAKE_TOPLEVEL_DIR_LENGTH=45 -DDISABLE_NEPOMUK_LEGACY - > DQT_USE_FAST_CONCATENATION -DQT_USE_FAST_OPERATOR_PLUS -DQT_NO_DEBUG > -DNDEBUG > -march=native -O2 -pipe -Wnon-virtual-dtor -Wno-long-long -Wundef -Wcast- > align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -fno- > exceptions -DQT_NO_EXCEPTIONS -fno-check-new -fno-common -Woverloaded-virtual > -fno-threadsafe-statics -fvisibility=hidden -fvisibility-inlines-hidden - > I/var/tmp/portage/kde- > base/dolphin-4.10.1/work/dolphin-4.10.1_build/dolphin/src - > I/var/tmp/portage/kde-base/dolphin-4.10.1/work/dolphin-4.10.1/dolphin/src - > I/var/tmp/portage/kde-base/dolphin-4.10.1/work/dolphin-4.10.1_build - > I/var/tmp/portage/kde-base/dolphin-4.10.1/work/dolphin-4.10.1/lib/konq - > I/usr/include/KDE -I/usr/include/qt4/QtXmlPatterns -I/usr/include/qt4/QtXml - > I/usr/include/qt4/QtWebKit -I/usr/include/qt4/QtUiTools - > I/usr/include/qt4/QtTest -I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtSql - > I/usr/include/qt4/QtScriptTools -I/usr/include/qt4/QtScript - > I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtNetwork - > I/usr/include/qt4/QtMultimedia -I/usr/include/qt4/QtDesigner - > I/usr/include/qt4/QtDeclarative -I/usr/include/qt4/QtDBus - > I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtGui - > I/usr/include/qt4/QtCore -I/usr/include/qt4/Qt - > I/usr/share/qt4/mkspecs/default -I/usr/include/qt4-D_GNU_SOURCE - > D_LARGEFILE64_SOURCE -o CMakeFiles/dolphin.dir/dolphin_dummy.o -c > /var/tmp/portage/kde- > base/dolphin-4.10.1/work/dolphin-4.10.1_build/dolphin/src/dolphin_dummy.cpp > Linking CXX executable dolphin > cd /var/tmp/portage/kde- > base/dolphin-4.10.1/work/dolphin-4.10.1_build/dolphin/src && /usr/bin/cmake > -E > cmake_link_script CMakeFiles/dolphin.dir/link.txt --verbose=1 > /usr/bin/x86_64-pc-linux-gnu-g++ -march=native -O2 -pipe > -Wnon-virtual-dtor > -Wno-long-long -Wundef -Wcast-align -Wchar-subscripts -Wall -W > -Wpointer-arith > -Wformat-security -fno-exceptions -DQT_NO_EXCEPTIONS -fno-check-new -fno- > common -Woverloaded-virtual -fno-threadsafe-statics -fvisibility=hidden - > fvisibility-inlines-hidden -Wl,--enable-new-dtags -Wl,-O1 -Wl,--as-needed > CMakeFiles/dolphin.dir/dolphin_dummy.o -o dolphin -rdynamic - > L/var/tmp/portage/kde-base/dolphin-4.10.1/work/dolphin-4.10.1_build/lib - > L/usr/lib64/qt4 ../../lib/libkdeinit4_dolphin.so -lkonq -lz -lX11 > ../../lib/libdolphinprivate.so.4.10.1 /usr/lib64/libkfile.so.4.10.1 > /usr/lib64/libkcmutils.so.4.10.1 /usr/lib64/libkparts.so.4.10.1 -lknewstuff3 - > lphonon /usr/lib64/libnepomukwidgets.so.4.10.1 > /usr/lib64/libnepomukcore.so.4.10.1 /usr/lib64/libkio.so.5.10.1 > /usr/lib64/libsolid.so.4.10.1 /usr/lib64/libnepomukutils.so.4.10.1 > /usr/lib64/qt4/libQtNetwork.so /usr/lib64/qt4/libQtXml.so > /usr/lib64/libnepomuk.so.4.10.1 /usr/lib64/libkdeui.so.5.10.1 > /usr/lib64/qt4/libQtGui.so /usr/lib64/qt4/libQtSvg.so -lsoprano > /usr/lib64/libkactivities.so.6.1.0 /usr/lib64/libkdecore.so.5.10.1 > /usr/lib64/qt4/libQtCore.so -lpthread /usr/lib64/qt4/libQtDBus.so -Wl,- > rpath,/var/tmp/portage/kde- > base/dolphin-4.10.1/work/dolphin-4.10.1_build/lib:/usr/lib64/qt4: > /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/../../../../x86_64-pc-linux-gnu/bin/ld: > > warning: libicuuc.so.49, needed by /usr/lib64/qt4/libQtWebKit.so.4, not found > (try using -rpath or -rpath-link) > /usr/lib64/qt4/libQtWebKit.so.4: undefined reference to `ubrk_isBoundary_49' > /usr/lib64/qt4/libQtWebKit.so.4: undefined reference to `ubrk_previous_49' > /usr/lib64/qt4/libQtWebKit.so.4: undefined reference to `ubrk_preceding_49' > /usr/lib64/qt4/libQtWebKit.so.4: undefined reference to `ubrk_openRules_49' > /usr/lib64/qt4/libQtWebKit.so.4: undefined reference to `ubrk_last_49' > /usr/lib64/qt4/libQtWebKit.so.4: undefined reference to `ubrk_first_49' > /usr/lib64/qt4/libQtWebKit.so.4: undefined reference to `ubrk_following_49' > /usr/lib64/qt4/libQtWebKit.so.4:
