Very astute observation. I was wondering if anyone would catch that one. ----- danek.duv...@oracle.com wrote:
> Craig Mohrman wrote: > > This isn't answering your question, but another look at your message > made > me see this: > > > 'usr/perl5/5.16-64/...' > > What is that path? I made it up. ;) > Does Perl have no way of dealing with 32 and 64 > bit > objects in the same directory hierarchy? Apparently not. > Does this mean that > architecture > independent files will have to be either duplicated or linked between > the > two directories? > Is there any way instead to just duplicate > i86pc-solaris-64/auto, since that seems to be (at least for 5.12) > where all > the .so files go? > I would think i86pc-solaris-64 would be the one to > duplicate (perhaps i86pc-solaris-32, too), but there are plenty of > .pm > files in there ... I observed the same thing but after digging through Perl's documentation and googling this very question I see no answers to mixing the 2 binary sizes under 1 directory tree. The only advice I've see so far is treat the different bit sizes as if another version and just create another perl tree. It's sad. They are close to achieving this I believe but the one area they lack is bin. Their bin directory contains 3 actual binaries that need to be split out. Also the perl scripts under bin all have hardcoded paths to the perl they require: #!/usr/perl5/5.16-64/bin/perl So the bin directory IS unique per bit size. Anyways, I'm not going to architect this for the Perl community. Sigh... craig _______________________________________________ userland-discuss mailing list userland-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/userland-discuss
