On Thu, 30 Aug 2001, Brian Harvell wrote:
>
> Sounds good. Out of curiosity why wouldn't you stick it in libdir/ia64
> or level with libdir in lib64 or some other like name.
>
> If I recall that's what Irix does for n32 vs 64 vs 32 bit libs.
yeah that's what IRIX does and IMO it's the most suitable solution to
the problem, but it's not the model adopted by trillian (aka linux for
ia64). The crux of the trillian model is that ia32 apps on ia64 are a
hack and perform poorly. In the open source world, the src should be
ported to ia64 and the apps should run native ia64, i.e. the ia32 libs
problem is a non-problem.
So the resulting trillian model for ia32 libs is adhoc - we had discussions
about this on the ia64 lists and none of the vendors (redhat, suse, turbo)
seemed to care two hoots, much less would they agree on a path/FS hierarchy
for ia32 libs on ia64. As a result, PCP installs ia32 libs in a private
directory (currently in $PCP_SHARE_DIR/lib/compat) and we link ia32 apps
using -rpath so they'll find their libs correctly. This seems to work
just fine .. for now. All this is needed for the pcp-pro RPM on ia64,
which has an app linked with a 3rd party static library (for which we
don't have the source).
thanks
-- Mark
|