If you want to port anything to use cthreads, you'll have to spend some
effort understanding in detail how startup and locking and so forth work in
cthreads, and debug this stuff yourself.
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/
I have got python2.1 to compile with cthreads enabled, however, when
I try to use said binary, it seg faults. Here is backtrace:
Program received signal SIGSEGV, Segmentation fault.
__libc_calloc (n=1, elem_size=20) at malloc.c:3832
3832malloc.c: No such file or directory.
in malloc
Here is more information on driving traffic to your site.
Pointcom.com is a pay-per-click search engine that operates in a similar
way to Goto.com. We have established ourselves as a safe and reliable
source of quality traffic over the past 7 years and look forward to
strengthening our posit
On Thu, Nov 01, 2001 at 07:07:13PM +0100, Alfred M. Szmidt wrote:
> Hi,
>
> There is a small error in `config.make.in' that will cause native compilation
> of the Hurd to fail. The problem is with MIGCOM being `$(MIG) -cc cat -
> /dev/null' when it really should be `$(MIG) -cc \"$(CPP)\" - /dev/
Hi,
There is a small error in `config.make.in' that will cause native compilation
of the Hurd to fail. The problem is with MIGCOM being `$(MIG) -cc cat -
/dev/null' when it really should be `$(MIG) -cc \"$(CPP)\" - /dev/null' or
`$(MIG) -cc "gcc -E -x c" - /dev/null', the first one is probably t
