mirror of
https://github.com/ctm/syn68k.git
synced 2024-12-01 00:51:19 +00:00
Builds correctly on Mac OS X
This commit is contained in:
parent
c4c3d51467
commit
71bf911a65
10
README
10
README
@ -38,8 +38,7 @@ glibc-devel.i386 and libgcc.i386) then try this hack
|
||||
|
||||
To compile syn68k on Mac OS X (tested under 10.5.7), you currently
|
||||
have to override the cleanup script, since the stock script
|
||||
(i486-cleanup.pl) will consume all of syn68k.s. However, even if you
|
||||
do this, the resultant binary will not work with native code.
|
||||
(i486-cleanup.pl) will consume all of syn68k.s.
|
||||
|
||||
./autogen.sh
|
||||
CLEANUP='' ./configure
|
||||
@ -47,9 +46,10 @@ do this, the resultant binary will not work with native code.
|
||||
make install
|
||||
|
||||
To test syn68k, run test/syngentest and compare the output to
|
||||
test/output/10000. It should be the same. If you want to be
|
||||
more thorough, you can use other command line options and compare the
|
||||
results to other files, as described in test/output/README.
|
||||
test/output/10000. It should be the same, assuming the same block of
|
||||
memory can be obtained for the test. If you want to be more thorough,
|
||||
you can use other command line options and compare the results to
|
||||
other files, as described in test/output/README.
|
||||
|
||||
Performance nit:
|
||||
|
||||
|
5
TODO
5
TODO
@ -30,11 +30,6 @@
|
||||
figure out *exactly* which options should be available
|
||||
via configure
|
||||
|
||||
clean the junk out of test (mostly old test results)
|
||||
|
||||
build some semi-canonical test results to use for
|
||||
comparing on other platforms
|
||||
|
||||
write-up what is needed to do testing on a real m68k
|
||||
|
||||
need a .spec file so we can build syn68k and syn68k-devel
|
||||
|
Loading…
Reference in New Issue
Block a user