> Many thanks for this thorough analysis. Could you do me a favour?
> Could you send me the installation instructions and the
> generated chicken-config.h files for each build option you used?
> Perhaps that way we can figure out where our various Windows
> build configurations are inconsistent.
Mark,
Many thanks for this thorough analysis. Could you do me a favour?
Could you send me the installation instructions and the
generated chicken-config.h files for each build option you used?
Perhaps that way we can figure out where our various Windows
build configurations are inconsistent.
> Could you give 5.3.0rc2 a quick spin? In it, we've simply
> dropped the custom implementation of opendir and readdir.
Sure thing. Looks good.
Sorry it's taken a while to respond, but I wanted to do some thorough tests.
TL,DR;
It's not crashing any more
I can install eggs, and use them.
I
On Fri, Aug 27, 2021 at 08:00:22PM +0100, Mark Fisher wrote:
> I have traced where my copy is crashing, but I don't know why.
Hi Mark,
Could you give 5.3.0rc2 a quick spin? In it, we've simply
dropped the custom implementation of opendir and readdir.
Also, since it is pre-translated to C, it
I have traced where my copy is crashing, but I don't know why.
After compiling with DEBUGBUILD, and using gdb, I've step debug the
application until it crashes.
This is the last function it enters in chicken-install.c:
/* main#destination-repository in k8330 in k8326 in k8322 in k8318 in
k8314
Firstly,
> Hope this helps!
This is all incredibly helpful thanks!
> > This is exactly what I was expecting too, although the "mingw-msys"
> > build I would expect to be from a "MSYS2 MinGW 64bit" shell to be
> > specific (as opposed to "MSYS2 MSYS" shell) when running make.
>
> I don't
On Thu, Aug 26, 2021 at 01:38:42PM +0100, Mark Fisher wrote:
> I always ran clean/confclean between any builds to regenerate the
> chicken-config file and would
> watch for its generation when I built it, so I don't think it was that.
> I'm pretty sure I never mixed and matched PLATFORM= values
>
> Those assumptions are all correct. Looking at your other mail, I think I
> understand what might be going wrong here.
>
> My guess is that you either tried to use PLATFORM=mingw from an msys
> shell (i.e., msys2 bash), which would explain the error about XCOPY,
> or you used PLATFORM=... with
On Wed, Aug 25, 2021 at 08:34:47PM +0100, Mark Fisher wrote:
> I've finally been able to get chicken installed and working, but I had to
> pretend to be cygwin.
> I think there's errors in the mingw-msys Makefile, or my assumptions about
> it are wrong.
> I would expect:
> - "Makefile.mingw" to
>
> I just can't get this working.
>
I've finally been able to get chicken installed and working, but I had to
pretend to be cygwin.
I think there's errors in the mingw-msys Makefile, or my assumptions about
it are wrong.
I would expect:
- "Makefile.mingw" to produce files for MingW64 in a
> My patches had an error, instead of HANDLE there should have been
> intptr_t
Thanks Jani
Firstly, I completely wiped all mingw64/msys2, and chocolatey installs from
my PC before trying this.
My system is absolutely pristine new installs, versions are as follows:
$ uname -a
Hi,
My patches had an error, instead of HANDLE there should have been
intptr_t
diff -up chicken-5.3.0rc1/file.c.orig chicken-5.3.0rc1/file.c
--- chicken-5.3.0rc1/file.c.orig 2021-08-24 15:19:00.847104480 +0300
+++ chicken-5.3.0rc1/file.c 2021-08-24 15:36:10.889230349 +0300
@@ -46,7 +46,7 @@
Hi,
The following patch might make a difference,
diff -up chicken-5.3.0rc1/file.c.orig chicken-5.3.0rc1/file.c
--- chicken-5.3.0rc1/file.c.orig 2021-08-24 15:19:00.847104480 +0300
+++ chicken-5.3.0rc1/file.c 2021-08-24 15:36:10.889230349 +0300
@@ -46,7 +46,7 @@ struct dirent
typedef struct
{
Hey, Mark!
I successfully installed Chicken on Windows off chocolatey just last week.
To get around all of the requirements for the Unix programs I installed
win-bash and put them on my path so it could use cp etc. like normal. For
SRFI-18 specifically you do have to modify it from using the
Thanks Peter.
I messed up the threading on this conversation, and went into more details
elsewhere about my adventures into getting this working, and I've tried
more since.
I've had no luck with the latest version (5.3.0rc2); I discovered (via
strace) that the created executable is internally
On Sat, Aug 21, 2021 at 12:14:51PM +0100, Mark Fisher wrote:
> The compilation works fine, but when I run the install phase, the
> "chicken-install -update-db" just hangs
Hello Mark,
I seem te remember something like this caused by Windows Defender (the
virus scanner thing in Windows). If you
Hi Mark, I installed Chicken successfully on Windows not too long ago,
but unfortunately I've since switched my setup and I don't know what
your issue might be. However looking at the wiki instructions I do
remember that I didn't install Chicken 'in' msys, if that makes sense,
but from a 'normal'
Hi all,
I'm on a new PC with windows 10 and thought I'd try getting a chicken
environment up and running on MSYS2 MingGW-64.
I've installed a fresh copy of msys2 and mingw64 from the msys2 site, doing
the pacman updates on top.
I've then followed the guide at http://wiki.call-cc.org/msys2
18 matches
Mail list logo
