Date: Tue, 22 Oct 2002 08:24:05 +0300 From: Peter Pentchev <roam@ringlet.net> To: Linus Kendall <linus@angliaab.se> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PThreads problem Message-ID: <20021022052405.GD377@straylight.oblivion.bg> In-Reply-To: <1035232308.24315.37.camel@bilbo> References: <1035200159.24315.13.camel@bilbo> <20021021124520.GS389@straylight.oblivion.bg> <1035206648.24315.20.camel@bilbo> <20021021134834.GA41198@straylight.oblivion.bg> <20021021135045.GB41198@straylight.oblivion.bg> <1035218026.24330.33.camel@bilbo> <20021021194453.GB377@straylight.oblivion.bg> <1035232308.24315.37.camel@bilbo>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Mon, Oct 21, 2002 at 10:31:48PM +0200, Linus Kendall wrote: [snip] > > That was very thorough, thanks! Now I at least have a notion of what > is going on. Since this is slightly urgent I guess a hack into the > libcurl source code to try to remove the sigalarms would do the trick > (in my case). In the general case it seems like there's a rather big > problem here as libcurl's behavior cannot really work together with the > FreeBSD implementation of threads. I wonder, though.. If libcurl depends on Linux-specific threads library behavior, what would the effects be if it were to be compiled against the devel/linuxthreads port? Maybe I will try building curl with linuxthreads later today.. G'luck, Peter -- Peter Pentchev roam@ringlet.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 If the meanings of 'true' and 'false' were switched, then this sentence wouldn't be false. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE9tOD07Ri2jRYZRVMRAi4IAKC0XjrVxGjjMlBO3hiGcW66obj7zQCeJF3B czvp9SlfHVKpiiNqJrmlv+I= =1qsj -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021022052405.GD377>