From: Alexander Kapshuk <alexander.kapshuk@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Cannot reinstall ffmpeg since new cpu flags [SOLVED]
Date: Mon, 2 Feb 2015 19:48:09 +0200 [thread overview]
Message-ID: <CAJ1xhMWbhZZhjbHrjm+_bQummC-6-raqrMwGe33pp4b7c8bPew@mail.gmail.com> (raw)
In-Reply-To: <54CF4506.7060308@hanft.de>
[-- Attachment #1: Type: text/plain, Size: 717 bytes --]
On Mon, Feb 2, 2015 at 11:36 AM, Matthias Hanft <mh@hanft.de> wrote:
> Alexander Kapshuk wrote:
> >
> > What's the output of the command lines shown below on your system?
> > grep -Es 'ffmpeg|CPU' /etc/portage/*
>
> Ah uh...
>
> /etc/portage/package.use:# this is necessary for ffmpeg update (see
> gentoo-bug 290741)
> /etc/portage/package.use:media-video/ffmpeg -pic
>
> Seems that I didn't USE "mmx" before, and, therefore, had to disable
> "pic" manually (because of the bug mentioned). Now "mmx" came into
> CPU_FLAGS, and obviously "mmx" and "pic" have to be enabled or disabled
> simultaneously.
>
> Thanks - this was a long-forgotten configuration...
>
> -Matt
>
>
> No worries.
Glad it worked out for you.
[-- Attachment #2: Type: text/html, Size: 1179 bytes --]
next prev parent reply other threads:[~2015-02-02 17:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 18:44 [gentoo-user] Cannot reinstall ffmpeg since new cpu flags Matthias Hanft
2015-02-01 19:13 ` Alexey Mishustin
2015-02-01 20:24 ` Mike Gilbert
2015-02-01 20:38 ` Alexey Mishustin
2015-02-01 20:41 ` Alexey Mishustin
2015-02-01 19:17 ` Alexander Kapshuk
2015-02-02 9:36 ` [gentoo-user] Cannot reinstall ffmpeg since new cpu flags [SOLVED] Matthias Hanft
2015-02-02 17:48 ` Alexander Kapshuk [this message]
2015-02-01 19:42 ` [gentoo-user] Cannot reinstall ffmpeg since new cpu flags Mike Gilbert
2015-02-01 20:01 ` Matthias Hanft
2015-02-01 20:32 ` Matthias Hanft
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=CAJ1xhMWbhZZhjbHrjm+_bQummC-6-raqrMwGe33pp4b7c8bPew@mail.gmail.com \
--to=alexander.kapshuk@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