As from 'cups' 1.6, many filters and drivers got removed to a separate
package, 'cups-filters'. This requires 'qpdf'.

These two packages are now required for printing.

I can compile them natively ok, however in T2 x86_64 generic build,
qpdf 5.1.2 fails:

/bin/bash ./libtool --quiet --mode=compile g++ -g -O2 -Wold-style-cast
-Wall -MD -MF libqpdf/build/SecureRandomDataProvider.tdep -MP
-Iinclude -Ilibqpdf  -c libqpdf/SecureRandomDataProvider.cc -o
libqpdf/build/SecureRandomDataProvider.o; sed -e 's/\.o:/.lo:/' <
libqpdf/build/SecureRandomDataProvider.tdep >
libqpdf/build/SecureRandomDataProvider.dep
/bin/bash ./libtool --quiet --mode=compile g++ -g -O2 -Wold-style-cast
-Wall -MD -MF libqpdf/build/qpdf-c.tdep -MP -Iinclude -Ilibqpdf  -c
libqpdf/qpdf-c.cc -o libqpdf/build/qpdf-c.o; sed -e 's/\.o:/.lo:/' <
libqpdf/build/qpdf-c.tdep > libqpdf/build/qpdf-c.dep
/bin/bash ./libtool --quiet --mode=compile g++ -g -O2 -Wold-style-cast
-Wall -MD -MF libqpdf/build/rijndael.tdep -MP -Iinclude -Ilibqpdf  -c
libqpdf/rijndael.cc -o libqpdf/build/rijndael.o; sed -e 's/\.o:/.lo:/'
< libqpdf/build/rijndael.tdep > libqpdf/build/rijndael.dep
/bin/bash ./libtool --quiet --mode=compile gcc -g -O2 -Wall -MD -MF
libqpdf/build/sha2.tdep -MP -Iinclude -Ilibqpdf  -c libqpdf/sha2.c -o
libqpdf/build/sha2.o; sed -e 's/\.o:/.lo:/' < libqpdf/build/sha2.tdep
> libqpdf/build/sha2.dep
libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'
/bin/bash: libqpdf/build/sha2.tdep: No such file or directory

That last compile step seems to be the problem. libtool is confused
whether it should be using g++ or gcc.
gcc is the wrong choice, I think.

Does anyone know, is there someway that T2 can force use of g++ in
this kind of circumstance? (if that is the problem)

Regards,
Barry

P.S.
Here is a reference that explains about cups-filters:

http://www.linuxfoundation.org/collaborate/workgroups/openprinting/cups-filters

LFS page:

http://www.linuxfromscratch.org/blfs/view/svn/pst/cups-filters.html



----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2

Reply via email to