On Thu Mar 20 16:59:55 2008, [EMAIL PROTECTED] wrote: > The dynamic lookup patch was applied in the PDD 17 branch, and merged in > with the rest of the branch. As I understood it, your problem with the > patch was that you didn't have MACOSX_DEPLOYMENT_TARGET properly set to > 10.3, and I remember resolving that.
No, it never was resolved. Even though I have had that TARGET set for weeks, whenever I applied what you were attempting I got those warnings during configuration. So I breathed a sigh of relief when you did not apply it to trunk. The failures reappeared after the PDD 17 branch was merged in -- and I'm not the only one reporting them. Andy Bach reported the same errors. > You reported all tests as passing > in the PDD 17 branch before the merge. > I have to apologize for what was an incomplete and misleading report. Looking back on that report, I see that it did *not* come from Darwin; it came from Linux (because only on my Linux can I simply call 'perl Configure.pl'). And the tests that were run were the pre- and post-configuration and build tools tests activated by 'perl Configure.pl -test'. Regardless of whether or not I was getting the warnings during auto::readline, all those tests were passing. And the sort of things they test were unlikely to be affected by what you were doing in the PDD 17 branch. So we're in a dilemma. The things that some of us are doing to try to push forward our development on Darwin are breaking the Darwin configuration and build of some of the rest of us on that platform. (Cf. the problems I'm reporting with one of chromatic's patches in http://rt.perl.org/rt3/Ticket/Display.html?id=51912.) So, although I know the news is not pleasant, I do have to report that the merging in of that branch has messed up (at least at the level of warnings) the same way I was configuring for > 1 year on my iBook. I don't know enough about this to provide a diagnosis, but I think it's at least a yellow flag in terms of our work on that OS. Jim Keenan
