Bug 25508 - MULTILIB_OSDIRNAMES undocumented
Status: NEW
Product: gcc
Classification: Unclassified
Component: bootstrap
: P3 normal
: ---
Assigned To: Not yet assigned to anyone
: documentation
Depends on:
  Show dependency treegraph
Reported: 2005-12-20 21:31 UTC by Joseph S. Myers
Modified: 2014-12-23 17:21 UTC (History)
2 users (show)

See Also:
Known to work:
Known to fail:
Last reconfirmed: 2012-01-12 00:00:00


Note You need to log in before you can comment on or make changes to this bug.
Description Joseph S. Myers 2005-12-20 21:31:23 UTC
MULTILIB_OSDIRNAMES, as used in target makefile fragments t-*, is undocumented.
Comment 1 Andrew Pinski 2005-12-25 01:03:40 UTC
Comment 2 Eric Gallager 2014-12-22 22:03:15 UTC
In some of the t-linux64 Makefile fragments in config/gcc/, I found the following comment that seems to describe what the value of MULTILIB_OSDIRNAMES represents:

# On Debian, Ubuntu and other derivative distributions, the 32bit libraries
# are found in /lib32 and /usr/lib32, /lib64 and /usr/lib64 are symlinks to
# /lib and /usr/lib, while other distributions install libraries into /lib64
# and /usr/lib64.  The LSB does not enforce the use of /lib64 and /usr/lib64,
# it doesn't tell anything about the 32bit libraries on those systems.  Set
# MULTILIB_OSDIRNAMES according to what is found on the target.

Is there a more central location to which this comment should be moved? Or should it just be copied-and-pasted to the rest of the 64bit-Linux-specific Makefile fragments as well?
Comment 3 joseph@codesourcery.com 2014-12-23 17:21:52 UTC
The point isn't documenting the rationale for particular choices, it's 
documenting (in fragments.texi) the general semantics, including for the 
A=B and A=!B forms.  It looks like the documentation was added by

r193508 | doko | 2012-11-14 21:29:15 +0000 (Wed, 14 Nov 2012) | 36 lines

but without closing this bug.