Having installed YDL on my play station 3m and then having tried and
failed to install my wireless keyboard, I have been following the
various messages that have developed over the past 6 months.It is a
great pity that the incompleteness of YDL and lack of readily accessible
documentation together with the failure of Sony to permit the machine to
be readily used and switch between operating systems should destroy what
could have been a fascinating and enriching engineering development, It
is disheartening to see discussions that are unchanged from 30 years ago
which to me show that all of the talk about object oriented code, and
clean interfaces was just that talk.I realise that the increasing
complexity of machines and programmes greatly increases the challenges,
however Many people such as myself do not want to spend our lives
fiddling trying to get commonly used software to work on a machine. It
is to me a measure of the inadequacy of the development and support
operation. This discourages me from even attempting to use the machine.
So no my play station is merely an expensive and clumsy blue ray
player. What a pity.
sincerely
Terence Christopher
On 7/27/2010 6:00 AM, Derick Centeno wrote:
On Mon, 26 Jul 2010 20:34:48 +0100
Pat Wall<[email protected]> wrote:
Hi All
I was wondering if anyone has tried building Firefox 4.0 beta or from
the latest source tree?
For me the build fails with an architecture support error for ycbcr
which has been added to Firefox from Chromium code:
"/home/pjwall/src/mozilla-central/gfx/ycbcr/chromium_types.h:76:2:
error: #error Please add support for your architecture in
chromium_types.h"
The new IPC support in Firefox from 3.6.4 onwards is using code from
Chromium giving a similar build failure but the build will complete
successfully if the option "ac_add_options --disable-ipc" is added to
the mozconfig.
Does anyone know of a similar option for disabling ycbcr or indeed
another workaround?
Thanks
Pat
Hi Pat:
The fastest and least time consuming option you may have is to comment
out the offending code.
The other possibility is to rewrite chromium_types.h so that it
references PPC recognized commands which also means that you may have
to become (or be) very familiar with PPC assembler and/or the PPC
command architecture controlling various aspects of the PPC cpu. The
problem with that is that you could make the new file so specific to
the PPC you own that the code may not function on other PPC systems
differently designed.
All the best...
_______________________________________________
yellowdog-general mailing list - [email protected]
Unsuscribe info: http://lists.fixstars.com/mailman/listinfo/yellowdog-general
HINT: to Google archives, try '<keywords> site:us.fixstars.com'
_______________________________________________
yellowdog-general mailing list - [email protected]
Unsuscribe info: http://lists.fixstars.com/mailman/listinfo/yellowdog-general
HINT: to Google archives, try '<keywords> site:us.fixstars.com'
