Re: Retro for Mac G3 and G4

70 views
Skip to first unread message

crc

unread,
Aug 10, 2012, 11:55:46 AM8/10/12
to retr...@googlegroups.com
What GCC or CLANG version are you using?

In the meantime, you can grab a pre-converted image from http://rx-core.org/retroImages/ and see if that works.

-- crc

On Tuesday, July 17, 2012 6:24:00 AM UTC-4, saurus wrote:
I'd like to run retro on Mac G3 and G4, both under Mac OS X 10.4.11.  
I downloaded Retro 11.4; failed to make retroImageBE.  
Could you show me how to do it?  Here is what I did:

In Makefile I modified
  CFLAGS = -Wall
to
  CFLAGS = -Wall -DRXBE
and did 
$ make
rm -f retro
rm -f retroImage16 retroImage64
rm -f retroImage16BE retroImageBE retroImage64BE
rm -f *~
cc -Wall -DRXBE vm/complete/retro.c -o retro
$ make images
cc -Wall -DRXBE tools/convert.c -o convert
./convert
Loading...
Converting...
Saving...

rm -f convert
$ ls -l retro*
-rwxr-xr-x   1 ...  ...  34964 Jul 17 19:14 retro
-rw-r--r--   1 ...  ...  27876 Jul  9 19:00 retroImage
-rw-r--r--   1 ...  ...      0 Jul 17 19:14 retroImage16
-rw-r--r--   1 ...  ...      0 Jul 17 19:14 retroImage16BE
-rw-r--r--   1 ...  ...      0 Jul 17 19:14 retroImage64
-rw-r--r--   1 ...  ...      0 Jul 17 19:14 retroImage64BE
-rw-r--r--   1 ...  ...      0 Jul 17 19:14 retroImageBE

John Chandler

unread,
Aug 12, 2012, 4:47:37 PM8/12/12
to retr...@googlegroups.com
I am running 10.4.11 on a PowerBook G4, and attempting to launch
retro.py. Depending on the specific image I symlink to, I either get
a quiet exit, with exit code 0 (retroImage, retroImage64,
retroImage64BE, retroImageBE), or a noisy exit w/exit code 1
(retroImage16, retroImage16BE).

In the noisy case, here's the error message:
====
Traceback (most recent call last):
File "/Users/jmc/bin/retro.py", line 427, in <module>
run()
File "/Users/jmc/bin/retro.py", line 400, in run
memory = list(struct.unpack( cells * 'i', f.read() ))
struct.error: unpack requires a string argument of length 13936
====

The file sizes might have a bearing on this, but none of the images is
13936. The two that are closest are the ones that produce the noisy
failures:

-rw-r--r-- 1 jmc jmc 55752 Aug 12 14:46 retroImage64
-rw-r--r-- 1 jmc jmc 55752 Aug 12 14:46 retroImage64BE
-rw-r--r-- 1 jmc jmc 27876 Aug 12 14:47 retroImageBE
-rw-r--r-- 1 jmc jmc 27876 Aug 12 10:04 retroImage
-rw-r--r-- 1 jmc jmc 13938 Aug 12 10:05 retroImage16
-rw-r--r-- 1 jmc jmc 13938 Aug 12 10:06 retroImage16BE


This looks like a very basic problem, which could be difficult to fix,
or completely trivial. Do the symptoms I describe indicate what the
problem is, and what I can do about it?

-jmc
> --
> --
> You received this message because you are RETRO 10 discussion group.
> To post to this group, send email to retr...@googlegroups.com
> To unsubscribe from this group, send email to
> retro-10-u...@googlegroups.com

ur...@me.com

unread,
Aug 11, 2012, 10:33:11 AM8/11/12
to retr...@googlegroups.com
Thank you for the suggestions. I'm out of town now; will check when I'm home.
Reply all
Reply to author
Forward
0 new messages