Il 09/05/2012 17:34, Matthias Klose ha scritto: >> > So -print-multiarch is like --print-multi-os-directory? > the former prints the part before the `:' in the MULTILIB_OSDIRNAMES, the > latter > the part after the `':', e.g. ../lib32 and i386-linux-gnu.
Yes, of course. >> > What is the difference, and where is it documented? > Not sure how it should be further documented. No idea, it is a new concept and people need to understand how it relates to multilibbing for example, what shortcomings are addressed etc. I went through the Debian pages (only cursorily, I admit) and I found nothing of this. Another question I have is related to usage of the option. Are you supposed to look for libraries in the multilib directories too if the compiler is multiarch-enabled? Or only in /lib/i386-linux-gnu? Which one takes priority, multiarch or multiosdir? >From the patch I can guess the intended search path is /lib/MULTIARCH:/lib/MULTIOSDIR, but I'm not entirely sure about that and it needs documentation. >> > Should it fail if multiarch support is not compiled in? > All the -print options always succeed. I would prefer if it just prints the > empty string if it is not configured (as it does now). Will the empty string be a valid output for a multiarch-enabled compiler? For example "gcc --print-multi-os-directory" and "gcc --print-multi-directory" on a bi-arch x86-64 compiler will never print the empty string. Again, I guess the answer is no but I'm not sure. If the answer is no, returning the empty string is fine. If the answer is yes, and assuming the search path is /lib/MULTIARCH:/lib/MULTIOSDIR, then programs need to know whether they need to omit the /lib/MULTIARCH component of the search path. A failure status code is then required. Paolo
