Bug 2942 - build fails with conflicting types for 'YYSTYPE'
Summary: build fails with conflicting types for 'YYSTYPE'
Status: RESOLVED WONTFIX
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Plugins/Perl (show other bugs)
Version: 3.9.2
Hardware: Other Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2013-06-10 11:19 UTC by Mark Trompell
Modified: 2013-06-10 15:41 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Mark Trompell 2013-06-10 11:19:21 UTC 
Here is what I get.
using perl 5.8.8 & bison 2.5:

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../src -I../../../src/common -I../../../src/common -I../../../src/gtk -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/harfbuzz -D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS -DDEBUGGING -fno-strict-aliasing -pipe -Wdeclaration-after-statement -I/usr/local/include -D_LARGEFILE_SOURCE -I/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE -I/usr/kerberos/include/ -O2 -g -D_FORTIFY_SOURCE=2 -fstack-protector -Wno-unused-function -Wno-pointer-sign -Wall -pthread -I/usr/include/enchant -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -MT perl_plugin.lo -MD -MP -MF .deps/perl_plugin.Tpo -c perl_plugin.c  -fPIC -DPIC -o .libs/perl_plugin.o
In file included from /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/perl.h:3716,
                 from perl_plugin.c:50:
/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/perly.h:70: error: conflicting types for 'YYSTYPE'
matcher_parser_parse.h:287: note: previous declaration of 'YYSTYPE' was here
Comment 1 Paul 2013-06-10 12:31:15 UTC 
perl 5.8.8 is several years old and, afaik, now unsupported. My guess would be that this is fixed in a newer perl. Can you upgrade perl?
Comment 2 Mark Trompell 2013-06-10 14:08:23 UTC 
I can try to bump perl locally and see if the issue persists.
I probably can't easily bump it in our repository, as I can't right away foresee what it will break
Comment 3 Mark Trompell 2013-06-10 15:41:45 UTC 
Works with newer perl, so resolving as won't fix.
If you want to fix it for old perl, feel free to reopen.
Note You need to log in before you can comment on or make changes to this bug.