On May 19, 2020, Joseph Myers <jos...@codesourcery.com> wrote: > On Tue, 19 May 2020, Alexandre Oliva wrote: >> > I don't think the error should mention .exe, but I also don't think the >> > error should mention collect2 (see what I said in >> > <https://gcc.gnu.org/ml/gcc-patches/2019-11/msg01772.html>, the existence >> > of collect2 is an implementation detail). >> >> I'm not changing collect2, at least not in this patch, but I wouldn't >> mind making the match for the internal executable name optional. WDYT? >> Untested patch follows.
> Allowing a missing executable name is reasonable enough, but I was > actually thinking that the messages should print "gcc" or whatever command > the user ran in place of "collect2". Uhh, that would require matching pretty much anything, considering all the potential per-language driver names, for pre-install testing, and the arbitrary transforms, most commonly s,^,$target-, for post-install testing. Should we make the regexps '\[^\n\]*', as in so many other pruned messages? -- Alexandre Oliva, freedom fighter he/him https://FSFLA.org/blogs/lxo/ Free Software Evangelist Stallman was right, but he's left :( GNU Toolchain Engineer Live long and free, and prosper ethically
