------- Comment #2 from joseph at codesourcery dot com 2005-12-21 23:27 ------- Subject: Re: libstdc++ headers should go in multilib directories
On Wed, 21 Dec 2005, gdr at integrable-solutions dot net wrote: > > > ------- Comment #1 from gdr at integrable-solutions dot net 2005-12-21 23:23 > ------- > Subject: Re: New: libstdc++ headers should go in multilib directories > > "jsm28 at gcc dot gnu dot org" <[EMAIL PROTECTED]> writes: > > | Some libstdc++ headers are installed in GPLUSPLUS_TOOL_INCLUDE_DIR, i.e. > | include/c++/version/target. These headers are derived from information > | configured separately for each multilib, and in general may differ between > | multilibs, so should go in a multilib directory (e.g. > | include/c++/version/target/multilib). The precompiled headers installed > there, > | in particular, should be separately installed for each multilib in all > cases, > | even if in some cases the actual text headers happen to be the same for each > | multilib. > > Most headers are target independents, so should not suffer from > multilib issue. I would think that a proper plan to fix this is to > install target dependent thingies in some deeper subdirectories. This issue is only for the target-dependent headers (in GPLUSPLUS_TOOL_INCLUDE_DIR), which can also be multilib-dependent, not for the target-independent headers in GPLUSPLUS_INCLUDE_DIR and GPLUSPLUS_BACKWARD_INCLUDE_DIR. Only GPLUSPLUS_TOOL_INCLUDE_DIR would be flagged to use a multilib suffix. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25524
