From owner-freebsd-ports@FreeBSD.ORG Sat Jun 23 19:00:34 2012 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 653531065672; Sat, 23 Jun 2012 19:00:34 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by mx1.freebsd.org (Postfix) with ESMTP id C54EC8FC12; Sat, 23 Jun 2012 19:00:33 +0000 (UTC) Received: by wibhn6 with SMTP id hn6so1367491wib.13 for ; Sat, 23 Jun 2012 12:00:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=if9c7RfCfqJZ5EwfHQG0L+WUub414jPE5MIaw9u2ils=; b=h3q14WS9QkbMrElQUSb5/H0d1HTRH5aDvy6yBPbMYYwe82/apTHUFqS0ZoVUpbcLpS cYasBtHNGo84KSUJ1Mhcrh76QwkYfanPjP1K1VLvBCyts8X0+vBw9qi8tEQqTIKKTC++ ZGq7r4u/KQB3uo2xovqNgWHh8/ROolL7XdChZvwdY09HDdP0k5firEGatp2IB4tz/J6k fSBT4zwP/5FFN9EMNubD5CU2A+n3VIJUUHctRLGtivH7QKvHkByEOZE+SIk1BTY+mIDc T2R3iNwL4btQXiLqlscAks0HaqKfUXIFrSEZH6Exf4Y0zgbsl8vuZ00IkzbfTeSOuuYb X/pQ== MIME-Version: 1.0 Received: by 10.180.14.165 with SMTP id q5mr13161510wic.8.1340478027535; Sat, 23 Jun 2012 12:00:27 -0700 (PDT) Received: by 10.223.155.4 with HTTP; Sat, 23 Jun 2012 12:00:27 -0700 (PDT) In-Reply-To: <4FE60561.8050606@freebsd.org> References: <4FE5EA8E.1020302@FreeBSD.org> <4FE60561.8050606@freebsd.org> Date: Sat, 23 Jun 2012 12:00:27 -0700 Message-ID: From: Kevin Oberman To: Michael Scheidell Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: ports@freebsd.org Subject: Re: Anyone using perl-5.12 and WITH_PERL_MALLOC? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jun 2012 19:00:34 -0000 On Sat, Jun 23, 2012 at 11:05 AM, Michael Scheidell 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