Re: Errors when building from source
Hi Akim, > > From the above I had concluded that I should first compile Bison and > > Flex later. > > Can't you get Flex from your distro? Yes, I'm now installing Flex through the package system (2.6.1). > > BTW, I also ran into the following error while running the `bootstrap' > > script in my local Bison directory for the first time: > > > >configure.ac:110: error: possibly undefined macro: AC_PROG_GNU_M4 > >If this token and others are legitimate, please use m4_pattern_allow. > >See the Autoconf documentation. > >autoreconf: /usr/bin/autoconf failed with exit status: 1 > > > > The link `m4/m4.m4' was not present in my local Bison directory. > > Following the discussion in > > https://lists.gnu.org/archive/html/bug-bison/2011-05/msg00012.html, I > > learned that running `git submodule update --init' prior to running > > `bootstrap' fixes this. > > 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 ..." to update what will be committed) (use "git checkout -- ..." to discard changes in working directory) deleted:m4/m4.m4 Untracked files: (use "git add ..." 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. --- Cheers, Wouter. ___ help-bison@gnu.org https://lists.gnu.org/mailman/listinfo/help-bison
Re: Errors when building from source
Hi Akim, On more thing I noticed: ``` $ bison --version bison (GNU Bison) 3.2.1.139-5fb0d-dirty Written by Robert Corbett and Richard Stallman. Copyright (C) 2018 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ``` This is after building the latest commit on master. The `5fb0d' bit correctly identifies this commit, but for the version number I was expecting to see 3.2.4 or later... --- Best, Wouter. Email: wou...@triply.cc WWW: https://triply.cc Tel: +31647674624 On Thu, Dec 27, 2018 at 5:04 AM Wouter Beek wrote: > > Hi Akim, > > > > From the above I had concluded that I should first compile Bison and > > > Flex later. > > > > Can't you get Flex from your distro? > > Yes, I'm now installing Flex through the package system (2.6.1). > > > > BTW, I also ran into the following error while running the `bootstrap' > > > script in my local Bison directory for the first time: > > > > > >configure.ac:110: error: possibly undefined macro: AC_PROG_GNU_M4 > > >If this token and others are legitimate, please use > > > m4_pattern_allow. > > >See the Autoconf documentation. > > >autoreconf: /usr/bin/autoconf failed with exit status: 1 > > > > > > The link `m4/m4.m4' was not present in my local Bison directory. > > > Following the discussion in > > > https://lists.gnu.org/archive/html/bug-bison/2011-05/msg00012.html, I > > > learned that running `git submodule update --init' prior to running > > > `bootstrap' fixes this. > > > > 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 ..." to update what will be committed) > (use "git checkout -- ..." to discard changes in working directory) > > deleted:m4/m4.m4 > > Untracked files: > (use "git add ..." 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. > > --- > Cheers, > Wouter. ___ help-bison@gnu.org https://lists.gnu.org/mailman/listinfo/help-bison
Re: Errors when building from source
Hi, that's unimportant detail. It's just future 3.3 however for whatever reason not yet properly identified. Cheers, > On 27 Dec 2018, at 11:15, Wouter Beek wrote: > > Hi Akim, > > On more thing I noticed: > > ``` > $ bison --version > bison (GNU Bison) 3.2.1.139-5fb0d-dirty > Written by Robert Corbett and Richard Stallman. > > Copyright (C) 2018 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > ``` > > This is after building the latest commit on master. The `5fb0d' bit > correctly identifies this commit, but for the version number I was > expecting to see 3.2.4 or later... > > --- > Best, > Wouter. > > Email: wou...@triply.cc > WWW: https://triply.cc > Tel: +31647674624 > > On Thu, Dec 27, 2018 at 5:04 AM Wouter Beek wrote: >> >> [...] > > [...] ___ help-bison@gnu.org https://lists.gnu.org/mailman/listinfo/help-bison
Re: Errors when building from source
> Le 27 déc. 2018 à 11:04, Wouter Beek 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 ..." to update what will be committed) > (use "git checkout -- ..." to discard changes in working directory) > >deleted:m4/m4.m4 > > Untracked files: > (use "git add ..." 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 ___ help-bison@gnu.org https://lists.gnu.org/mailman/listinfo/help-bison
Re: Errors when building from source
> Le 27 déc. 2018 à 11:15, Wouter Beek a écrit : > > Hi Akim, > > On more thing I noticed: > > ``` > $ bison --version > bison (GNU Bison) 3.2.1.139-5fb0d-dirty > Written by Robert Corbett and Richard Stallman. > > Copyright (C) 2018 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > ``` > > This is after building the latest commit on master. The `5fb0d' bit > correctly identifies this commit, but for the version number I was > expecting to see 3.2.4 or later... If you look at the git history, you'll see that I merge 3.2.1 into master, but that's all: the other patches were cherry-picked. ___ help-bison@gnu.org https://lists.gnu.org/mailman/listinfo/help-bison
Re: Errors when building from source
> Le 27 déc. 2018 à 13:50, Akim Demaille a écrit : > > > >> Le 27 déc. 2018 à 11:04, Wouter Beek 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 ..." to update what will be committed) >> (use "git checkout -- ..." to discard changes in working directory) >> >> deleted:m4/m4.m4 >> >> Untracked files: >> (use "git add ..." 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
