On Thu, 2006-03-02 at 11:09, Richard Megginson wrote:
> >
> >>In addition, there are no pre-built native 64 bit Apache and Perl
> >>binaries that we can use. We require native 64 bit because all of our
> >>components are native 64 bit, and we'd rather not get into the business
> >>of having to ship the full contingent of 32 bit components with our 64
> >>bit distribution - harder to build, harder to manage, package size
> >>bloat, etc. etc.
> >>
> >>
> >
> >Aren't libraries almost certain to get out of sync on platforms
> >with 32/64 bit capabilities if you don't bundle both versions
> >in all binary distributions?
> >
> >
> I'm not sure I understand. For Solaris, we plan on having a native 32
> bit version (only 32 bit components) and a native 64 bit version (only
> 64 bit components). Same as we have now on linux. The linux i386
> packages contain only 32 bit components, and the x86_64 packages contain
> only 64 bit components.
If none of the components can successfully interact, I suppose
it doesn't matter. However, if you include both client and
server libraries, shouldn't you be able to use a 32-bit app
that needs client libraries to access a 64-bit server running
on the same box? Or vice-versa?
--
Les Mikesell
lesmikesell at gmail.com
