1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
[[!meta copyright="Copyright © 2010, 2011, 2012 Free Software Foundation,
Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]
[[!tag open_issue_glibc open_issue_libpthread]]
[[!toc]]
# cthreads -> pthreads
Get rid of cthreads; switch to pthreads.
There is a [[!FF_project 275]][[!tag bounty]] on this task.
## Original [[community/GSoC]] Task Description
[[!inline pages=community/gsoc/project_ideas/pthreads feeds=no]]
## IRC, freenode, #hurd, 2012-04-26
<pinotree> youpi: just to be sure: even if libpthread is compiled inside
glibc (with proper symbols forwarding etc), it doesn't change that you
cannot use both cthreads and pthreads in the same app, right?
[[Packaging_libpthread]].
<youpi> it's the same libpthread
<youpi> symbol forwarding does not magically resolve that libpthread lacks
some libthread features :)
<pinotree> i know, i was referring about the clash between actively using
both
<youpi> there'll still be the issue that only one will be initialized
<youpi> and one that provides libc thread safety functions, etc.
<pinotree> that's what i wanted to knew, thanks :)
|
