This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Path to libstdc++
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: "M. Lavasani" <lavasani at connect dot org dot uk>
- Cc: snowwolf at one2one-networks dot com (Allan Sandfeld Jensen), gcc at gcc dot gnu dot org, manfred dot h at gmx dot net, rodrigc at attbi dot com
- Date: 26 Mar 2002 12:39:22 -0300
- Subject: Re: Path to libstdc++
- Organization: GCC Team, Red Hat
- References: <200203260906.g2Q96Tb27762@quioch.connect.liv.ac.uk>
On Mar 26, 2002, "M. Lavasani" <lavasani@connect.org.uk> wrote:
> Apart from that I really think the gcc developers should come up
> with better configure and Makefile. First, they should scrap the
> idea of having version number in header and library path
Such that you have to set up a different --prefix, --exec_prefix or
--libdir yourself otherwise you'll overwrite a functioning compiler
with the newer one, and such that you can no longer have multiple
cross compilers sharing the same prefix/exec_prefix? The latter would
be a particularly major loss.
> second they should build gcc in the same directory as the source
The reason this doesn't work is that libiberty is built with the
compiler for the host and then with the compiler for the target, but
if you configure it in-place, as is the case for all packages built
with the compiler for the host, you lose when you try to configure it
for the target.
The solution would be to create not only <target> and <build>
subdirectories, but also <host> and, perhaps, <stage/host> ones, such
that we never run into the problem above.
> also thay can creat "lib" directory and move all the generated
> libraries in that directory, and use relative link instead of full
> path link.
Remember the user is allowed to configure --bindir=/foo/bar and
--libdir=/something/entirely/different, and the whole system is
supposed to work. So there's no way we can guess correctly what
relative prefix should be used, especially if yo consider that all of
/foo, /foo/bar, /something, /something/entirely and
/something/entirely/different may all be soft links, that point to
other pathnames with soft-links in between, some of which may change
over time.
I.e., I sometimes agree these matters are better left to the user to
figure out.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer