public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jesús Guerrero" <i92guboj@terra.es>
To: <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] win32codecs on an ARM architecture?
Date: Wed, 02 Sep 2009 23:34:35 +0200	[thread overview]
Message-ID: <2ee207f78552c78f99bbf10c487fe125@localhost> (raw)
In-Reply-To: <200909022128.11102.expendable.0@danielquinn.org>

On Wed, 2 Sep 2009 21:28:10 +0000, Daniel Quinn
<expendable.0@danielquinn.org> wrote:
> I have 3 Sheevaplugs (http://www.marvell.com/featured/plugcomputing.jsp)
> which 
> all run ARM cpus.  For the most part I've had very few problems setting
> these 
> up to run Gentoo but now I'm trying to have one of them run Mencoder to
> record 
> CBC's The National from an MMS stream and I'm having this problem:
> 
>   Sorry, this file format is not recognized/supported
> 
> I can only assume that this is due to the fact that mplayer won't emerge
> with 
> the win32codecs USE flag, probably relating the architecture I'm using. 
> Isn't 
> there a way to make this work?  Emulate an x86 space or something?  I'm
> rather 
> new at working across architectures so I'm kinda poking around in the
dark 
> here.

I don't think so.

win32codecs install some dll files which come precompiled from
windows. There's no way to change that, they are dll's compiled
for x86. They work only for that arch. That's why chosing
closed formats is *never* a good idea.

Your best bet is the try the absolute latest ffmpeg and pray that
they have included support for the concrete format you need.

-- 
Jesús Guerrero



  reply	other threads:[~2009-09-02 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02 21:28 [gentoo-user] win32codecs on an ARM architecture? Daniel Quinn
2009-09-02 21:34 ` Jesús Guerrero [this message]
2009-09-03  1:32 ` Stroller

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=2ee207f78552c78f99bbf10c487fe125@localhost \
    --to=i92guboj@terra.es \
    --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