From: Bernd Paysan [mailto:bernd.pay...@gmx.de]
Sent: Tuesday, August 13, 2013 12:51 PM
Am Dienstag, 13. August 2013, 12:28:30 schrieb Dennis Ruffer:
> You wrote: " To solve the chicken and egg problem do a make dist e.g.
> on Linux and untar the created tarball on cygwin64."
>
> I'm not sure ex
Am Dienstag, 13. August 2013, 12:28:30 schrieb Dennis Ruffer:
> You wrote: " To solve the chicken and egg problem do a make dist e.g. on
> Linux and untar the created tarball on cygwin64."
>
> I'm not sure exactly what that gained, but the build did get further. It
> still fails, with log attache
You wrote: " To solve the chicken and egg problem do a make dist e.g. on
Linux and untar the created tarball on cygwin64."
I'm not sure exactly what that gained, but the build did get further. It
still fails, with log attached. ;(
I see that you commented out the thread affinity and the 32 bit c
Am Dienstag, 13. August 2013, 06:47:16 schrieb Dennis Ruffer:
> I see the following as a new set of error messages since 04/09 when I last
> pulled down the git sources:
>
> $FFBB398C throw
> $FFBDE218 c(abort")
> $FFBDECCC compile-wrapper-function1
> /usr/src/gforth/lib/gforth/0.7.9_20130214/libc
I see the following as a new set of error messages since 04/09 when I last
pulled down the git sources:
$FFBB398C throw
$FFBDE218 c(abort")
$FFBDECCC compile-wrapper-function1
/usr/src/gforth/lib/gforth/0.7.9_20130214/libcc-named/pthread.c: In function
'stick_to_core':
/usr/src/gforth/lib/gfo
