Date: Sun, 24 Jun 2012 18:46:10 -0400 From: Steve Wills <swills@FreeBSD.org> To: Kevin Oberman <kob6558@gmail.com> Cc: ports@FreeBSD.org, Michael Scheidell <scheidell@FreeBSD.org> Subject: Re: Anyone using perl-5.12 and WITH_PERL_MALLOC? Message-ID: <4FE798B2.5060403@FreeBSD.org> In-Reply-To: <CAN6yY1sfAQ-HjsZNuFJq1f-spVOozfYw_9UW4pQ06F-WOODkLA@mail.gmail.com> References: <4FE5EA8E.1020302@FreeBSD.org> <CAN6yY1uuefD0iQngPJpsHT=O103DkKC5_CH4tLmOySeMSV%2B49A@mail.gmail.com> <4FE60561.8050606@freebsd.org> <CAN6yY1sfAQ-HjsZNuFJq1f-spVOozfYw_9UW4pQ06F-WOODkLA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On 06/23/12 15:00, Kevin Oberman wrote: > > Yes, I agree that perl is not really being built with PERL_MALLOC, > but selecting THREADS and PERL_MALLOC options does produce a > working threaded perl. Neither THREADS nor PERL_MALLOC are > defaults, but I have ports installed that require threaded perl. Not to hijack the thread, but I'm just curious, which ports require threaded perl? Steve -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBAgAGBQJP55ixAAoJEPXPYrMgexuhfbUIAKNrOkBQ2UwDOnAUPUIw4RRt RQ9Tz/1eBbcdXIIsEIWB976v7tQF5Wavg1/seh6KeFE3CKS/vAjW6D3K6Rm+tJ// IGtrZly6xObcMa/SthB1nct2MYidJ1AWYZ9bFA2G6+RGt1LOlXHlC2KvljPum8wT OP5F7siIIrxnX1j1NdYV2IOgoNhJikjFJdPzm3WdOfFci7JwjgBnlX9NcBZ270QJ aDPobrTN+Y3d4RMyJRzOUQ1q2+QYybFPLOzDYylhWZQsHq8dksM4i17ZRp521fxP WPLH4hYrhe/WOa9JGByKFR9qp0b/3paXKX9xbsni3+SIjtk9UeSnlsB1FZTCDCM= =VrXR -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FE798B2.5060403>