Gentoo Archives: gentoo-user

From: Gevisz <gevisz@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Building media-libs/lcms-2.6-r1 failed
Date: Wed, 29 Oct 2014 19:51:27
Message-Id: 54514536.4a35700a.530b.ffff8545@mx.google.com
In Reply to: Re: [gentoo-user] Building media-libs/lcms-2.6-r1 failed by "Canek Peláez Valdés"
1 On Wed, 29 Oct 2014 13:19:54 -0600 Canek Peláez Valdés <caneko@×××××.com> wrote:
2
3 > On Wed, Oct 29, 2014 at 1:10 PM, Gevisz <gevisz@×××××.com> wrote:
4 > > On Wed, 29 Oct 2014 19:25:20 +0200 Alexander Kapshuk <alexander.kapshuk@×××××.com> wrote:
5 > >
6 > >> On Wed, Oct 29, 2014 at 6:05 PM, Gevisz <gevisz@×××××.com> wrote:
7 > >> > After today's # emerge-webrsyc
8 > >> > # emerge --update --deep --with-bdeps=y --newuse --backtrack=90 --ask world
9 > >> > failed with the following message:
10 > >> >
11 > >> > These are the packages that would be merged, in order:
12 > >> >
13 > >> > Calculating dependencies... done!
14 > >> > [ebuild U ] media-libs/lcms-2.6-r1 [2.5] USE="threads%*" ABI_X86="(64%*) (-32) (-x32)"
15 > >> > [ebuild U ] net-misc/wget-1.16 [1.14]
16 > >> > [ebuild U ] media-gfx/imagemagick-6.8.9.9 [6.8.8.10-r1]
17 > >> >
18 > > <skipped>
19 > >> >
20 > >> > I think that something may be wrong with sys-devel/gcc-4.8.3 as my problems begun when
21 > >> > I have updated it from sys-devel/gcc-4.7.3-r1 this Monday. Namely, just after this only
22 > >> > update, # emerge @preserved-rebuild
23 > >> > failed to rebuild app-text/pdftk-1.44 that was not updated that time and built well with
24 > >> > sys-devel/gcc-4.7.3-r1. Then I recalled that to build app-text/pdftk I had to add gcj use
25 > >> > flag to sys-devel/gcc. So, as I am not fond of Java, I just unmerged app-text/pdftk.
26 > >> > Bu now it seems that I had to unmerge media-libs/lcms and all packages that depend on it.
27 > >> >
28 > >> > May be it would be easier to unmerge sys-devel/gcc-4.8.3 and return back to
29 > >> > sys-devel/gcc-4.7.3-r1 but I do not know how to do it properly.
30 > >> >
31 > >>
32 > >> Did you remember to run 'gcc-config -f 1' after updating gcc as root?
33 > >
34 > > No, I did not remember to run 'gcc-config -f 1' because I never knew that it should be done
35 > > and no portage message advised me to do so. `man gcc' or `man gcc-config' also report that
36 > > there is no manual on these packets. Gentoo's Upgrading GCC wiki also says nothing about
37 > > this command...
38 > >
39 > >> What's the output of 'gcc-config -l'?
40 > >
41 > > # gcc-config -l
42 > > * gcc-config: Active gcc profile is invalid!
43 > >
44 > > [1] x86_64-pc-linux-gnu-4.8.3
45 > >
46 > > Nice!
47 > >
48 > > Ok, trying # gcc-config -f 1
49 > > * Switching native-compiler to x86_64-pc-linux-gnu-4.8.3 ...
50 > >>>> Regenerating /etc/ld.so.cache... [ ok ]
51 > >
52 > > * If you intend to use the gcc from the new profile in an already
53 > > * running shell, please remember to do:
54 > >
55 > > * . /etc/profile
56 > >
57 > >
58 > > What exactly shall I remember to do?
59 > >
60 > > Ok, # gcc-config -l
61 > > [1] x86_64-pc-linux-gnu-4.8.3 *
62 > >
63 > > Now # emerge --update --deep --with-bdeps=y --newuse --backtrack=90 --ask world
64 > > emerges all three above packages.
65 > >
66 > > Trying to emerge pdftk. Done.
67 > >
68 > > Ok. Thank you. But why there was no hint about it after updating gcc?
69 > >
70 > > Well, there was a reference to Gentoo's Upgrading GCC wiki
71 > > but nothing more...
72 >
73 > From the toolchain eclass[1]:
74 >
75 > # if we're installing a genuinely different compiler version,
76 > # we should probably tell the user -how- to switch to the new
77 > # gcc version, since we're not going to do it for him/her.
78 > # We don't want to switch from say gcc-3.3 to gcc-3.4 right in
79 > # the middle of an emerge operation (like an 'emerge -e world'
80 > # which could install multiple gcc versions).
81 > # Only warn if we're installing a pkg as we might be called from
82 > # the pkg_{pre,post}rm steps. #446830
83 > if [[ ${EBUILD_PHASE} == *"inst" ]] ; then
84 > einfo "The current gcc config appears valid, so it will not be"
85 > einfo "automatically switched for you. If you would like to"
86 > einfo "switch to the newly installed gcc version, do the"
87 > einfo "following:"
88 > echo
89 > einfo "gcc-config ${CTARGET}-${GCC_CONFIG_VER}"
90 > einfo "source /etc/profile"
91 > echo
92 > fi
93 >
94 > This gets printed if you "genuinely" install a different compiler
95 > version. If it didn't, it is a bug and should be reported.
96
97 Thank you for replying to this thread.
98
99 I have just checked and found out that, after upgrading my gcc
100 from version gcc-4.7.3-r1 to version 4.8.3, I got the following
101 message:
102
103 >>> Installing (1 of 1) sys-devel/gcc-4.8.3
104 * The current gcc config appears valid, so it will not be
105 * automatically switched for you. If you would like to
106 * switch to the newly installed gcc version, do the
107 * following:
108
109 * gcc-config x86_64-pc-linux-gnu-4.8.3
110 * source /etc/profile
111
112 * Switching native-compiler to x86_64-pc-linux-gnu-4.7.3 ...>>> Regenerating /etc/ld.so.cache...
113 [ ok ]
114
115 * If you have issues with packages unable to locate libstdc++.la,
116 * then try running 'fix_libtool_files.sh' on the old gcc versions.
117
118 * You might want to review the GCC upgrade guide when moving between
119 * major versions (like 4.2 to 4.3):
120 * http://www.gentoo.org/doc/en/gcc-upgrading.xml
121
122
123 * Messages for package sys-devel/gcc-4.8.3:
124
125 * If you have issues with packages unable to locate libstdc++.la,
126 * then try running 'fix_libtool_files.sh' on the old gcc versions.
127 * You might want to review the GCC upgrade guide when moving between
128 * major versions (like 4.2 to 4.3):
129 * http://www.gentoo.org/doc/en/gcc-upgrading.xml
130
131 But I noticed only the last part of it, starting from
132 * Messages for package sys-devel/gcc-4.8.3 line.
133
134 Well, probably I should be more attentive...
135
136 > Regards.
137 >
138 > [1] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/eclass/toolchain.eclass?view=markup