On Sunday, November 13, 2016 at 1:02:00 PM UTC-8, Gary Johnson wrote: > On 2016-11-13, Guido wrote: > > On Saturday, November 5, 2016 at 1:19:49 PM UTC-7, Guido wrote: > > > During the make cycle, cc* (.c, .o, .s, .le, .ls) appear, then > > > are removed in /tmp. > > > > > > In 8.0.0055, I'm left with 3 empty .c, .o, .le files + a .ld > > > file giving the allowable ld options since it did not like an > > > option or was missing a file. > > > > > > In my makeLog, I see a warning "_FORTIFY_SOURCE" redefined. > > > There are no other error/warning messages. > > > > > > Everything seems to function properly. > > > > > > Anyone know when this crept into vim? > > > > > > Patch? > > > > > > Thanks. > > > > After some exhaustive tests, it seems that the cause is grep-2.26, > > not vim! > > > > I mainly use Slackware 14.2. There was an upgrade from grep-2.25 > > in October that otherwise seemed ok, until this episode. I have no > > clue what broke in grep. > > The garbage did not show in my Fedora 24 partition because they > > still use grep-2.25. > > The grep development team has been making a number of "improvements" > to grep recently that have changed the behavior so as to have broken > some scripts that use it. Each new release seems to break something. > I don't know specifically what changed between 2.25 and 2.26. > > You might try setting > > LC_ALL=C > > in your shell before executing your build script. I now execute > grep using a function that includes > > LC_ALL=C grep ... > > to avoid at least that set of problems with the newer versions of > grep. > > If that doesn't fix the problem, you may have to find the line in > the build script that is now broken, find out how it is broken, and > change the invocation of grep to fix it. > > HTH, > Gary
I found a post on LQ about this. It's affecting LOTS more stuff than just vim. I reverted to grep-2.25 & will wait for the upstream community to decide what to do. https://www.linuxquestions.org/questions/slackware-14/pkgtools-grep-bug-in-slackware%5B64%5D-current-4175593054/ Guido -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
