Date: Tue, 28 Dec 1999 11:27:12 +0100 From: Dirk Froemberg <dirk@freebsd.org> To: Mikhail Teterin <mi@kot.ne.mediaone.net> Cc: stable@freebsd.org, ports@freebsd.org, nsayer@freebsd.org Subject: Re: -lc vs. -lc_r (building Apache-PHP) Message-ID: <19991228112712.A9934@physik.TU-Berlin.DE> In-Reply-To: <199912272030.PAA76727@rtfm.newton>; from mi@kot.ne.mediaone.net on Mon, Dec 27, 1999 at 03:30:08PM -0500 References: <Pine.BSF.4.02A.9912271136420.6973-100000@shell.uniserve.ca> <199912272030.PAA76727@rtfm.newton>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Mikhail! On Mon, Dec 27, 1999 at 03:30:08PM -0500, Mikhail Teterin wrote: > Tom once stated: > => => What's the magic and why doesn't the port know it? Why is -lc even > => => in play if some of the components (-lmysqlclient) require -lc_r? > => => Yours, > => = > => = libmysqlclient does not require -lc_r, because the library does > => =not use threads. Only mysqld is threaded. > => > => Thank you, Tom, for this correction. However, this does not change > => much. Some other extension wants threads then... > = > = Uhh.. highly unlikely. Almost none of PHP3 is thread-safe, and only a > =bit of Apache is thread-safe. I doubt that anything in the Apache-PHP > =port wants or needs threads. > > I did not put it in there myself :) At least one of the many extensions > selected (I included the Makefile.inc with my original report) dragged > the c_r with it... It's the mhash option causing the problem. I disabled it for now. Basically the mhash port doesn't seem to be able to deal with FreeBSD's -pthread. I'll look at it to see whether the problem can be easily be solved. Regards Dirk [Cc'ed to mhash's maintainer] -- Dirk Froemberg FreeBSD: The Power to Serve! http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991228112712.A9934>