[MacPorts] #60417: noah (run linux binaries on mac)
MacPorts
noreply at macports.org
Fri May 1 05:52:58 UTC 2020
#60417: noah (run linux binaries on mac)
----------------------+----------------------
Reporter: axet | Owner: (none)
Type: request | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords: haspatch
Port: noah |
----------------------+----------------------
Changes (by ryandesign):
* keywords: => haspatch
* cc: ryandesign (added)
Old description:
> Hello!
>
> Nice port to have 'noah' allows run linux binaries on mac OSX!
>
> https://github.com/linux-noah/noah
>
> brew has is
>
> # brew install linux-noah/noah/noah
New description:
Hello!
Nice port to have 'noah' allows run linux binaries on mac OSX!
https://github.com/linux-noah/noah
brew has is
{{{
# brew install linux-noah/noah/noah
}}}
--
Comment:
noah was initially submitted in [https://github.com/macports/macports-
ports/pull/1744 PR 1744] which was quickly closed and replaced with
[https://github.com/macports/macports-ports/pull/1745 PR 1745] where most
of the previous discussion happened. It looks like it was closed because
Ken couldn't get it to work on his machine with High Sierra without
crashing, and Perry thought it was too experimental to include a port that
we didn't at least think would work reliably on the then-current macOS
version.
In my testing on a 2012 MacBook Pro with Retina Display running High
Sierra, the software is still unreliable. Half the time, `noah` crashes at
launch with a malloc error, or it launches its emulated `bash` but then
any executable launched by that emulated bash crashes with a segmentation
fault. However other times it works fine, at least as far as launching
some of the Linux binaries that noahstrap installs, such as `ls` or
`uname` or `which`; I haven't sought out any other ELF binaries to test.
Fortunately, it is not our responsibility to fix these crashes. All that
we need to do is make it possible for a user to install the software that
the developer as provided, and that's what I've done in
[https://github.com/macports/macports-ports/pull/6986 PR 6986]. If the
software doesn't work, users can file bug reports with the developers.
The developers have provided Portfiles in their repositories; I used them
as the starting point for my Portfiles but made many changes. It is an
anti-pattern for projects to host their own Portfiles in their own
repositories and ask users to follow our local repository instructions to
use them. By adding these Portfiles to our official collection, we can
then file PRs with the developers to remove those Portfiles and update
their instructions for installing their software with MacPorts. Making it
easier for users to install this software should increase the number of
users who are available to submit bug reports or pull requests to the
developers to get the crashes fixed.
--
Ticket URL: <https://trac.macports.org/ticket/60417#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list