Hi,
> It sounds like containers may be exactly what you want. The same
> development environment isolated from your host OS of choice. Docker
> containers run great on Linux and my understanding is that Windows is
> gaining/already has better support than the past. There's not much more
> work
Hello Richard,
It sounds like containers may be exactly what you want. The same
development environment isolated from your host OS of choice. Docker
containers run great on Linux and my understanding is that Windows is
gaining/already has better support than the past. There's not much more
On Sun, Jul 16, 2017 at 12:21:39PM -0400, David Bloom wrote:
Hi,
> Hi Richard. If you want to get PicoLisp running on windows compilation can
> be difficult but you mention wine. What are you trying to run PicoLisp on,
> Linux, BSD? If you are willing to try using Docker containers I've made
On Jul 16, 2017 10:33 AM, "Richard Z" wrote:
On Sun, Jul 09, 2017 at 02:06:05PM -0400, r...@tamos.net wrote:
Hi,
> Curious, if you gave Msys2 a try, as Mike was asking about here:
unfortunatley, msys2 (like cygwin) doesn't work with my wine installation
so I am out of
On Sun, Jul 09, 2017 at 02:06:05PM -0400, r...@tamos.net wrote:
Hi,
> Curious, if you gave Msys2 a try, as Mike was asking about here:
unfortunatley, msys2 (like cygwin) doesn't work with my wine installation
so I am out of luck for this project.
Also, it seems the float support of picolisp
>
>
> Does MSYS handle fork?
>
>
yes.
On Sun, Jul 09, 2017 at 02:06:05PM -0400, r...@tamos.net wrote:
Hi Rick,
> Curious, if you gave Msys2 a try, as Mike was asking about here:
>
> On Thu, 06 Jul 2017 13:07 +0300, Mike Pechkin wrote:
> > Richard,
> >
> > I've compile picoLisp under msys (http://www.msys2.org/)
> > and 'ctl'
Hi, Richard!
Curious, if you gave Msys2 a try, as Mike was asking about here:
On Thu, 06 Jul 2017 13:07 +0300, Mike Pechkin wrote:
> Richard,
>
> I've compile picoLisp under msys (http://www.msys2.org/)
> and 'ctl' locking works here.
> You should a try.
(Glad to see that joebo chimed in. I
On Wed, Jul 05, 2017 at 02:00:51PM -0400, Joe Bogner wrote:
Hi Joe,
thanks for your answer.
> I'm not sure about mingw/cygwin but I do have an unofficial port of pil-64
> that runs on windows using midipix --
> https://github.com/joebo/picoLisp-win-x86-64
out of curiosity, does the 32bit port
Richard,
I've compile picoLisp under msys (http://www.msys2.org/)
and 'ctl' locking works here.
You should a try.
On Wed, Jul 5, 2017 at 4:20 PM, Alexander Burger
wrote:
> On Wed, Jul 05, 2017 at 02:27:34PM +0200, Richard Z wrote:
> > > We now checked with Mike. Seems
Hi Richard,
I'm not sure about mingw/cygwin but I do have an unofficial port of pil-64
that runs on windows using midipix --
https://github.com/joebo/picoLisp-win-x86-64
My port has somewhat stalled as midipix is moving a bit slower than I
expected.
If I recall, most tests were passing and it
On Wed, Jul 05, 2017 at 02:27:34PM +0200, Richard Z wrote:
> > We now checked with Mike. Seems most of it is still needed. So we just did
> > the
> > first case in src/io.c
>
> so database locking now works (minus ocassional Windows bugs)?
Unfortunately not. It just passes compilation. We
On Tue, Jul 04, 2017 at 11:04:16AM +0200, Alexander Burger wrote:
> On Mon, Jul 03, 2017 at 04:42:32PM +0200, Alexander Burger wrote:
> > > Cool! So I can safely remove it? It looks ugly indeed ;)
> >
> > Looking at it, there are move such "ifndef __CYGWIN__" lines, besides the
> > above
> >
On Mon, Jul 03, 2017 at 04:42:32PM +0200, Alexander Burger wrote:
> > Cool! So I can safely remove it? It looks ugly indeed ;)
>
> Looking at it, there are move such "ifndef __CYGWIN__" lines, besides the
> above
> from "src/io.c" alsoin "src/pico.h" and "src/main.c".
>
> Rather ugly stuff,
On Mon, Jul 03, 2017 at 04:29:23PM +0200, Alexander Burger wrote:
> Hi Mike,
>
> > > noticed that the code still has
> > >
> > > #ifdef __CYGWIN__
> > > #include
> > > #define fcntl(fd,cmd,fl) 0
> > > #endif
> > >
> >
> > on my cygwin it compiles and pass buildin tests without code above
>
>
Hi Mike,
> > noticed that the code still has
> >
> > #ifdef __CYGWIN__
> > #include
> > #define fcntl(fd,cmd,fl) 0
> > #endif
> >
>
> on my cygwin it compiles and pass buildin tests without code above
Cool! So I can safely remove it? It looks ugly indeed ;)
♪♫ Alex
--
UNSUBSCRIBE:
On Sun, Jul 2, 2017 at 8:07 PM, Richard Z wrote:
> Hi,
>
> noticed that the code still has
>
> #ifdef __CYGWIN__
> #include
> #define fcntl(fd,cmd,fl) 0
> #endif
>
on my cygwin it compiles and pass buildin tests without code above
On Sun, 02 Jul 2017 19:07 +0200, Richard Z wrote:
> Did anyone test it recently?
Hi Richard,
Hopefully, joebo will comment on this. He is the one I know for sure
who has looked into mingw-type builds of picolisp this the past year.
Best, --Rick
--
UNSUBSCRIBE:
Hi,
noticed that the code still has
#ifdef __CYGWIN__
#include
#define fcntl(fd,cmd,fl) 0
#endif
- is this still necessary? Did anyone test it recently?
Regards,
Richard
--
Name and OpenPGP keys available from pgp key servers
--
UNSUBSCRIBE:
19 matches
Mail list logo