New installation defaults (was: Re: once we have cpplib...)

[Manfred Hollstein]

On Thu, 16 April 1998, 15:07:18, hjl@lucon.org wrote:

 [snip]
 > > If we'll be going to change installation rules, where should
 > > _G_config.h be installed? Currently it goes into
 > > ${prefix}/${target}/include, but I think it should be installed in
 > > ${libsubdir}/include (or ${gxx_include_dir}), right?!
 > 
 > We have to be very careful on it.
 > 
 > > 
 > > Anyway, if nobody  else has a patch already  I'll preparing  one which
 > > will provide this:
 > > 
 > >   1. Change the default for g++ header installation from
 > >      ${prefix}/include/g++ to ${libsubdir}/include/g++
 > >   2. Install _G_config.h in ${libsubdir}/include.
 > >   3. Install runtime libs (libstdc++.*) in ${libsubdir}
 > >      resp. subdirectories for multilib configurations.
 > > 
 > > Once  3. is active,  I'm afraid we'll be  receiving lots of complaints
 > > from Linux users  about   ld.so no  longer   finding libstdc++.so.2.8,
 > > though :-(
 > > 
 > 
 > I have warned it many months ago.

Agreed, I think if we'll be going to change installation defaults, we
should agree which way to go!

So, the questions look to me like:

1. Shall we change the installation defaults?

If yes:

 2. Where shall _G_config.h be installed?

    a) in ${libsubdir}/include
    b) in ${gxx_include_dir}

 3. How do we manage locating a shared libstdc++ at runtime if their
    location changes from a directory covered by /etc/ld.so.conf to a
    new absolutely non-standard one?

If not:

 4. How do we achieve to help people protect their `standard'
    installation from being clobbered by an `experimental' one and
    without introducing too many --prefix=.../package/... related
    directories?

I'm sorry if you feel bothered by this, but I agree with H.J.:

  the current situation isn't very pleasant with having two worlds
  competing: most Linux users able to get root access allowing them to
  add any possible directory to ld.so's cache, and the rest of the world
  (I really hate to always type something like the following on
   Solaris: "g++ ... -Wl,-rpath,`gcc --print-file-name=`"!).

So, what's your vote?

manfred