| 1 |
On Tue, May 1, 2012 at 3:51 PM, Michael Mol <mikemol@×××××.com> wrote: |
| 2 |
> On Tue, May 1, 2012 at 4:46 PM, Paul Hartman |
| 3 |
> <paul.hartman+gentoo@×××××.com> wrote: |
| 4 |
>> On Tue, May 1, 2012 at 2:56 PM, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 5 |
>>> On Tue, 1 May 2012 12:30:11 -0700, Mark Knecht wrote: |
| 6 |
>>> |
| 7 |
>>>> Notice the (-win32codecs) flag. Seems to me (on this system anyway) |
| 8 |
>>>> they are hard masked off? I tried adding the flag to package.use but |
| 9 |
>>>> emerge won't enable the darn thing... |
| 10 |
>>> |
| 11 |
>>> You need to unmask the USE flag first, by adding -win32codecs |
| 12 |
>>> to /etc/portage/profile/use.mask |
| 13 |
>> |
| 14 |
>> If he is using amd64 he can't use win32codecs unless he uses a 32-bit |
| 15 |
>> mplayer/ffmpeg. AFAIK. |
| 16 |
> |
| 17 |
> Wouldn't using multilib work around this? |
| 18 |
|
| 19 |
I think he would still need to compile a 32-bit mplayer/ffmpeg (in a |
| 20 |
32-bit chroot) to be able to make use of them. Multilib would let him |
| 21 |
run 32-bit mplayer or ffmpeg binaries (which themselves would be able |
| 22 |
to use the 32-bit DLLs). But I don't think 64-bit mplayer/ffmpeg can |
| 23 |
call 32-bit DLLs. |
| 24 |
|
| 25 |
There is an amd64codecs package containing the 64-bit codecs, but it |
| 26 |
has been masked and made obsolete by the fact that mplayer/ffmpeg can |
| 27 |
natively do most (or all?) of those codecs these days. |
Archives