Re: [Liberty-eiffel] Bug #44601

[Mehul Sanghvi]

Paolo, 

     I was talking about having a VM running on MacOS X, which will than run FreeBSD in it.  Not a VM running 

MacOS X  on some other host OS.   :) 

cheers, 

      mehul

On Thu, Feb 18, 2016 at 2:16 PM, Paolo Redaelli <address@hidden> wrote:

I was sure that there were no legal way to run Macosx into a virtual environment without owning Apple's hardware.
Am I wrong?

Il 18 febbraio 2016 17:36:54 CET, Mehul Sanghvi <address@hidden> ha scritto:

I only have an iMac and an old PowerMac G4 running Debian.

I can take a look at running a FreeBSD VM on my iMac and I can target that.  I think for the most part *BSD systems

will work if I target OS X, but why take that route when a VM may be available :)

I would like to target OS X first, only if it helps me get Eiffel up and running on my system to play around with.  This way I can work on making it a package for Macports as well.

Thoughts and/or suggestions ? 

cheers,

       mehul

On Thu, Feb 18, 2016 at 10:21 AM, Paolo Redaelli <address@hidden> wrote:

I don't own Apple hardware to test.

Yet I know that Mac OS X is quite similar to a BSD system under the hood, so I guess that if
we compile Liberty for some BSD it could also compile on MacOsX

According to https://wiki.freebsd.org/Myths and http://stackoverflow.com/questions/3446231/how-close-are-mac-os-x-and-bsd-related it seems that FreeBSD is the BSD variant most similar to MacOSX

Does anyone have any clue about it?

In that case we could target  FreeBSD .

2016-02-18 15:08 GMT+01:00 <address@hidden>:

I am the one who reported the bug #44601.

I have no objection. It would be wonderful if install.sh run on any Unix-like system.

KOIZUMI Satoru

On 平成 28/02/17, at 10:27, Mehul Sanghvi wrote:

I updated 44601.  Although it doesn't directly relate, it is along the same lines, basically there are problems with getting install.sh to work on MacOS X because
of assumptions about the script running with a GNU set of tools, rather than a general Unix set of tools.

I see that 44601 hasn't had an update in a while.  Since I'm going to need to get
past this issue, and will have to work on install.sh to do so, does anyone have objections to assigning this bug to me ?   Might as well put my release/build
engineering acumen to good use :)



cheers,

     mehul


--
Mehul N. Sanghvi
email: address@hidden

--

Mehul N. Sanghvi
email: address@hidden

-- Inviato dal mio cellulare Android con K-9 Mail.

--

Mehul N. Sanghvi
email: address@hidden