"The Senator" <[EMAIL PROTECTED]> writes:
>
> So perhaps eval.c will need to include malloc.h,
Yep, thanks, I made that change.
> or is this autoconf's (or even somebody else's) job?
The blob of alloca code that's there is (or should be) the autoconf
manual recommendation.
> ??? This is out of
> eval.c:3248: warning: implicit declaration of function `alloca'
>
> The relevant line in the c file was I think in the debugging code,
Yes, but it's the debugging evaluator, ie. when you run with --debug
so you can see scheme-level backtraces.
Ok, so that probably needs fixing.
> so what's
"The Senator" <[EMAIL PROTECTED]> writes:
>
> eval.c:3248: warning: implicit declaration of function `alloca'
>
> The relevant line in the c file was I think in the debugging code,
Yes, but it's the debugging evaluator, ie. when you run with --debug
so you can see scheme-level backtraces.
> so wh
Oops, I gave it another try and 1.8 looks ok with no threads (on
gnu+linux at least). I should try to keep up, eh. You might want to
try a native mingw build before attempting the cross compile, I'd
Hmm, that sounds like a fair bit of trouble. I choose the path of
least resistance! (even thoug
"The Senator" <[EMAIL PROTECTED]> writes:
>
> Which version?
Oops, I gave it another try and 1.8 looks ok with no threads (on
gnu+linux at least). I should try to keep up, eh. You might want to
try a native mingw build before attempting the cross compile, I'd
guess the former gets a lot more exe
"The Senator" <[EMAIL PROTECTED]> writes:
>
> checking for restartable system calls... configure: error: cannot run
> test program while cross compiling
You should be able to force it with
./configure ac_cv_sys_restartable_syscalls=yes
or "no" if that's the right answer, I don't know how
"The Senator" <[EMAIL PROTECTED]> writes:
>
> I've read
> through the configure.in file (saw commented code for removing
> fileblocks.o using sed,
Yep, that's a bug in the guile configure I think. Try uncommenting
it,
LIBOBJS="`echo ${LIBOBJS} | sed 's/fileblocks\.o//g'`"
Or creating an
Cool, thanks for the suggestions on the build process. I'll try those,
and hopefully I won't come back with errors.
Incidentally, last time I tried cross-compiling to mingw (a while ago
now) it didn't work. I think in the end it bombed because mingw
didn't have pthreads and guile wasn't yet set
Greetings folks,
Thanks for a great piece of software!
I am building guile using the guile-1.8.0 tarball downloaded from the
frontpage of gnu.org/software/guile. I have successfully used the
tarball to compile guile-1.8.0 to run on Linux, but couldn't get it
(cross-compile) to run on windows. I
