Lire 1.3 on RedHat 9

[Willman, Matt B - CNF]

perl -V:usethreads comes back with "usethreads='define';".  Un-install the
XML-parser RPM and re-compile from scratch sounds like the way to go?

If that does fix it, then I would assume RedHat didn't re-compile all their
modules when they futzed around with their Perl config.

Matt

Matt Willman
503 450 2752(v)
503 701 9816(c)
willman.matt at cnf.com

Scientia est potentia.


-----Original Message-----
From: Francis J. Lacoste [mailto:flacoste at logreport.org] 
Sent: Monday, June 16, 2003 4:09 PM
To: Willman, Matt B - CNF
Cc: development at logreport.org
Subject: RE: Lire 1.3 on RedHat 9


On lun, 2003-06-16 at 18:50, Willman, Matt B - CNF wrote:
> Give the man a kewpie doll.
> 
> [...]
> ASCII output segfaults also.
> 
> XML parser was installed from RedHat RPMS, as was expat
> 
> perl-XML-Parser-2.31-15
> expat-1.95.5-2
> 
> Is there any information I can provide to make debugging easier?  
> Anything I should look at or different versions of software to try?
> 

Actually, I think I know the problem: Red Hat probably decided that it was
time to ship perl with threading enabled. Which causes all sort of troubles.
(I googled for that weird message I saw in your first post: "Attempt to free
non-existent shared string" and this seems to be related to threading.) 

The problem might be related to a non-thread aware compilation of
XML-Parser, but I'd expect Red Hat to rebuild all the perl RPMS when they
upgrade perl.

Anyway, you can check for a thread-enabled perl build by running the
command:

perl -V:usethreads

Here, it says:

usethreads='undef';

Next step would be to recompile the XML-Parser module just to see if it
solves the problem.

Francis J. Lacoste

-- 
Francis J. Lacoste              . .           http://www.logreport.org
/^LogReport$/               . .               flacoste at logreport.org

-- 
To UNSUBSCRIBE, email to development-request at logreport.org with a subject of
"unsubscribe". Trouble? Send an email with subject "help" to
development-request at logreport.org