On Sat, Apr 15, 2017 at 5:45 AM, Esteban Lorenzano
wrote:
> this belongs to pharo-dev, please continue there :)
>
It should also have been cc'ed to vm-dev. It is mostly about VM related
issues.
On 15 Apr 2017, at 14:25, Alistair Grant wrote:
>
> On Sat, Apr 15, 2017 at 02:14:26PM +0200, Luke
Success!
I'm now running the Pharo 5.0, Pharo 6.0, and Moose 6.1 images without a
hitch.
Some hero has even fixed the libcairo name lookup issue in the Moose image.
Now it's searching LD_LIBRARY_PATH and so I have added every shared library
there in the wrapper script.
I decided to manually writ
On 17 April 2017 at 10:37, K K Subbu wrote:
> You can use the attached magic file with file(1) command:
>
> file -m magic ...
>
> to detect the image type. or register the patterns with binfmt_misc to
> match the vm to the image type automatically.
>
Thanks for this!
On Sun, Apr 16, 2017 at 11:21:48PM +0800, Ben Coman wrote:
> On Sun, Apr 16, 2017 at 10:50 PM, Alistair Grant
> wrote:
> >
> > Do you know how the linux zero conf scripts are / will be built?
> >
> > My assumption has been that they are part of the image build.
>
> I'm not familiar with the zero
On Mon, Apr 17, 2017 at 12:47:38PM +0200, Luke Gorrie wrote:
> On 17 April 2017 at 11:33, Luke Gorrie wrote:
>
> Fighting the VM build in another window. Just now I am able to build the
> 32-bit VM from master and run both the Pharo 5 and Pharo 6 images. The
> next
> problem is the i
On 17 April 2017 at 11:33, Luke Gorrie wrote:
> Fighting the VM build in another window. Just now I am able to build the
> 32-bit VM from master and run both the Pharo 5 and Pharo 6 images. The next
> problem is the issue of accessing $HOME. The actual error is
> ExternalLibraryFunction>>invokeWi
On 17 April 2017 at 11:59, Alistair Grant wrote:
> What about the genVersion.sh script I provided earlier in this thread?
>
The genVersion.sh script has a dependency under the hood that I can't
satisfy: it expects to be able to run git commands but I can't do that in
the nix environment.
The ro
On Mon, Apr 17, 2017 at 02:07:40PM +0530, K K Subbu wrote:
> On Monday 17 April 2017 01:04 PM, Luke Gorrie wrote:
> >
> >I wonder if some DWIM would make sense here. For example, my bash
> >wrapper that starts the VM could inspect the image file and decide which
> >VM is appropriate (spur, non-spur
Hi Luke,
On Mon, Apr 17, 2017 at 11:33:38AM +0200, Luke Gorrie wrote:
> On 17 April 2017 at 11:01, Luke Gorrie wrote:
> Otherwise I need to supply the "smudged" version information in some
> reasonable
> way.
What about the genVersion.sh script I provided earlier in this thread?
> I don't hav
On 17 April 2017 at 11:01, Luke Gorrie wrote:
> I have only read through once, but isn't it a no-brainer
>
^^^ please forgive gratuitously combative tone :)
Fighting the VM build in another window. Just now I am able to build the
32-bit VM from master and run both the Pharo 5 and Pharo 6 images
On 17 April 2017 at 10:17, Alistair Grant wrote:
> This isn't really a feature, it's a core part of the VM's operation.
> You could choose to build the itimer VM, but that has its own problems.
> See:
>
> https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/tag/r3732#linux
> http://forum.wo
On Monday 17 April 2017 01:04 PM, Luke Gorrie wrote:
I wonder if some DWIM would make sense here. For example, my bash
wrapper that starts the VM could inspect the image file and decide which
VM is appropriate (spur, non-spur, 32-it, 64-bit, etc.) Otherwise the
user needs to guess and decipher c
On Mon, Apr 17, 2017 at 09:34:53AM +0200, Luke Gorrie wrote:
> On 17 April 2017 at 07:50, Alistair Grant wrote:
>
> Yes, 32 bit VM will only work with 32 bit images, and 64 bit VM with 64
> bit images.
>
>
> I wonder if some DWIM would make sense here. For example, my bash wrapper that
On 17 April 2017 at 07:50, Alistair Grant wrote:
> Yes, 32 bit VM will only work with 32 bit images, and 64 bit VM with 64
> bit images.
>
I wonder if some DWIM would make sense here. For example, my bash wrapper
that starts the VM could inspect the image file and decide which VM is
appropriate
On Sun, Apr 16, 2017 at 11:55:27PM +0200, Luke Gorrie wrote:
> I have the VM building under nix from the master branch now. The build is
> based
> loosely on the linux.64x64 mvm script so it's building a 64-bit x86-64 VM. The
> pharo-vm commit I am testing is 1c38b03f (from wednesday.)
>
> I have
Luke,
I don't see this in the latest binary and I have not adjusted the rtprio
figures at all. I can try running some simple tests if you send them to me.
$ curl get.pharo.org/64/60+vmLatest | bash
file Pharo.image
Pharo.image: Smalltalk image Spur 64b +C+NF+Tag (68021)
$ prlimit --rtpr
I have the VM building under nix from the master branch now. The build is
based loosely on the linux.64x64 mvm script so it's building a 64-bit
x86-64 VM. The pharo-vm commit I am testing is 1c38b03f (from wednesday.)
I have tried opening both Pharo-60465.image and Pharo-50771.image and both
give
On 16 April 2017 at 16:42, Ben Coman wrote:
> A historical perspective...
>
Thanks for the background, Ben.
It sounds like the path of least resistance is to forget Pharo 5 and focus
on packaging up the Pharo 6 VM in a maintainable way. Then to get a stable
VM all I need to do is go hang out at
On Sun, Apr 16, 2017 at 10:50 PM, Alistair Grant wrote:
> Hi Ben,
>
> On Sun, Apr 16, 2017 at 10:42:42PM +0800, Ben Coman wrote:
>> On Sat, Apr 15, 2017 at 4:34 PM, Luke Gorrie wrote:
>> > On 15 April 2017 at 10:08, Alistair Grant
>> > wrote:
>> >
>> > Grabbing the source directly from Git is at
Hi Ben,
On Sun, Apr 16, 2017 at 10:42:42PM +0800, Ben Coman wrote:
> On Sat, Apr 15, 2017 at 4:34 PM, Luke Gorrie wrote:
> > On 15 April 2017 at 10:08, Alistair Grant
> > wrote:
> >
> > Grabbing the source directly from Git is attractive if (a) I know
> > that I am choosing a good version and (b
On Sat, Apr 15, 2017 at 4:34 PM, Luke Gorrie wrote:
> On 15 April 2017 at 10:08, Alistair Grant wrote:
>
> Grabbing the source directly from Git is attractive if (a) I know that I
am
> choosing a good version and (b) I am able to build it in a good way.
>
> Seems like a workable solution to (a) i
Whoops, now copied to pharo-dev to continue discussion there.
On Sun, Apr 16, 2017 at 9:13 PM, Ben Coman wrote:
> On Sat, Apr 15, 2017 at 12:43 PM, Luke Gorrie wrote:
>>
>> On 14 April 2017 at 22:20, Stephane Ducasse wrote:
>>>
>>> This is what we always have when we release and we freeze it.
>
this belongs to pharo-dev, please continue there :)
> On 15 Apr 2017, at 14:25, Alistair Grant wrote:
>
> On Sat, Apr 15, 2017 at 02:14:26PM +0200, Luke Gorrie wrote:
>> On 15 April 2017 at 11:53, Alistair Grant wrote:
>>
>>(actually, I'm not sure why you're bothering since 6 should
>>
23 matches
Mail list logo
