From: LRN <lr...@gm...> - 2011-02-25 23:44:27
|
On 25.02.2011 21:04, LRN wrote: > On 25.02.2011 17:53, LRN wrote: >> On 25.02.2011 3:09, Charles Wilson wrote: >>> On 2/24/2011 6:44 PM, JonY wrote: >>>> On 2/25/2011 07:03, Charles Wilson wrote: >>>>> Well, if so then I share the same problem. It may be that jon_y's >>>>> build >>>>> environment (which IIRC is the msys-phoenix build, which is a >>>>> rather old >>>>> semi-fork of our msys) is, for whatever reason, "better" about this >>>>> problem than the current official msys 1.0.16. >>>> >>>> I was using vanilla MSYS then in 2008, not phoenix. It was all done >>>> on a >>>> Vista32 machine, no segfaults, no errors, it just worked out of the >>>> box. >>>> >>>> I remember using msysgit patches and msys-dtk, along with all the msys >>>> libs like libcrypt and such. >>> Interesting. >>> >>> Another idea I just had off the top of my head was PERHAPS the problem >>> is related to the new msys-gcc (3.4.5 vs. 2.95) and/or DLLs introduced >>> since 2008. The whole sync_with_child problem is usually triggered >>> because some DLL didn't end up loaded with the same image_base address >>> in the child as it had in the parent. >> I've attempted to unpack gcc-3.4.4-3-msys-1.0.13-bin.tar.lzma on top >> of the msys installation with which i've built perl, and then use >> that msys, with new gcc, to build perl again. The error reappeared. >> This gives weight to your theory about blaming it on gcc 3.4.x. > Also, retrofitting modern msys with msysDVLPR-1.0.0-alpha-1.tar.gz > allowed me to build perl 5.8.8 without stumbling upon fork-related > errors. > > Well, i wouldn't say that i've had no errors during the build, some > extensions have failed to build and make ignored them. But that's > better than encountering "sync_with_child" error early. > Also note that "build perl" does not mean "build perl that passes all > tests" or "get a build of perl that works flawlessly". Attached to > this message is a compressed log from executing `make test' upon the > latest version of perl i've built (the one when i've used modern msys > retrofitted with gcc-2.95). Looks decent to me, but then i have only > rudimentary knowledge of perl and i am hardly capable of judging the > importance of the failed testcases. Well, i've been tinkering around with the buildscript, and it came out pretty well. I'm attaching compressed test and harness logs and the buildsystem to this message. Requires contemporary msys with msysDVLPR-1.0.0-alpha-1.tar.gz H-m-m... Could it be possible to just download msysDVLPR (the same way it downloads perl tarball), unpack it to a local directory and prepend that directory's bin subdir to the PATH (msys-build-perl already changes PATH, so it shouldn't be a problem)? That would allow current msys users to build this perl OOTB with this buildscript, and will allow msys-perl-5.8.8 to become a full-featured package (as long as msysDVLPR dependency is not considered too ugly, or maybe you can just make a package for msys-gcc-2.95.3). P.S. It skips the installation of man-pages for some reason. |