Mike Gran writes:
> On Tue, Nov 20, 2018 at 06:16:32PM +0100, Christoph Buck wrote:
>> Is there currently no way to get guile running under mingw-64bit? My plan
>> was to integrate guile in a project of mine which currently only builds
>> under 64bit.
>
> Well anything is possible, of course. Her
Christoph Buck writes:
> Currently i try to compile guile-2.2.4 under mingw64 bit.
Oh, interesting!
> I had some minor issues in the c source code which i managed to fix by
> applying some of the patches from
> https://github.com/mkeeter/guile-mingw. Namely
>
> 1) 0003-winsock-compat.mingw.patch
On Tue, Nov 20, 2018 at 06:16:32PM +0100, Christoph Buck wrote:
> Mike Gran writes:
>
> > Hey Chris,
> >
> > This is one of two errors. One problem is that Guile makes assumptions
> > about the size of long vs the size of a pointer, as do some the
> > libraries on which Guile depends. In practi
Mike Gran writes:
> Hey Chris,
>
> This is one of two errors. One problem is that Guile makes assumptions
> about the size of long vs the size of a pointer, as do some the
> libraries on which Guile depends. In practice, your Guile needs to be
> compiled under MinGW 32-bit where sizeof(void *)
> From: Christoph Buck
> Date: Tue, 20 Nov 2018 15:31:25 +0100
>
> > ice-9/boot-9.scm:752:25: In procedure dispatch-exception:
> > In procedure bytevector-u64-set!: Value out of range: -149659645
> > make[2]: *** [Makefile:1931: ice-9/eval.go] Error 1
> > make[2]: Leaving directory '/home/Christo
On Tue, Nov 20, 2018 at 03:31:25PM +0100, Christoph Buck wrote:
> Hi!
>
> Currently i try to compile guile-2.2.4 under mingw64 bit. I had some
> minor issues in the c source code which i managed to fix by applying
> some of the patches from https://github.com/mkeeter/guile-mingw. Namely
[...]
>
Hi,
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> Now that we're busy dropping cruft, it would be really nice if we could
> libtool too. (major sigh).
But we don't want to drop supported platforms, so we can't drop
Libtool. And Libtool is friendly, isn't it? :-)
Ludo'.
Ludovic Courtès escreveu:
> Hello,
>
> "Han-Wen Nienhuys" <[EMAIL PROTECTED]> writes:
>
>> autoreconf: running: aclocal --force
>> autoreconf: configure.in: not using Libtool
>> autoreconf: running: /home/hanwen/usr/pkg/ac/bin/autoconf --force
>> configure.in:20: error: possibly undefined macro:
Ludovic Courtès escreveu:
>
> Looks like the machine is missing Libtool or at least that its M4 macros
> cannot be found. You need Libtool 1.5.x, *not* Libtool 2.2.
>
>> How do I get GUILE to actually compile now?
>
> How did you get it to compile last week? :-)
I used my 32 bit laptop, but
Hello,
"Han-Wen Nienhuys" <[EMAIL PROTECTED]> writes:
> autoreconf: running: aclocal --force
> autoreconf: configure.in: not using Libtool
> autoreconf: running: /home/hanwen/usr/pkg/ac/bin/autoconf --force
> configure.in:20: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL
> If this t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Han-Wen Nienhuys wrote:
> Also, can someone tip me off how I create 64 bit binary on a mixed
> 32/64 machine? I assume the default
> will generate a 32 bit binary.
Actually I would think the default is to generate 64-bit code, but you can pass
gcc t
11 matches
Mail list logo
