Closed GoogleCodeExporter closed 9 years ago
Probably the binary I built (on 10.6) is not compatible with 10.5; not sure
which lib
I screwed though -.-
Original comment by auria...@gmail.com
on 17 Dec 2009 at 12:27
Okay, I tried uploading a new build, can you test? (it's the same file, just
re-download)
Original comment by auria...@gmail.com
on 17 Dec 2009 at 1:12
From the comments on the forum, it seems like it should now work; whoever has
that
power can close this issue
Original comment by auria...@gmail.com
on 18 Dec 2009 at 6:25
Actually, I still get the same error with the new binary
Original comment by ericd...@gmail.com
on 19 Dec 2009 at 8:27
Which new binary? I screwed up a couple time, so make sure you really have the
latest. The latest definitely shouldn't issue the same message since it does
not even
contain the said load command
Original comment by auria...@gmail.com
on 19 Dec 2009 at 3:44
tried just now with a freshly downloaded zip, still have an error but I noticed
that the
line (or byte?) number has changed:
ericd-2:MacOS eric$ ./run.sh example.v64
dyld: unknown required load command 0x80000022
./run.sh: line 1: 982 Trace/BPT trap ./mupen64plus --corelib
libmupen64plus.dylib --plugindir . --gfx mupen64plus-video-rice $1
I just noticed that the build instructions at [1] have been updated, I'll try
to make a
10.5 build.
Original comment by ericd...@gmail.com
on 20 Dec 2009 at 9:03
Well I'm quite puzzled. A guy on the emutalk forum ran this binary successfully
on
his 10.5 machine
In any case, I believe command 0x80000022 is command LC_DYLD_INFO, which no more
appears in my last uploaded binary.
Original comment by auria...@gmail.com
on 20 Dec 2009 at 6:47
Maybe try the command otool -l mupen64plus on the executable, and see if
LC_DYLD_INFO
appears in the output; if it does then either you don't use the executable you
downloaded, either there's some weird caching issue somehwere
Original comment by auria...@gmail.com
on 20 Dec 2009 at 6:50
ericdrex, do you still have this compilation problem with the latest code or
has it
been resolved?
Original comment by richard...@gmail.com
on 14 Jan 2010 at 5:29
Original comment by richard...@gmail.com
on 20 Jan 2010 at 4:11
Since original reporter has not responded, I assume this issue has been
resolved. If
not, please re-open this issue report.
Original comment by richard...@gmail.com
on 2 Feb 2010 at 3:18
Just try the latest build 1.99.3 binary, and the same error appears on my OSX
10.5.8.
After trying the command otool -l mupen64plus as Comment 8 suggested, there is
no LC_DYLD_INFO in the output, but the following:
Load command 4
cmd ?(0x80000022) Unknown load command
cmdsize 48
00000000 00000000 0000b000 000001c0 00000000 00000000 0000b1c0 000003d0
0000b590 00000640
Hope it would be helpful to solve that problem.
Original comment by add...@gmail.com
on 23 Aug 2010 at 6:26
addone: ok thanks for testing; can you now run the same command, but this time
on all the .dylib librairies? (those in Contents/MacOS and also those in in
Contents/libs)
I can't find LC_DYLD_INFO on my side, so I wonder what the problem is :/ In the
end maybe we can simply get a 10.4/10.5 user to build mupen and bypass all the
complications of building for an older system than the build host
Original comment by auria...@gmail.com
on 23 Aug 2010 at 2:55
Original issue reported on code.google.com by
ericd...@gmail.com
on 16 Dec 2009 at 8:43