https://sourceware.org/bugzilla/show_bug.cgi?id=21251
--- Comment #6 from Nick Clifton <nickc at redhat dot com> --- Hi Rainer, >> Hmm, I was going to say not a lot, but then I remembered that GCC uses it: >> >> https://gcc.gnu.org/onlinedocs/gcc/Directory-Options.html > > Maybe I'm blind, but where did you see that? Umm, do you mean "where in that web page do I see an '=' prefix being used to indicate that a sysroot should be used ?" Then, right at the start: -idirafter dir Add the directory dir to the list of directories to be searched for header files during preprocessing. If dir begins with ‘=’, then the ‘=’ is replaced by the sysroot prefix; see --sysroot and -isysroot. If you mean, "where does this information come from ?" The have a look in gcc/doc/cppdiropts.texi. > I'd have been surprised to find pure linker option descriptions repeated > in the GCC manual, so I didn't even think to look. Well to be honest it is talking about the c-preprocessor include path options rather than the linker search path, but I think that it establishes a principle which users will expect to be followed. IE if include paths can use a '=' prefix then library search paths should be able to as well. Cheers Nick -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
