On Tue, May 1, 2012 at 5:41 PM, Paul Hartman <paul.hartman+gen...@gmail.com> wrote: > On Tue, May 1, 2012 at 3:51 PM, Michael Mol <mike...@gmail.com> wrote: >> On Tue, May 1, 2012 at 4:46 PM, Paul Hartman >> <paul.hartman+gen...@gmail.com> wrote: >>> On Tue, May 1, 2012 at 2:56 PM, Neil Bothwick <n...@digimed.co.uk> wrote: >>>> On Tue, 1 May 2012 12:30:11 -0700, Mark Knecht wrote: >>>> >>>>> Notice the (-win32codecs) flag. Seems to me (on this system anyway) >>>>> they are hard masked off? I tried adding the flag to package.use but >>>>> emerge won't enable the darn thing... >>>> >>>> You need to unmask the USE flag first, by adding -win32codecs >>>> to /etc/portage/profile/use.mask >>> >>> If he is using amd64 he can't use win32codecs unless he uses a 32-bit >>> mplayer/ffmpeg. AFAIK. >> >> Wouldn't using multilib work around this? > > I think he would still need to compile a 32-bit mplayer/ffmpeg (in a > 32-bit chroot) to be able to make use of them. Multilib would let him > run 32-bit mplayer or ffmpeg binaries (which themselves would be able > to use the 32-bit DLLs). But I don't think 64-bit mplayer/ffmpeg can > call 32-bit DLLs. > > There is an amd64codecs package containing the 64-bit codecs, but it > has been masked and made obsolete by the fact that mplayer/ffmpeg can > natively do most (or all?) of those codecs these days. >
I don't muck with multilib explicitly; I have it enabled, but I don't actively do anything. How does one appropriately build a 32-bit version of an established ebuild on a multilib system? -- :wq
