Re: [PATCH v3] Add `--with-toolexeclibdir=' configuration option

["Maciej W. Rozycki" <macro@wdc.com>]

On Tue, 21 Jan 2020, Joseph Myers wrote:

> > Provide means, in the form of a `--with-toolexeclibdir=' configuration 
> > option, to override the default installation directory for target 
> > libraries, otherwise known as $toolexeclibdir.  This is so that it is 
> > possible to get newly-built libraries, particularly the shared ones, 
> > installed in a common place, so that they can be readily used by the 
> > target system as their host libraries, possibly over NFS, without a need 
> > to manually copy them over from the currently hardcoded location they 
> > would otherwise be installed in.
> 
> This patch is OK (I think you'll need to go via Ian for committing the 
> libgo part since that directory is imported from elsewhere).

 Joseph: Thank you for your review.

 Ian: Can we please coordinate this somehow?  The libgo/ part, like all, 
relies on config/toolexeclibdir.m4, so I can either:

1. push the whole change all at once and you'll push the libgo/ part to 
   your repo independently, which shouldn't be an issue except perhaps for 
   policy reasons as the changes will be identical anyway, or

2. push all the bits sans the libgo/ part and you'll push the libgo/ part 
   to your repo and then you'll merge it to GCC.

There is a slight technical advantage to going with #1 as there'll be no 
window where the new option is not consistently supported; it's also less 
work as you won't have to do the merge.  But I have no strong preference 
either way.

  Maciej