summaryrefslogtreecommitdiffstats
path: root/libitm.1.pkg/files
diff options
context:
space:
mode:
authorP. J. McDermott <pjm@nac.net>2013-06-04 20:11:15 (EDT)
committer P. J. McDermott <pjm@nac.net>2013-06-04 20:11:15 (EDT)
commit483993c24194cb4c3254e85fc81ed14fa60bb7a2 (patch)
treef48cc10b4f6288069ca1fad01855ea242f853f2f /libitm.1.pkg/files
parente8647d9ec7b7126f708da068184522751dbb23d1 (diff)
Also edit MULTILIB_OSDIRNAMES in target fragment.
The GCC Internals manual (gcc/doc/fragments.texi) says: > For configurations that support both multilib and multiarch, > MULTILIB_OSDIRNAMES also encodes the multiarch name, thus subsuming > MULTIARCH_DIRNAME. > [...] > > MULTIARCH_DIRNAME is not used for configurations that support both multilib > and multiarch. In that case, multiarch names are encoded in > MULTILIB_OSDIRNAMES instead. This sounds like the makefile macro used depends on the build-time user configuration; that is, the options --disable-multilib and --enable-multiarch should cause MULTIARCH_DIRNAME to be used. Instead, it seems MULTILIB_OSDIRNAMES is used, even if multilib is disabled. So apparently, "configurations that support both" means GCC target configurations that support both features, not build-time user configurations that enable them.
Diffstat (limited to 'libitm.1.pkg/files')
0 files changed, 0 insertions, 0 deletions