Date: Sat, 23 Jun 2012 12:00:27 -0700 From: Kevin Oberman <kob6558@gmail.com> To: Michael Scheidell <scheidell@freebsd.org> Cc: ports@freebsd.org Subject: Re: Anyone using perl-5.12 and WITH_PERL_MALLOC? Message-ID: <CAN6yY1sfAQ-HjsZNuFJq1f-spVOozfYw_9UW4pQ06F-WOODkLA@mail.gmail.com> In-Reply-To: <4FE60561.8050606@freebsd.org> References: <4FE5EA8E.1020302@FreeBSD.org> <CAN6yY1uuefD0iQngPJpsHT=O103DkKC5_CH4tLmOySeMSV%2B49A@mail.gmail.com> <4FE60561.8050606@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jun 23, 2012 at 11:05 AM, Michael Scheidell
<scheidell@freebsd.org> wrote:
>
>
> On 6/23/12 12:31 PM, Kevin Oberman wrote:
>
> (I noticed in the Makefile, if you have WITH_THREADS && WITH_PERL_MALLOC,
> .if defined(WITH_THREADS)
> #XXX .if ${ARCH} =3D=3D "amd64"
> #XXX IGNORE=3D =C2=A0 =C2=A0Threaded perl does not pass tests on ${ARCH}
> #XXX .endif
> CONFIGURE_ARGS+=3D =C2=A0 =C2=A0 =C2=A0 =C2=A0-Dusethreads=3Dy
> PKGNAMESUFFIX=3D =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0-threaded
> WITH_PTHREAD=3D =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 yes
> # it seems perl malloc has problems with threaded perl on FreeBSD
> .undef WITH_PERL_MALLOC
>
>
> I wonder if this is true for WITH_PTHREAD (which is on by default)
>
> anyone using it this way? with_perl_malloc? =C2=A0on 7.x?
>
> is it broken on 7.x?
>
> On my 9.0-Stable (4/28/12) system I have perl-threaded installed with
> PERL_MALLOC selected. 'perl5 -V' reports:
> Characteristics of this binary (from libperl):
> Compile-time options: MULTIPLICITY PERL_DONT_CREATE_GVSV
> PERL_IMPLICIT_CONTEXT PERL_MALLOC_WRAP
> USE_64_BIT_ALL
> USE_64_BIT_INT USE_ITHREADS USE_LARGE_FILES
> USE_PERLIO USE_PERL_ATOF USE_REENTRANT_API
> Built under freebsd
> Compiled at Feb 16 2012 10:25:18
>
> I believe you were tricked by the above .if defined in the Makefile
>
> mine (without_threads), and (without_perl_malloc) says same thing
> 'perl_malloc_wrap'
>
> (I ASSUME that WITH_PERL_MALLOC=C2=A0=C2=A0=C2=A0=C2=A0 and WITHOUT_THREA=
DS, it would say
> perl_malloc?
>
> here is mine: (that runs, without_perl_malloc)
>
>
> Characteristics of this binary (from libperl): this is the default build.
>
> =C2=A0 Compile-time options: PERL_DONT_CREATE_GVSV PERL_MALLOC_WRAP
> USE_64_BIT_ALL
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 USE_64_B=
IT_INT USE_LARGE_FILES USE_PERLIO
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 USE_PERL=
_ATOF
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.
--=20
R. Kevin Oberman, Network Engineer
E-mail: kob6558@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1sfAQ-HjsZNuFJq1f-spVOozfYw_9UW4pQ06F-WOODkLA>