On 09.05.2012 15:37, Paolo Bonzini wrote:
> Il 09/05/2012 02:38, Matthias Klose ha scritto:
>> Index: gcc/doc/invoke.texi
>> ===================================================================
>> --- gcc/doc/invoke.texi (revision 187271)
>> +++ gcc/doc/invoke.texi (working copy)
>> @@ -6110,6 +6110,11 @@
>> @file{../lib32}, or if OS libraries are present in @file{lib/@var{subdir}}
>> subdirectories it prints e.g.@: @file{amd64}, @file{sparcv9} or @file{ev6}.
>>
>> +@item -print-multiarch
>> +@opindex print-multiarch
>> +Print the path to OS libraries for the selected multiarch,
>> +relative to some @file{lib} subdirectory.
>> +
>> @item -print-prog-name=@var{program}
>> @opindex print-prog-name
>> Like @option{-print-file-name}, but searches for a program such as
>> @samp{cpp}.
>
> 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.
> What is the difference, and where is it documented?
Not sure how it should be further documented.
> 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).
Matthias
