>>>>> "Kyle" == Kyle Moffett <[EMAIL PROTECTED]> writes:
>> The problem is that both Apache::Request and Apache::Cookie link in >> libapreq (statically). You can "use" one *or* the other in a given >> mod_perl-enabled process, but if you try to "use" both, they both >> publish the same libapreq's symbols, and you get a symbol clash. Kyle> That is kind of weird, why isn't this the case on other platforms? Not sure. the .so for A::R and A::C both statically link to libapreq, which should internally bind the entry points between the A::R/A::C and libapreq libs, and it does on every platform including Apple. However, on Apple, the entry points are also *published*, so when both .so's are pulled in, you get a duplicate on the libapreq entry points! I'm not smart enough to know how to turn that off. That is, how do you tell Apple's linker that when making a .so that is linking to a .a that the entry points that pull the .a in are satisfied and now private? Works on standard GNU ld, and every other ld on the planet. Not on Apple. It makes those .a externs to be also published by the .so. Boom. Bug? Or feature? Another workaround would be to make libapreq a separate .so, and then pulling it in both ways from both A::C and A::R would still be OK. Perhaps. :) -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <[EMAIL PROTECTED]> <URL:http://www.stonehenge.com/merlyn/> Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training! _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
