This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: $(build_tooldir)/lib (was Re: http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html)
- To: "H . J . Lu" <hjl at lucon dot org>
- Subject: Re: $(build_tooldir)/lib (was Re: http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html)
- From: Jim Wilson <wilson at cygnus dot com>
- Date: Fri, 21 Jul 2000 15:53:03 -0700
- cc: gcc-patches at gcc dot gnu dot org
>I don't think it is that simple. You have to build libstdc++ v3 to
>see it. It even has a shell script, mkcheck, to figure out where
>header files and libraries are.
I still don't see the problem. You just add a -L option pointing at where
libstdc++ v3 is built. It doesn't matter how or when libstdc++ v3 is built.
I am aware of only one target tool at the moment that needs the -L option
for link tests, and that is gperf. This isn't in the FSF gcc tree, nor the
sourceware binutils/gdb tree, so this should not be a problem for you.
Jim