After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 705401 - GStreamer does not build with Bison 3.0
GStreamer does not build with Bison 3.0
Status: RESOLVED DUPLICATE of bug 706462
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-08-03 12:05 UTC by Lubosz Sarnecki
Modified: 2013-08-21 09:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch to fix warnings because of redundant declarations (1.07 KB, patch)
2013-08-03 12:05 UTC, Lubosz Sarnecki
none Details | Review
Patch to fix build with bison 3.0 (780 bytes, patch)
2013-08-03 12:05 UTC, Lubosz Sarnecki
needs-work Details | Review

Description Lubosz Sarnecki 2013-08-03 12:05:10 UTC
Created attachment 250765 [details] [review]
Patch to fix warnings because of redundant declarations

Bison did some API changes. Gst does not build:

grammar.tab.c: In function 'priv_gst_parse_yyparse':
grammar.tab.c:1809:7: error: too few arguments to function 'priv_gst_parse_yylex'
   if (yychar == YYEMPTY)
       ^
./grammar.y:39:5: note: declared here
 int priv_gst_parse_yylex (void * yylval_param , yyscan_t yyscanner);
     ^

The patch to fix is pretty simple, didn't test it with older bison though.
Comment 1 Lubosz Sarnecki 2013-08-03 12:05:37 UTC
Created attachment 250766 [details] [review]
Patch to fix build with bison 3.0
Comment 2 Tim-Philipp Müller 2013-08-03 13:46:53 UTC
Comment on attachment 250766 [details] [review]
Patch to fix build with bison 3.0

Thanks for the patch! Unfortunately this seems to break the build with bison 2.x:


  CC     libgstparse_la-grammar.tab.lo
grammar.tab.c: In function 'priv_gst_parse_yyparse':
grammar.tab.c:1992:7: error: too many arguments to function 'priv_gst_parse_yylex'
./grammar.y:39:5: note: declared here
make: *** [libgstparse_la-grammar.tab.lo] Error 1
Comment 3 Lubosz Sarnecki 2013-08-03 14:59:29 UTC
The patch fixes the build, but it crashes

bmonkey@bbook:~$ gst-launch-1.0 videotestsrc ! autovideosink
Caught SIGSEGV
  • #0 waitpid
    from /usr/lib/libpthread.so.0
  • #1 g_on_error_stack_trace
  • #2 ??
  • #3 <signal handler called>
  • #4 ??
    from /usr/lib/libgstreamer-1.0.so.0
  • #5 ??
    from /usr/lib/libgstreamer-1.0.so.0
  • #6 ??
    from /usr/lib/libgstreamer-1.0.so.0
  • #7 gst_parse_launch_full
  • #8 gst_parse_launchv_full
  • #9 ??
  • #10 __libc_start_main
    from /usr/lib/libc.so.6
  • #11 ??

Comment 4 Tim-Philipp Müller 2013-08-05 12:02:29 UTC
Any chance you could provide a stack trace with full debugging symbols?
Comment 5 Lubosz Sarnecki 2013-08-06 10:30:24 UTC
gst-launch freezes at this step with debugging symbols:

0:00:00.044489880 11820       0x717a00 INFO            GST_PIPELINE gstparse.c:322:gst_parse_launch_full: parsing pipeline description 'videotestsrc ! autovideosink '

i tried "-g -O0", "-g3", "-g" but it does not crash anymore.
Comment 6 Sebastian Dröge (slomo) 2013-08-08 09:29:34 UTC
Could you get a backtrace of that crash? Must be somewhere in the bison generated code
Comment 7 Bruce Dubbs 2013-08-20 18:52:31 UTC
Program received signal SIGSEGV, Segmentation fault.
priv_gst_parse_yylex (yylval_param=yylval_param@entry=0x7fffffffd3f0, yyscanner=0x0)
    at lex.priv_gst_parse_yy.c:1157
1157    #line 71 "parse.l"
(gdb) bt
  • #0 priv_gst_parse_yylex
    at lex.priv_gst_parse_yy.c line 1157
  • #1 priv_gst_parse_yyparse
    at grammar.tab.c line 1809
  • #2 priv_gst_parse_launch
    at ./grammar.y line 938
  • #3 gst_parse_launch_full
    at gstparse.c line 324
  • #4 gst_parse_launchv_full
    at gstparse.c line 262
  • #5 gst_parse_launchv
    at gstparse.c line 215
  • #6 main
    at gst-launch.c line 987

Comment 8 Tim-Philipp Müller 2013-08-21 09:04:18 UTC

*** This bug has been marked as a duplicate of bug 706462 ***