[CentOS-devel] Re: Building perl (and perl threads memory leak)...

James Olin Oden james.oden at gmail.com
Fri Mar 9 17:14:12 UTC 2007

On 3/9/07, James Olin Oden <james.oden at gmail.com> wrote:
> On 3/9/07, James Olin Oden <james.oden at gmail.com> wrote:
> > Hi All,
> >
> > I'm trying to rebuild the version of perl that is in CentOS 4.3 to
> > update the version of threads::shared(3pm) that has a serious memory
> > leak in it.  When I try to build it some of the tests its running fail
> > (failure went off my screen but I'll have that in a moment) and it
> > failed to build.  BTW, I'm building on a CentOS 4.2 system.
> >
> > So my questions are two fold:
> >
> >   - Does anyone know of any known issues with building the perl SRPM in
> >     general?
> >   - Once I have the latest threads::shared in buildable SRPM is there
> > an interest
> >     in picking that up, or is there anyone that would like to put it
> > in a repository?
> >
> Correction I'm building on CentOS 4.3 and I pulled the SRPM from CentOS 4.4.
> The test that is failing is the t/op/pwent test.  I'll be looking at
> why its failing, but the same questions still apply.
OK, hre is the test error:

        # where NIS passwd
        # max = 25, n = 14, perfect = 0
        # The failure of op/pwent test is not necessarily serious.
        # It may fail due to local password administration conventions.
        # If you are for example using both NIS and local passwords,
        # test failure is possible.  Any distributed password scheme
        # can cause such failures.
        # What the pwent test is doing is that it compares the 26 first
        # entries of NIS passwd
        # with the results of getpwuid() and getpwnam() call.  If it finds no
        # matches at all, it suspects something is wrong.
        not ok 1        # (not necessarily serious: run t/op/pwent.t by itself)
        ok 2

So that on is not anyone's problem, save that I have to figure out how
to get it to not die...but the situation it reports that would make it
not a real bug is the situation on that build server.

Anyway, once I have the thing building with the non-leaky
thread::shared(3pm) libs, does anyone want to the SRPM (i.e. to host


More information about the CentOS-devel mailing list