Re: [PATCH] New configuration options to enable additional executable/startfile/shared library prefixes

[Gerald Pfeifer <gerald at pfeifer dot com>]

On Thu, 1 Nov 2012, Michael Meissner wrote:
> 	* doc/install.texi (--with-extra-prefix=): Document new configure
> 	switches.
> 	(--with-extra-exec-prefix=): Likewise.
> 	(--with-extra-startfile-prefix=): Likewise.
> 	(--with-extra-rpath-prefix=): Likewise.

+On powerpc64-linux systems, the dynamic linker will be searched for in
+the directories specified by the prefixed, that is used instead of the
                                  ^^^^^^^^
+standard system dynamic linker.

Is the use of "prefixed" correct her, or would that be "prefixes"?

+In addition on powerpc64-linux systems, if the user used static

"the user used" comes across a bit oddly.  How about "requests"?

+linking, as well as the @option{-mcpu=} option, the linker will be

Do I understand this correctly that both must hold?  Perhaps say "plus"
to avoid any ambiguity?

+for that particular machine.  If dynamic linking is used, these cpu
+tuned libraries will not be searched, since the dynamic linker will
+load the appropriate cpu tuned library, based on the system that is
+executing the code.

CPU (uppercase) in two cases.

+@item --with-extra-rpath-prefix=@var{prefixes}
+Specify additional directories for finding shared libraries when
+the compiler is run.  Each prefix is separated by the standard path
+sepator (usually colon, @option{:}).  By default no extra prefixes are
+used.  If this option is used, each of the directories if they exist
+will be specified to the linker via the @option{-rpath=} option.

"each of the directories if they exist" is a bit confusing ("each"
versus "they").

Do you mean "each of the directories that exists on the build system
will be..." or something like that?

Gerald