Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

10
  • 7
    This is basically correct as to what the problem is, but the issue isn't really libraries (which could be dragged along) but system calls, which are requests to the OS kernel. If the OS doesn't provide a compatible system call interface, you are out of luck. Commented Feb 22, 2011 at 22:11
  • 1
    Aah, This is excellent. This is exactly the kind of constructive correction I was hoping for. Thanks a bunch :D Could you tell me more about these supposed system calls, or redirect me to somewhere I can learn more about them? Commented Feb 22, 2011 at 22:16
  • 3
    They're not "supposed", they are actual. :) Here's a good start: ibm.com/developerworks/linux/library/l-system-calls Commented Feb 22, 2011 at 22:55
  • 7
    That said, your "crazy" idea isn't completely impossible. Just a lot of work. The Wine project is essentially this for running MS Windows binaries on Linux (or OS X). It provides a translation layer for system calls. wiki.winehq.org/… Commented Feb 23, 2011 at 0:12
  • 2
    Well, I figured it wouldn't be completely impossible, but I also did not expect it to be nearly as simple as I described it. I wrote the question with the intention of being corrected. This at times seems like a more efficient method of getting to the heart of the matter than asking a direct question such as "How do I convert a linux binary to run on Mac OS ". Also I have used wine from time to time, but I had never really pondered about how it worked before, I think I shall go look into it sometime now. Commented Feb 23, 2011 at 2:51