> Le 27 déc. 2018 à 13:50, Akim Demaille <a...@lrde.epita.fr> a écrit : > > > >> Le 27 déc. 2018 à 11:04, Wouter Beek <wou...@triply.cc> a écrit : >> >> Hi Akim, >>> >>> That's weird. What "git status" noticing any difference? >> >> Yes, the missing file seems to have been deleted: >> >> ``` >> $ git status >> On branch master >> Your branch is up to date with 'origin/master'. >> >> Changes not staged for commit: >> (use "git add/rm <file>..." to update what will be committed) >> (use "git checkout -- <file>..." to discard changes in working directory) >> >> deleted: m4/m4.m4 >> >> Untracked files: >> (use "git add <file>..." to include in what will be committed) >> >> .bootstrap13738.0 >> .bootstrap13738.1 >> ``` >> >> I now have a working build on another distribution (Fedora). I still >> encountered the above issue with the missing m4/m4.m4 file. > > git reset --hard HEAD
I can reproduce this error: somewhere inside ./bootstrap, symlinks to nonexistent files are removed. And m4/m4.m4 is a symlink inside submodule/autoconf: if you run ./bootstrap before submodule update --init, it will kill this symlink. I'll see if I can do something about it. _______________________________________________ help-bison@gnu.org https://lists.gnu.org/mailman/listinfo/help-bison
