Paul Eggert | 4 Jan 18:58
Favicon

Re: FW: [scons-users] Build error details needed!!! [Error 721035]

"Saurabh Bhatnagar" <saurabh.b.bhatnagar <at> oracle.com> writes:

> However, this is not approved since we need v2.3 on win 32 as well.
> Can you help with the steps to build bison on win32 and where I can get
> v2.3?

Sorry, I don't know.  I don't use Microsoft Windows.  But you can
build the files in question on some other host (GNU/Linux, say); you
don't need to build them on Microsoft Windows.

Wojciech Polak | 5 Jan 21:12
Picon
Gravatar

compiling current checkout

Hello,

There is an error while compiling a fresh new checkout:

Making all in src
make[1]: Entering directory `/home/polak/src/cvs/bison/src'
../tests/bison -y --warnings=all,error  "-dv" parse-gram.y
../tests/bison: line 8: /home/polak/src/cvs/bison/src/bison: No such
file or directory
../tests/bison: line 8: exec: /home/polak/src/cvs/bison/src/bison:
cannot execute: No such file or directory
make[1]: *** [parse-gram.c] Error 126
make[1]: Leaving directory `/home/polak/src/cvs/bison/src'
make: *** [all-recursive] Error 1

Joel E. Denny | 5 Jan 21:40

Re: compiling current checkout

On Sat, 5 Jan 2008, Wojciech Polak wrote:

> There is an error while compiling a fresh new checkout:
> 
> Making all in src
> make[1]: Entering directory `/home/polak/src/cvs/bison/src'
> ../tests/bison -y --warnings=all,error  "-dv" parse-gram.y
> ../tests/bison: line 8: /home/polak/src/cvs/bison/src/bison: No such
> file or directory
> ../tests/bison: line 8: exec: /home/polak/src/cvs/bison/src/bison:
> cannot execute: No such file or directory
> make[1]: *** [parse-gram.c] Error 126
> make[1]: Leaving directory `/home/polak/src/cvs/bison/src'
> make: *** [all-recursive] Error 1

Thanks for reporting that.  It looks like the timestamp on parse-gram.c 
was about 1s earlier than that on parse-gram.y.  I'm not sure how this 
happened, but I fixed it.

Claudio Saavedra | 9 Jan 21:42
Picon

comment about locations in data/yacc.c

Hi,

This may be nitpicking, but I suppose it's better to ask it, anyway:

