This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++-v3/std_cstddef.h's #include_next x libg++
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Subject: Re: libstdc++-v3/std_cstddef.h's #include_next x libg++
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 15 Aug 2000 04:48:23 -0300
- Cc: gcc at gcc dot gnu dot org, libstdc++ at sources dot redhat dot com
- Organization: GCC Team, Red Hat
- References: <Pine.SOL.3.91.1000810105701.7913A-100000@cse.cygnus.com>
On Aug 10, 2000, Benjamin Kosnik <bkoz@redhat.com> wrote:
>> > Shouldn't you be using INCLUDES from libstdc++-v3/src/Makefile.am:
>>
>> Great! That's the clue I was missing. Ok to install?
> Please do..........
Done. Sorry about the delay. Since I had failed to Cc: gcc-patches,
this message got in the wrong folder, and that's where I regularly
check for pending patches :-(
> (FYI at some point, I'd like to make things like INCLUDES go into the
> top-level Makefile.am, instead of being duplicated in the src/Makefile.am
> and libio/Makefile.am. I think I tried to do this once but it wasn't
> working and I gave up quickly (should this be possible?) . When/if I do
> this, will this bit need to be changed? )
Yep, it will have to be changed.
The way to go is probably to do it in libstdc++-v3's configure.in, and
get it AC_SUBSTed in all Makefiles. Then we probably won't have to
bother changing the way INCLUDES are handled.
Next step is to arrange for libstdc++-v3's configure to output a
`.'-able script that sets LD_LIBRARY_PATH or equivalent to all
directories containing run-time libraries. Then we'd arrange for the
top-level's SET_LIB_PATH to source any such scripts when appropriate.
--
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 *Please* write to mailing lists, not to me