wrwalke@uunet.uu.net (William Walker) (03/14/90)
i compiled perl patchlevel 12 with no problems, passed all tests on my HP9000/850. Full optimization on and all tests passed, so i installed it. that was friday. tuesday i find patches 13 and 14. SURE i say, no problem. i patch my source and build it on my main machine. PL 14 fails test 0 of comp.cpp and hangs forever in comp.script. major bummer. i haven't had a chance to scope through it yet, but i hate when i get a "high-priority" patch that blows up. aaarrgghh. details to follow. bill.
piet@cs.ruu.nl (Piet van Oostrum) (03/14/90)
In article <3180@uvaarpa.virginia.edu>, prcrs!wrwalke@uunet (William Walker) writes: ` `i compiled perl patchlevel 12 with no problems, passed all tests on `my HP9000/850. Full optimization on and all tests passed, so i installed `it. that was friday. ` `tuesday i find patches 13 and 14. SURE i say, no problem. i patch my `source and build it on my main machine. ` `PL 14 fails test 0 of comp.cpp and hangs forever in comp.script. `major bummer. i haven't had a chance to scope through it yet, `but i hate when i get a "high-priority" patch that blows up. aaarrgghh. ` In article <2643@ruuinf.cs.ruu.nl>, piet@cs (Piet van Oostrum) writes: `I recompiled perl 3.0 patch level 14 on our newly installed HP/UX version `7.0 and several tests failed. We changed to version 7.0 last weekend. The `previous version of perl (patch level 12) had been compiled on HP/UX 6.5 `and continues to work on 7.0. I have not tried to compile perl3pl12 on `HP/UX 7.0. ` This looks like the same problem. But as the difference in the first case is pl 12-> pl 14, I now suspect perl rather than malloc. Could it be that perl destroys the malloc adm? Some wild store or so? -- Piet* van Oostrum, Dept of Computer Science, Utrecht University, Padualaan 14, P.O. Box 80.089, 3508 TB Utrecht, The Netherlands. Telephone: +31-30-531806 Uucp: uunet!mcsun!ruuinf!piet Telefax: +31-30-513791 Internet: piet@cs.ruu.nl (*`Pete')