Summary: | dev-db/virtuoso-server-6.1.5 with sys-devel/bison-2.6 - In file included from sparql2sql.c:31:0: sparql_p.h:451:5: error: conflicting types for ‘sparyyparse’ | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | MarisN <maris.gis> |
Component: | [OLD] KDE | Assignee: | Maciej Mrozowski <reavertm> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | cedric.godin, creffett, dschridde+gentoobugs, kde, kripton |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://github.com/openlink/virtuoso-opensource/issues/9 | ||
Whiteboard: | Fixed in 6.1.6 | ||
Package list: | Runtime testing required: | --- | |
Attachments: | virtuoso-server-6.1.5 build log |
Description
MarisN
2012-07-22 19:08:45 UTC
Created attachment 318934 [details]
virtuoso-server-6.1.5 build log
See, if it's not something alike to bug 427438. I had the same problem on x86 32bit. Reverting to bison 2.5.1 solved the problem, I suggest you try the same. I can confirm exactly the same issue. (In reply to comment #2) > See, if it's not something alike to bug 427438. Yes, it is. Downgrading bison to 2.5.1 fixes compilation. Changed summary to reflect the issue. Can somebody report it upstream? Is there any bison-2.6 issues tracking bug? This bug should remain open till it's fixed upstream. Bug opened upstream, and I will look at this when I have some time this weekend and see if I can come up with a patch. (In reply to comment #6) > Bug opened upstream, and I will look at this when I have some time this > weekend and see if I can come up with a patch. If it's about the problem described in the bug 427438, that snippet from NEWS already describes the fix. Well, a simple find-and-replace through the code didn't fix it, but I don't claim to understand the code all that well. Simple search and replace most likely won't work, but it seems there's a large field for simplification here. While most trivial would be something along the lines of %parse-param {void *sparp_as_void} %lex-param {void *sparp_as_void} (put near %pure-parser, not where the defines were) given a few other defines, it would seem that trying something like: %parse-param {sparp_t *sparp_as_void} %lex-param {sparp_t *sparp_as_void} (and adjusting the rest of the sources) would make things cleaner. ...and even looking only at this directory, some of bison sources here already use this method of defining the argument. Fixed in 6.1.6, which will be in the KDE overlay shortly and should hit the tree within a week. Thank you all. This should be fixed in 6.1.6, which was added to the tree by Chris.
> 05 Aug 2012; Chris Reffett <creffett@gentoo.org>
> +virtuoso-server-6.1.6.ebuild, -virtuoso-server-6.1.5.ebuild:
> Version bump, remove 6.1.5 because it's somewhat broken and unsupported for
> KDE 4.9.
|