Hello, Ping for patch proposed here: https://gcc.gnu.org/ml/gcc-patches/2017-06/msg00579.html
Thanks much in advance, With Kind Regards, Olivier > On Jun 9, 2017, at 10:42 , Olivier Hainque <hain...@adacore.com> wrote: > > Hello, > > This is a follow-up improvement over the change > introduced from > > https://gcc.gnu.org/ml/gcc-patches/2016-01/msg00414.html > > << self-specs setup with configure --with-specs are allowed to contain > %:getenv > environment variable references. We are using this capability in a few cases > for cross ports. > > In such configurations, gcc --help or gcc --version fail if the variables > aren't defined [...] > > It is a bit annoying to have to define environment variables just to > be able to retrieve version info. >>> > > The attached patch adjusts the code to allow a lone "gcc -v" as well, > for the same reason. > > I verified that it works as intended on ports configured with > self specs as described above, that it doesn't change the behavior > of a lone "gcc -v" on a regular x86-linux compiler, and that is > bootstraps + regtests clean on x86_64-linux. > > OK to commit ? > > Thanks in advance, > > With Kind Regards, > > Olivier > > 2017-06-09 Olivier Hainque <hain...@adacore.com> > > * gcc.c (process_command): When deciding if undefined variables > should be ignored when processing specs, accept "gcc -v" as well. > > > <undef-var-gcc-v.diff>
