On Tuesday 31 May 2011, Joel E wrote: > On Tue, 31 May 2011, Stefano Lattarini wrote: > > > And this is likely the problem: > > > > $ head -1 m4/m4.m4 > > head: cannot open `m4/m4.m4' for reading: No such file or directory > > m4/m4.m4 is in bison.git. It's a sym link: > > m4/m4.m4 -> ../submodules/autoconf/m4/m4.m4 > > Not sure how you wouldn't have it. > Neither am I :-(
> The hash of the most recent commit on > master is 28801043bb49bfb1e94bde2e46a9b580790afbd5. You might check "git > status" to see if there are any local changes. > Yes, git status returns: # On branch master # Changed but not updated: # (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 # no changes added to commit (use "git add" and/or "git commit -a") After running "git reset --hard" on my checked-out repository, the bootstraping, configuration, building and testing of bison succeeds. The same happens in a freshly cloned repository (if "git submodule init" is issued by hand in advance). So this was a user error after all; sorry for the time I've made you loose. Thanks again, Stefano
