Re: [gentoo-user] Update to dev-libs/icu-51.1 results in borked Dolphin

[Alan McKinnon]

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:  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?  :-/
>


-- 
Alan McKinnon
alan.mckinnon@×××××.com