In data/yacc.c:1021:

  /* Three stacks and their tools:
     `yyss': related to states,
     `yyvs': related to semantic values,
     `yyls': related to locations.

 ...

Shouldn't the comment about the locations stack be conditional to the
usage of locations (just as the declaration of the stack itself is)?

Would a patch to make it conditional be considered, or it doesn't worth
the effort?

Claudio

--

-- 
Claudio Saavedra <csaavedra <at> alumnos.utalca.cl>

Paul Eggert | 10 Jan 01:58
Favicon

Re: comment about locations in data/yacc.c

Claudio Saavedra <csaavedra <at> alumnos.utalca.cl> writes:

> Would a patch to make it conditional be considered, or it doesn't worth
> the effort?

Thanks, I installed this:

2008-01-09  Paul Eggert  <eggert <at> cs.ucla.edu>

	* data/yacc.c (yyparse): Correct the comment when locations aren't used.
	Problem reported by Claudio Saavedra in
	<http://lists.gnu.org/archive/html/bug-bison/2008-01/msg00003.html>.

Index: data/yacc.c
===================================================================
RCS file: /cvsroot/bison/bison/data/yacc.c,v
retrieving revision 1.169
diff -u -p -r1.169 yacc.c
--- data/yacc.c	29 Oct 2007 17:36:39 -0000	1.169
+++ data/yacc.c	10 Jan 2008 00:58:10 -0000
@@ -1018,10 +1018,10 @@ b4_c_function_def([yyparse], [int], b4_p
   YYSIZE_T yymsg_alloc = sizeof yymsgbuf;
 #endif

-  /* Three stacks and their tools:
-     `yyss': related to states,
-     `yyvs': related to semantic values,
-     `yyls': related to locations.
+  /* The stacks and their tools:
+     `yyss' is related to states.
(Continue reading)

Hans Aberg | 10 Jan 20:40
Picon
Picon

Re: comment about locations in data/yacc.c

On 9 Jan 2008, at 21:42, Claudio Saavedra wrote:

> This may be nitpicking, but I suppose it's better to ask it, anyway:
>
> In data/yacc.c:1021:
>
>   /* Three stacks and their tools:
>      `yyss': related to states,
>      `yyvs': related to semantic values,
>      `yyls': related to locations.
>
>  ...
>
> Shouldn't the comment about the locations stack be conditional to the
> usage of locations (just as the declaration of the stack itself is)?
>
> Would a patch to make it conditional be considered, or it doesn't  
> worth
> the effort?

Or
     /* Three stacks and their tools:
      `yyss': related to states,
      `yyvs': related to semantic values,
      `yyls': related to locations (optional).
   ...

   Hans Aberg

(Continue reading)

Claudio Saavedra | 11 Jan 20:14
Picon

Re: comment about locations in data/yacc.c


El jue, 10-01-2008 a las 20:40 +0100, Hans Aberg escribió:
> 
> 
> Or
>      /* Three stacks and their tools:
>       `yyss': related to states,
>       `yyvs': related to semantic values,
>       `yyls': related to locations (optional).

The problem with that approach is the same than with the previous one.
When inspecting the generated parser, you don't find that yyls stack at
all. Noting that it's optional doesn't necessarily makes the fact that
it wasn't generated more obvious.

I had in mind exactly what Paul committed.

Claudio

--

-- 
Claudio Saavedra <csaavedra <at> alumnos.utalca.cl>

Hans Aberg | 12 Jan 10:24
Picon
Picon

Re: comment about locations in data/yacc.c

On 11 Jan 2008, at 20:14, Claudio Saavedra wrote:

> I had in mind exactly what Paul committed.

I did not see his post when I wrote mine. :-)

   Hans Aberg

Micah Henning | 19 Jan 07:39
Picon

[GNU Bison 2.3] testsuite: 84 85 87 88 89 90 94 108 126 129 133 135 137 139 141 142 143 144 145 146 147 148 150 151 152 153 156 157 failed

:-(
Attachment (testsuite.log): application/octet-stream, 163 KiB
Juan Manuel Guerrero | 21 Jan 16:15
Picon
Picon

Difficulty trying to build distribution from CVS sources

Hello,
I have checked out today's CVS head on my linux box to test if the DJGPP
port still works.
Here some parameters:
Linux localhost 2.6.18.8-0.5-default #1 Fri Jun 22 14:17:53 CEST 2007 x86_64 GNU/Linux
autoconf (GNU Autoconf) 2.61
automake (GNU automake) 1.10
ltmain.sh (GNU libtool) 1.5.24 (1.1220.2.455 2007/06/24 02:13:29)
coreutils 6.9
make 3.81
texinfo 4.11

Unfortunatly I was short on time so I have not followed this mailing list for
some months.  As usual I have tried to build a distribution by running
the command sequence:
  ./bootstrap
  ./configure
  make
  make check
  make dist
At a first glance all steps appeared to work except for the one to build
the dist target.  That target produces the following output:

  make: build-aux/git-version-gen: Kommando nicht gefunden   (command not found)
  INFO: rerunning autoconf for new version string: 
  cat: .prev-version: Datei oder Verzeichnis nicht gefunden  (file or directory not found)
  /bin/sh ./config.status --recheck
  running CONFIG_SHELL=/bin/sh /bin/sh ./configure   --no-create --no-recursion
[snip]
  make: build-aux/git-version-gen: Kommando nicht gefunden
(Continue reading)


Gmane