kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/unproven-pthreads/PLIST

35 lines
1 KiB
Text
Raw Normal View History

Move pkg/ files into package's toplevel directory
2001-11-01 01:57:41 +01:00
@comment $NetBSD: PLIST,v 1.1 2001/11/01 01:27:15 zuntum Exp $
Import unproven-pthreads, the mit-pthreads based cleanup I'm hacking on. Why am I using MIT-Pthreads? Because all the alternatives seem to have very low level problems. PTL2 has a locking problem of some sort that I cannot track down, and the author insists that lock = PTHREAD_MUTEX_INIT; is always to be legal, so he uses a pointer for locks. This means pthread_lock() can break in out of memory situations, and therefore so can pthread_once(), and if you're using that to protect logging, and you need to report a memory depletion, you're screwed. --Michael
1999-11-12 21:27:16 +01:00
pthreads/bin/pgcc
pthreads/bin/pg++
pthreads/lib/libpthread.a
The way that shared objects were handled in the PLISTs and bsd.pkg.mk was out of date - it was based on a.out OBJECT_FMT, and added entries in the generated PLISTs to reflect the symlinks that ELF packages uses. It also tried to be clever, and removed and recreated any symbolic links that were created, which has resulted in some fun, especially with packages which use dlopen(3) to load modules. Some recent changes to our ld.so to bring it more into line with other Operating Systems also exposed some cracks. + Modify bsd.pkg.mk and its shared object handling, so that PLISTs now contain the ELF symlinks. + Don't mess about with file system entries when handling shared objects in bsd.pkg.mk, since it's likely that libtool and the BSD *.mk processing will have got it right, and have a much better idea than we do. + Modify PLISTs to contain "ELF symlinks" + On a.out platforms, delete any "ELF symlinks" from the generated PLISTs + On ELF platforms, no extra processing needs to be done in bsd.pkg.mk + Modify print-PLIST target in bsd.pkg.mk to add dummy symlink entries on a.out platforms + Update the documentation in Packages.txt With many thanks to Thomas Klausner for keeping me honest with this.
2001-01-04 16:10:17 +01:00
pthreads/lib/libpthread.so
pthreads/lib/libpthread.so.1
Import unproven-pthreads, the mit-pthreads based cleanup I'm hacking on. Why am I using MIT-Pthreads? Because all the alternatives seem to have very low level problems. PTL2 has a locking problem of some sort that I cannot track down, and the author insists that lock = PTHREAD_MUTEX_INIT; is always to be legal, so he uses a pointer for locks. This means pthread_lock() can break in out of memory situations, and therefore so can pthread_once(), and if you're using that to protect logging, and you need to report a memory depletion, you're screwed. --Michael
1999-11-12 21:27:16 +01:00
pthreads/lib/libpthread.so.1.60
pthreads/include/Makefile.inc
pthreads/include/pthread.h
pthreads/include/sched.h
pthreads/include/pthread/cleanup.h
pthreads/include/pthread/cond.h
pthreads/include/pthread/debug_out.h
pthreads/include/pthread/fd.h
pthreads/include/pthread/fd_pipe.h
pthreads/include/pthread/kernel.h
pthreads/include/pthread/kthread.h
pthreads/include/pthread/mutex.h
pthreads/include/pthread/prio_queue.h
pthreads/include/pthread/pthread_attr.h
pthreads/include/pthread/pthread_once.h
pthreads/include/pthread/queue.h
pthreads/include/pthread/sleep.h
pthreads/include/pthread/specific.h
pthreads/include/pthread/state.def
bump to 0.17 -- fixes a resolver bug, and works with 1.5{,A,B} as well.
2000-07-10 22:12:18 +02:00
pthreads/include/pthread/sysfunc.h
Import unproven-pthreads, the mit-pthreads based cleanup I'm hacking on. Why am I using MIT-Pthreads? Because all the alternatives seem to have very low level problems. PTL2 has a locking problem of some sort that I cannot track down, and the author insists that lock = PTHREAD_MUTEX_INIT; is always to be legal, so he uses a pointer for locks. This means pthread_lock() can break in out of memory situations, and therefore so can pthread_once(), and if you're using that to protect logging, and you need to report a memory depletion, you're screwed. --Michael
1999-11-12 21:27:16 +01:00
pthreads/include/pthread/util.h
pthreads/include/pthread/version.h
pthreads/include/pthread/machdep.h
@dirrm pthreads/lib
@dirrm pthreads/bin
@dirrm pthreads/include/pthread
@dirrm pthreads/include
@dirrm pthreads
Reference in a new issue Copy permalink