From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] mplayer-package doesn't build forotherarchitectures than avr32
Date: Fri, 31 Aug 2007 18:05:07 +0200 [thread overview]
Message-ID: <00cb01c7ec06$cf9c3bb0$c6dc780a@atmel.com> (raw)
In-Reply-To: 20070831073156.GA29704@aon.at
>>> Ulf, can you fix this up in a sane manner, i.e. not add ...$(ARCH).patch
>>> stuff but arch agnostic, universally working fixes, if any?
>>>
>>> TIA,
>>>
>>
>>Got it from Hans Christian, which in his turn, got it from a colleague,
>>so they need to update it if that is to happen.
>>A lot of the stuff seems to be AVR32 specific in-line assembly code
>>using the AVR32 DSP features to optimize the mplayer algorithms,
>>so it seems utterly useless to apply for other architectures.
>
> Given that mplayer currently is at 1.0-rc1 (i.e. not released), what
> about fixing this in the proper place, i.e. upstream?
> $ svn ls svn://svn.mplayerhq.hu/ffmpeg/trunk/libavcodec/ | grep -i avr
> $
> Turns up nothing..
>
I think it is the intention of the AVR32 team to ensure that all additions
they do are fed upstream, but I do not control their activities.
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2007-08-31 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 8:33 [Buildroot] mplayer-package doesn't build for other architectures than avr32 Simon Pasch
2007-08-29 8:48 ` Hans-Christian Egtvedt
2007-08-30 22:14 ` Bernhard Fischer
2007-08-30 22:30 ` [Buildroot] mplayer-package doesn't build for otherarchitectures " Ulf Samuelsson
2007-08-31 7:31 ` Bernhard Fischer
2007-08-31 16:05 ` Ulf Samuelsson [this message]
2007-09-01 16:31 ` [Buildroot] mplayer-package doesn't build forotherarchitectures " Bernhard Fischer
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='00cb01c7ec06$cf9c3bb0$c6dc780a@atmel.com' \
--to=ulf@atmel.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.