This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: New installation defaults (was: Re: once we have cpplib...)
- To: manfred at s-direktnet dot de
- Subject: Re: New installation defaults (was: Re: once we have cpplib...)
- From: hjl at lucon dot org (H.J. Lu)
- Date: Sat, 18 Apr 1998 16:37:58 -0700 (PDT)
- Cc: law at cygnus dot com, jbuck at synopsys dot com, drepper at cygnus dot com, egcs at cygnus dot com
>
> 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)