Re: Why do kaffe shared libraries get installed in share/kaffe/lib?

Date view Thread view Subject view Author view

From: Godmar Back (gback@cs.utah.edu)
Date: Tue Nov 10 1998 - 13:36:01 EST


>
> Alexandre Oliva writes:
> > I've just noticed that most of the kaffe shared libraries get
> > installed in share/kaffe/lib. This is just plain wrong; share
> > ($prefix/share) is not supposed to contain executable code nor
> > libraries; the lib directory ($exec_prefix/lib) is. Does anyone mind
> > if I fix configure.in so that it defines nativedir as
> > $exec_prefix/lib? Otherwise, the kaffe script should be fixed so that
> > it properly sets LD_LIBRARY_PATH.

Hmm, I thought it would do that:

LD_LIBRARY_PATH="$KAFFE_LIB"${LD_LIBRARY_PATH+":$LD_LIBRARY_PATH"}
export LD_LIBRARY_PATH

Is this something else?

>
> I think you don't need to set LD_LIBRARY_PATH because kaffe
> "knows" where to look when calling dlopen() .. ie, for all
> but the first shared lib, ld.so is not used- dlopen() is.
>
> Notice libkaffevm *is* in /usr/local/lib, whereas all the
> others are under /usr/local/share/kaffe/lib/ ...
>
> I think I remember that it used to be that all the libs were
> under lib, and then it was changed.. ? If so then it's worth
> asking why the change happened in the first place..
>

I noticed that change too and wondered. I had heard that the rule is
to only put architecture-independent stuff in a share directory.
On the other hand, I too have seen other people take a point of view
that share is everything that can or should be put on a shared server,
so having directories like share/freebsd, share/linux, etc. would
be okay --- if one takes this point of view.

In general, I don't think we have to stick to "GNU"'s or whoevers directives
by the letter: sometimes, bending the rules according to what makes most
sense for us is perfectly okay.

        - Godmar


Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:02 EDT