Jump to content

tien_huu_1408

Members+
  • Content Count

    23
  • Joined

  • Last visited

  • Days Won

    2

tien_huu_1408 last won the day on October 7 2016

tien_huu_1408 had the most liked content!

Community Reputation

2 Neutral

About tien_huu_1408

  • Rank
    Novice
  1. Re-read what I posted, you did something obviously wrong with muparser, probably linked to this "universal" setting, you are the only one who can fix it ! When I make clean, I saw this TienHuusMacBook:muparser H2T$ make clean rm -rf ./.deps ./.pch rm -f ./*.o rm -f ./lib/libmuparser.a rm -f ./lib/libmuparser.2.2.4.dylib rm -f ./lib/libmuparser.dylib rm -f ./lib/libmuparser.dylib ./lib/libmuparser.2.dylib rm -f ./samples/example1/example1 It means the file existed. I rebuilt the muparser and check libmuparser.a is in /usr/lib already. TienHuusMacBook:muparser H2T$ sudo make install
  2. What should I do now? Frustrating to compile Raine ( Maybe I will stick to 0.63.4 instead. But I still want to compile by myself
  3. @Tux: Same error ld: symbol(s) not found for architecture i386 clang: error: linker command failed with exit code 1 (use -v to see invocation)
  4. @Tux: I continued to face another error after following your instruction. Hope you could help me solve it! I think it is the last step. Thanks! ld: warning: could not create compact unwind for __Z12do_soft_dipsi: stack subl instruction is too different from dwarf stack size 1258 translated messages, 2 fuzzy translations, 270 untranslated messages. ld: warning: could not create compact unwind for _parse: stack subl instruction is too different from dwarf stack size ld: warning: could not create compact unwind for _get_script_name: stack subl instruction is too different from dwarf stack size l
  5. TienHuusMacBook:raine-master H2T$ nasm -v NASM version 0.98.40 (Apple Computer, Inc. build 11) compiled on Aug 24 2016 I am trying to install newest nasm to 2.12.02 successfully TienHuusMacBook:nasm-2.12.02 H2T$ nasm -v NASM version 2.12.02 compiled on Oct 3 2016 After that, I try to rebuild Raine again. But I face the next error clang: error: no such file or directory: '/usr/local/lib/libmuparser.a' make: *** [raine] Error 1 How to solve it? Thanks!
  6. How to get the older nasm installed? I just got the nasm from source through brew install.
  7. Well if you installed all the libs, it's the hardest part in building raine, now all you have to do is build it from source, this way you are 100% sure you are using the latest official version. Just use git clone https://github.com/zelurker/raine.git or download a zip file from the git section. Then cd to the source directory, if all the libs are already installed you should be able to type make and everything should work without problem, it should autodetect everything including the fact you are using osx. If something fails tell me. You can use the very last git commit, there were only fixe
  8. @Tux About MacOSX version, it seems working for the first screen but after that, it crashes immediately. I am testing Samurai Spirits RPG with Raine 0.63.13 by @rrshier. It never happened with previous MacOSX before and Win version also. Again, I download Raine 0.63.4 provided by Raine website. It worked as a charm like before.
  9. Finally, I made it work perfectly under Mac OSX 10.11.6 as before. I have installed all required package and reinstall muparser with this command line: brew reinstall muparser --universal Moreover, could you help me compile Raine under Debian ARM like Raspberry Pi 3? If possible, hope you give me detailed instructions. Thanks a lot!
  10. Hi sir, I could not make it work under 10.11.6. I don't know why. Hope you could help me resolve it. Thanks! Problem report: Process: Raine [22779] Path: /Applications/Raine v0.64.13.app/Contents/MacOS/RaineIdentifier: org.vim.RaineVersion: ???Code Type: X86 (Native)Parent Process: ??? [1]Responsible: Raine [22779]User ID: 501 Date/Time: 2016-09-24 10:33:57.803 +0700OS Version: Mac OS X 10.11.6 (15G1004)Report Version: 11Anonymous UUID: 752862F8-4D25-D40C-
  11. Thanks a lot for your work. I will try and report later!
  12. Yeah. I think so but I still wait for next release for osx even though the win version is almost perfect!
  13. It means I should not try to download it. And continue to waiting official release. Right? Hic
  14. Please give me decryption key to access this file. Thanks a lot!
×
×
  • Create New...