Joakim Lundborg wrote:
the port in question is in
/usr/ports/devel/pth  and is GNU Pthreads.2.0

I assumed that the mod_php4 port automaticly did the right thing; it
tries to install GNU pthreads, but that install fails with the error
messages i reported. So if anyone's confused it's the mod_php4 port...

If GNU Pthreads isn't really necessary then I still need a way to
convince mod_php4 that it does not need GNU Pthreads.

I think I've read that GNU Pthreads have some differences that might
make some progs require it, but I'm not sure. Anyone knows about this?

ports/devel/pth are "GNU Portable Threads" which implements threading support using a common interface for all systems. php4 requires this for working with apache2 (what is declared as "experimental"). Because of apache2 and php4 work under unix and windows (os/2, beos, ...), at least mod_php4 might require sth. like pth for having the same interface to a thread library on all systems.


I know this doesn't help you, but may give some clearance.

So long,
Jens

- Joakim

ons 2003-02-26 klockan 03.24 skrev Kris Kennaway:

On Wed, Feb 26, 2003 at 02:06:39AM +0100, Joakim Lundborg wrote:

I'm trying to compile pthreads 2.0-0 from ports on an AlphaServer 5/400
running FreeBSD 5.0. (Pthreads is needed for php4)

I think you're confused about the need for this pthreads port (I can't find a 'pthreads' port anyway).."pthreads" means "posix threads" which are supported by the FreeBSD base system (libc_r). The php4 port should automatically do the right thing.

Kris



To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message





-- L i W W W i Jens Rehsack L W W W L i W W W W i nnn gggg LiWing IT-Services L i W W W W i n n g g LLLL i W W i n n g g Friesenstraße 2 gggg 06112 Halle g g g Tel.: +49 - 3 45 - 5 17 05 91 ggg e-Mail: <[EMAIL PROTECTED]> Fax: +49 - 3 45 - 5 17 05 92 http://www.liwing.de/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Reply via email to