OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: vputz on January 05, 2005, 09:00:36 pm
-
OK, I built xmame for 3.5.2 on my SL6000 using OpenEmbedded with this result:
root@tosa:/mnt/card# xmame.SDL
SDL: Info: SDL initialized
error: compiled byte ordering doesn't match machine byte ordering
are you sure you choose the right arch?
compiled for msb-first, are you sure you choose the right cpu in makefile.unix
sh: ../bin/qcop: not found
root@tosa:/mnt/card#
Looking at makefile.unix, the "arm" option doesn't appear to be a real one. Since OE is presumably using the arm toolchain anyway, I tried "risc_lsb" for MY_CPU, and may have made some progress...
root@tosa:/mnt/card# xmame.SDL
SDL: Info: SDL initialized
error: invalid value for brightness: 1.0
sh: ../bin/qcop: not found
root@tosa:/mnt/card#
However... still no luck on having the thing run. Doing a search for "invalid value for brightness" doesn't seem to reveal much. I don't have any sort of xmamerc, though--which may be important.
Any pointers?
-->VPutz
-
You tried from text console?
Try from opie-terminal - it looks like calls to qcop doesn't work due to missing OPIEDIR/QPEDIR/QTDIR env variables.
-
Good point (I had done it from text console for cut/paste).
But from the command line it's not much better.
Seven lines of
libpng error: Invalid bit depth
and then
SDL: Info: SDL initialized
error: invalid value for brightness: 1.0
... so something is still wonky. I don't even know where this "value for brightness" comes from. Interestingly, "xmame --help" gives the same result; I would have expected it to print the help message.
-->VPutz