From mboxrd@z Thu Jan  1 00:00:00 1970
From: hjl@lucon.org (H.J. Lu)
To: manfred@s-direktnet.de
Cc: law@cygnus.com, jbuck@synopsys.com, drepper@cygnus.com, egcs@cygnus.com
Subject: Re: New installation defaults (was: Re: once we have cpplib...)
Date: Sat, 18 Apr 1998 18:48:00 -0000
Message-id: <m0yQhBG-00058vC@ocean.lucon.org>
References: <13624.39452.811565.52754@saturn.s-direktnet.de>
X-SW-Source: 1998-04/msg00742.html

> 
> 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

It may be ok for egcs, but not for a standalone libstdc++.

>     b) in ${gxx_include_dir}

I prefer this one since libstdc++ is not installed in
${libsubdir}.

> 
>  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=`"!).
> 

Give user a choice at the configure time.

-- 
H.J. Lu (hjl@gnu.org)