Re: [gentoo-user] Building media-libs/lcms-2.6-r1 failed

[Gevisz <gevisz@gmail.com>]

On Wed, 29 Oct 2014 13:19:54 -0600 Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Wed, Oct 29, 2014 at 1:10 PM, Gevisz <gevisz@gmail.com> wrote:
> > On Wed, 29 Oct 2014 19:25:20 +0200 Alexander Kapshuk <alexander.kapshuk@gmail.com> wrote:
> >
> >> On Wed, Oct 29, 2014 at 6:05 PM, Gevisz <gevisz@gmail.com> wrote:
> >> > After today's # emerge-webrsyc
> >> > # emerge --update --deep --with-bdeps=y --newuse --backtrack=90 --ask world
> >> > failed with the following message:
> >> >
> >> > These are the packages that would be merged, in order:
> >> >
> >> > Calculating dependencies... done!
> >> > [ebuild     U  ] media-libs/lcms-2.6-r1 [2.5] USE="threads%*" ABI_X86="(64%*) (-32) (-x32)"
> >> > [ebuild     U  ] net-misc/wget-1.16 [1.14]
> >> > [ebuild     U  ] media-gfx/imagemagick-6.8.9.9 [6.8.8.10-r1]
> >> >
> > <skipped>
> >> >
> >> > I think that something may be wrong with sys-devel/gcc-4.8.3 as my problems begun when
> >> > I have updated it from sys-devel/gcc-4.7.3-r1 this Monday. Namely, just after this only
> >> > update, # emerge @preserved-rebuild
> >> > failed to rebuild app-text/pdftk-1.44 that was not updated that time and built well with
> >> > sys-devel/gcc-4.7.3-r1. Then I recalled that to build app-text/pdftk I had to add gcj use
> >> > flag to sys-devel/gcc. So, as I am not fond of Java, I just unmerged app-text/pdftk.
> >> > Bu now it seems that I had to unmerge media-libs/lcms and all packages that depend on it.
> >> >
> >> > May be it would be easier to unmerge sys-devel/gcc-4.8.3 and return back to
> >> > sys-devel/gcc-4.7.3-r1 but I do not know how to do it properly.
> >> >
> >>
> >> Did you remember to run 'gcc-config -f 1' after updating gcc as root?
> >
> > No, I did not remember to run 'gcc-config -f 1' because I never knew that it should be done
> > and no portage message advised me to do so.  `man gcc' or `man gcc-config' also report that
> > there is no manual on these packets. Gentoo's Upgrading GCC wiki also says nothing about
> > this command...
> >
> >> What's the output of 'gcc-config -l'?
> >
> > # gcc-config -l
> >  * gcc-config: Active gcc profile is invalid!
> >
> >  [1] x86_64-pc-linux-gnu-4.8.3
> >
> > Nice!
> >
> > Ok, trying # gcc-config -f 1
> >  * Switching native-compiler to x86_64-pc-linux-gnu-4.8.3 ...
> >>>> Regenerating /etc/ld.so.cache...                                                                                                                            [ ok ]
> >
> >  * If you intend to use the gcc from the new profile in an already
> >  * running shell, please remember to do:
> >
> >  *   . /etc/profile
> >
> >
> > What exactly shall I remember to do?
> >
> > Ok, # gcc-config -l
> >  [1] x86_64-pc-linux-gnu-4.8.3 *
> >
> > Now # emerge --update --deep --with-bdeps=y --newuse --backtrack=90 --ask world
> > emerges all three above packages.
> >
> > Trying to emerge pdftk. Done.
> >
> > Ok. Thank you. But why there was no hint about it after updating gcc?
> >
> > Well, there was a reference to Gentoo's Upgrading GCC wiki
> > but nothing more...
> 
> From the toolchain eclass[1]:
> 
> # if we're installing a genuinely different compiler version,
> # we should probably tell the user -how- to switch to the new
> # gcc version, since we're not going to do it for him/her.
> # We don't want to switch from say gcc-3.3 to gcc-3.4 right in
> # the middle of an emerge operation (like an 'emerge -e world'
> # which could install multiple gcc versions).
> # Only warn if we're installing a pkg as we might be called from
> # the pkg_{pre,post}rm steps.  #446830
> if [[ ${EBUILD_PHASE} == *"inst" ]] ; then
>         einfo "The current gcc config appears valid, so it will not be"
>         einfo "automatically switched for you.  If you would like to"
>         einfo "switch to the newly installed gcc version, do the"
>         einfo "following:"
>         echo
>         einfo "gcc-config ${CTARGET}-${GCC_CONFIG_VER}"
>         einfo "source /etc/profile"
>         echo
> fi
> 
> This gets printed if you "genuinely" install a different compiler
> version. If it didn't, it is a bug and should be reported.

Thank you for replying to this thread.

I have just checked and found out that, after upgrading my gcc
from version gcc-4.7.3-r1 to version 4.8.3, I got the following
message: 

>>> Installing (1 of 1) sys-devel/gcc-4.8.3
 * The current gcc config appears valid, so it will not be
 * automatically switched for you.  If you would like to
 * switch to the newly installed gcc version, do the
 * following:

 * gcc-config x86_64-pc-linux-gnu-4.8.3
 * source /etc/profile

 * Switching native-compiler to x86_64-pc-linux-gnu-4.7.3 ...>>> Regenerating /etc/ld.so.cache...
 [ ok ]

 * If you have issues with packages unable to locate libstdc++.la,
 * then try running 'fix_libtool_files.sh' on the old gcc versions.

 * You might want to review the GCC upgrade guide when moving between
 * major versions (like 4.2 to 4.3):
 * http://www.gentoo.org/doc/en/gcc-upgrading.xml


 * Messages for package sys-devel/gcc-4.8.3:

 * If you have issues with packages unable to locate libstdc++.la,
 * then try running 'fix_libtool_files.sh' on the old gcc versions.
 * You might want to review the GCC upgrade guide when moving between
 * major versions (like 4.2 to 4.3):
 * http://www.gentoo.org/doc/en/gcc-upgrading.xml

But I noticed only the last part of it, starting from
* Messages for package sys-devel/gcc-4.8.3 line.

Well, probably I should be more attentive...
 
> Regards.
> 
> [1] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/eclass/toolchain.eclass?view=markup