On Sun, 21 Aug 2011, Matthias Klose wrote:
> On 08/21/2011 12:21 AM, Joseph S. Myers wrote:
> > On Sat, 20 Aug 2011, Matthias Klose wrote:
> >
> >> +@findex MULTILIB_OSDIRNAMES
> >> +@item MULTILIB_OSDIRNAMES
> >> +If @code{MULTILIB_OPTIONS} is used, this variable specifies the list
> >> +of OS subdirectory names. The format is either the same as of
> >> +@code{MULTILIB_DIRNAMES}, or a set of mappings. When it is the same
> >> +as @code{MULTILIB_DIRNAMES}, it describes the multilib directories
> >> +using OS conventions, rather than GCC conventions. When it is a set
> >
> > I think more explanation is needed of what this means (where OS
> > conventions are used and where GCC conventions are used).
>
> well, could you point me to the GCC conventions?
The directories named with the GCC conventions (for example, "64") are
used under libsubdir for libraries and .o files, under
libsubdir/include-fixed for fixed headers and under
($target/)include/c++/$version/$target for some C++ headers. The
directories named with the OS conventions (for example, "../lib64") are
used under ($target/)lib for libraries and under lib/ and usr/lib/ in any
sysroot. The OS conventions are always relative to a "lib" directory and
those directory names may start with "../" but names in the GCC
conventions should never start with "../".
--
Joseph S. Myers
[email protected]
