r19370 extension/internal/pdfinput/pdf-parser.cpp:2***: error: expected primary-expression before '**' token
Inkscape svn trunk stopped building for me on Gentoo Linux ~x86 about two weeks ago, which corresponds somewhat with the last commit on xtension/internal/pdfinput/pdf-parser.cpp.
The build.log is huge, but available if it helps anyone debug.
# grep error: build.log extension/internal/pdfinput/pdf-parser.cpp:2259: error: expected primary-expression before '<<' token extension/internal/pdfinput/pdf-parser.cpp:2259: error: expected primary-expression before '<<' token extension/internal/pdfinput/pdf-parser.cpp:2259: error: expected primary-expression before '<<' token extension/internal/pdfinput/pdf-parser.cpp:2259: error: expected primary-expression before '<' token extension/internal/pdfinput/pdf-parser.cpp:2259: error: expected primary-expression before '.' token extension/internal/pdfinput/pdf-parser.cpp:2261: error: expected primary-expression before '==' token extension/internal/pdfinput/pdf-parser.cpp:2261: error: expected primary-expression before '==' token extension/internal/pdfinput/pdf-parser.cpp:2261: error: expected primary-expression before '==' token extension/internal/pdfinput/pdf-parser.cpp:2261: error: expected primary-expression before '=' token extension/internal/pdfinput/pdf-parser.cpp:2316: error: expected primary-expression before '<<' token extension/internal/pdfinput/pdf-parser.cpp:2316: error: expected primary-expression before '<<' token extension/internal/pdfinput/pdf-parser.cpp:2316: error: expected primary-expression before '<<' token extension/internal/pdfinput/pdf-parser.cpp:2316: error: expected primary-expression before '<' token extension/internal/pdfinput/pdf-parser.cpp:2316: error: expected primary-expression before '.' token extension/internal/pdfinput/pdf-parser.cpp:2318: error: expected primary-expression before '==' token extension/internal/pdfinput/pdf-parser.cpp:2318: error: expected primary-expression before '==' token extension/internal/pdfinput/pdf-parser.cpp:2318: error: expected primary-expression before '==' token extension/internal/pdfinput/pdf-parser.cpp:2318: error: expected primary-expression before '=' token
P.S. The pdf-parser's issues with the public vs. private parts of the poppler API have been the only real source of build failures for me over the past year. Perhaps r19370 is central to fixing that. Still, It would be nice if a config option allowed it to be skipped entirely when there's trouble.
(old, since fixed)
pdfinput/pdf-parser.cpp:2248: error: no matching function for call to GfxFont::getNextChar
pdf-input.cpp:544: error: '_preview_output_dev' was not declared in this scope
On Thu, Jul 31, 2008 at 03:18:47PM -0400, Jeff Kowalczyk wrote:
Inkscape svn trunk stopped building for me on Gentoo Linux ~x86 about two weeks ago, which corresponds somewhat with the last commit on xtension/internal/pdfinput/pdf-parser.cpp.
The build.log is huge, but available if it helps anyone debug.
# grep error: build.log extension/internal/pdfinput/pdf-parser.cpp:2259: error: expected primary-expression before '<<' token
That often indicates that there's an svn merge conflict in that file. Try doing svn revert extension/internal/pdfinput/pdf-parser.cpp (perhaps preceded by svn diff to check whether there are any deliberate changes of yours to that file that you want to keep).
You might also look at the three files pdf-parser.cpp.mine, and the two [usually] pdf-parser.cpp.r* files. (There can be more than two of them if you've done svn up without first resolving any conflicts.)
pdfinput/pdf-parser.cpp:2248: error: no matching function for call to GfxFont::getNextChar
I added a change that attempted to have the configure script detect which version of libpoppler is installed and to enable the appropriate code accordingly.
If you still get this error after addressing the `<<' error you describe above, then it may mean that the configure test needs tweaking.
pdf-input.cpp:544: error: '_preview_output_dev' was not declared in this scope
I don't remember seeing this one.
pjrm.
On Fri, Aug 01, 2008 at 10:27:20AM +1000, I wrote:
Try doing svn revert extension/internal/pdfinput/pdf-parser.cpp (perhaps preceded by svn diff to check whether there are any deliberate changes of yours to that file that you want to keep).
You might also look at the three files pdf-parser.cpp.mine, and the two [usually] pdf-parser.cpp.r* files.
Note that `svn revert' may well remove those files; do `svn revert' only once you're sure that you don't want to keep any of your changes to the file.
When I say `You might also look at the three files pdf-parser.cpp.*', what I actually mean is that you might do `diff -dup pdf-parser.cpp.rEARLIER pdf-parser.cpp.mine' to see your changes, and `diff -dup pdf-parser.cpp.r*' (assuming just two .r* files) to see the changes that have been made in svn. The top few entries of `svn log pdf-parser.cpp' may also be useful in understanding the .r* diffs -- particularly in this case.
If by chance you do have changes in that file that you want to keep, then once you've manually merged your changes and no longer need to pdf-parser.cpp.* files, you can do `svn resolved pdf-parser.cpp' to tell svn that pdf-parser.cpp now contains the desired merge of your changes and other people's changes in svn, and then svn will remove the pdf-parser.cpp.* files and will no longer flag pdf-parser.cpp as being in conflict.
pjrm.
On Fri, 01 Aug 2008 10:27:20 +1000, Peter Moulder wrote:
# grep error: build.log extension/internal/pdfinput/pdf-parser.cpp:2259: error: expected primary-expression before '<<' token
That often indicates that there's an svn merge conflict in that file. Try doing svn revert extension/internal/pdfinput/pdf-parser.cpp (perhaps preceded by svn diff to check whether there are any deliberate changes of yours to that file that you want to keep).
You're right of course. I'm familiar with the conflict, but I hadn't anticipated that being the case because I use the inkscape svn checkout only to build, never edit. The diff was as follows:
$ svn diff Index: src/extension/internal/pdfinput/pdf-parser.cpp =================================================================== --- src/extension/internal/pdfinput/pdf-parser.cpp (revision 19501) +++ src/extension/internal/pdfinput/pdf-parser.cpp (working copy) @@ -2207,7 +2207,7 @@ #ifdef POPPLER_NEW_GFXFONT Unicode *u = NULL; #else - Unicode u[8]; + Unicode *u = NULL; #endif double x, y, dx, dy, dx2, dy2, curX, curY, tdx, tdy, lineX, lineY; double originX, originY, tOriginX, tOriginY; @@ -2256,10 +2256,14 @@ len = s->getLength(); while (len > 0) { n = font->getNextChar(p, len, &code, +<<<<<<< .mine + &u, &uLen, +======= #ifdef POPPLER_NEW_GFXFONT &u, &uLen, /* TODO: This looks like a memory leak for u. */ #else u, (int)(sizeof(u) / sizeof(Unicode)), &uLen, +>>>>>>> .r19372 #endif &dx, &dy, &originX, &originY); dx = dx * state->getFontSize() + state->getCharSpace(); @@ -2309,10 +2313,14 @@ len = s->getLength(); while (len > 0) { n = font->getNextChar(p, len, &code, +<<<<<<< .mine + &u, &uLen, +======= #ifdef POPPLER_NEW_GFXFONT &u, &uLen, /* TODO: This looks like a memory leak for u. */ #else u, (int)(sizeof(u) / sizeof(Unicode)), &uLen, +>>>>>>> .r19372 #endif &dx, &dy, &originX, &originY);
Thanks again.
That's because sometime you edited the file extension/internal/pdfinput/pdf-parser.cpp at line 2259 and now, after a 'svn up', svn left some cruft there detailing the differences between your changes and the svn version. I usually delete the file and run 'svn up' again to restore the file.
Regards.
2008/7/31 Jeff Kowalczyk <jtk@...36...>:
Inkscape svn trunk stopped building for me on Gentoo Linux ~x86 about two weeks ago, which corresponds somewhat with the last commit on xtension/internal/pdfinput/pdf-parser.cpp.
The build.log is huge, but available if it helps anyone debug.
# grep error: build.log extension/internal/pdfinput/pdf-parser.cpp:2259: error: expected primary-expression before '<<' token extension/internal/pdfinput/pdf-parser.cpp:2259: error: expected primary-expression before '<<' token extension/internal/pdfinput/pdf-parser.cpp:2259: error: expected primary-expression before '<<' token extension/internal/pdfinput/pdf-parser.cpp:2259: error: expected primary-expression before '<' token extension/internal/pdfinput/pdf-parser.cpp:2259: error: expected primary-expression before '.' token extension/internal/pdfinput/pdf-parser.cpp:2261: error: expected primary-expression before '==' token extension/internal/pdfinput/pdf-parser.cpp:2261: error: expected primary-expression before '==' token extension/internal/pdfinput/pdf-parser.cpp:2261: error: expected primary-expression before '==' token extension/internal/pdfinput/pdf-parser.cpp:2261: error: expected primary-expression before '=' token extension/internal/pdfinput/pdf-parser.cpp:2316: error: expected primary-expression before '<<' token extension/internal/pdfinput/pdf-parser.cpp:2316: error: expected primary-expression before '<<' token extension/internal/pdfinput/pdf-parser.cpp:2316: error: expected primary-expression before '<<' token extension/internal/pdfinput/pdf-parser.cpp:2316: error: expected primary-expression before '<' token extension/internal/pdfinput/pdf-parser.cpp:2316: error: expected primary-expression before '.' token extension/internal/pdfinput/pdf-parser.cpp:2318: error: expected primary-expression before '==' token extension/internal/pdfinput/pdf-parser.cpp:2318: error: expected primary-expression before '==' token extension/internal/pdfinput/pdf-parser.cpp:2318: error: expected primary-expression before '==' token extension/internal/pdfinput/pdf-parser.cpp:2318: error: expected primary-expression before '=' token
P.S. The pdf-parser's issues with the public vs. private parts of the poppler API have been the only real source of build failures for me over the past year. Perhaps r19370 is central to fixing that. Still, It would be nice if a config option allowed it to be skipped entirely when there's trouble.
(old, since fixed)
pdfinput/pdf-parser.cpp:2248: error: no matching function for call to GfxFont::getNextChar
pdf-input.cpp:544: error: '_preview_output_dev' was not declared in this scope
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
participants (3)
-
Jeff Kowalczyk -
Pajarico -
Peter Moulder