#6131: cups-2.0.2
-------------------------+--------------------------
 Reporter:  bdubbs@…     |       Owner:  blfs-book@…
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  7.7
Component:  BOOK         |     Version:  SVN
 Severity:  normal       |  Resolution:
 Keywords:               |
-------------------------+--------------------------

Comment (by fo):

 There is a problem: cups-filters-1.0.62 does not compile with
 poppler-0.31.0. It needs to be reinstalled, after cups.

 I had to downgrade poppler to 0.30.0.

 Problem is (some edit done):

 {{{
 ...
 /usr/include/poppler/Object.h:260:10: warning:
 ISO C++ 1998 does not support ‘long long’ [-Wlong-long]
      long long int64g;           //   64-bit integer
           ^
 filter/pdftoopvp/OPVPOutputDev.cxx: In member function
 ‘void OPVPOutputDev::startDoc(XRef*)’:
 filter/pdftoopvp/OPVPOutputDev.cxx:281:23: error: ‘class GlobalParams’
 has no member named ‘getAntialias’
          globalParams->getAntialias());
                        ^
 Makefile:3426: recipe for target 'pdftoopvp-OPVPOutputDev.o' failed
 make[1]: *** [pdftoopvp-OPVPOutputDev.o] Error 1
 make[1]: Leaving directory '/tmp//cups-filters-1.0.62'
 Makefile:1647: recipe for target 'all' failed
 make: *** [all] Error 2
 }}}

 In poppler-0.30.0, this was defined:

 /usr/include/poppler/GlobalParams.h:  GBool getAntialias();

 but was removed, in poppler-0.31.0.

 Actually this header has suffered a large amount of modifications: removed
 53 lines and added 13, so, less 40 lines.

 This bug is new (of course) and has not yet been solved:

 [https://bugs.linuxfoundation.org/show_bug.cgi?id=1254]

 Now, we have a big problem, if there is no solution before freeze.

-- 
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/6131#comment:2>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to