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