public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Gevisz <gevisz@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Building media-libs/lcms-2.6-r1 failed
Date: Wed, 29 Oct 2014 21:10:28 +0200	[thread overview]
Message-ID: <54513bc9.a802980a.427d.2201@mx.google.com> (raw)
In-Reply-To: <CAJ1xhMUJ58=WLhKLSZV1cdhOb2kch3b-YdG6rEo7Btr5Sj_CjQ@mail.gmail.com>

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...


  reply	other threads:[~2014-10-29 19:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29 16:05 [gentoo-user] Building media-libs/lcms-2.6-r1 failed Gevisz
2014-10-29 17:25 ` Alexander Kapshuk
2014-10-29 19:10   ` Gevisz [this message]
2014-10-29 19:19     ` Canek Peláez Valdés
2014-10-29 19:50       ` Gevisz

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=54513bc9.a802980a.427d.2201@mx.google.com \
    --to=gevisz@gmail.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