Failed to compile cups (on Debian using dpkg-buildpackage)

I downloaded the cups source from apt-get source cups

and I am trying to compile it with dpkg-buildpackage

. Compilation failed with an error:

PASS: All job control files purged.
PASS: Printer 'Test1' correctly produced 55 page(s).
PASS: Printer 'Test2' correctly produced 23 page(s).
PASS: 135 requests logged.
PASS: CUPS-Get-Default not logged.
PASS: 0 emergency messages.
PASS: 0 alert messages.
PASS: 0 critical messages.
FAIL: 19 error messages, expected 18.
E [16/Oct/2014:15:48:55.461975 +0200] Returning IPP client-error-bad-request for Get-Jobs (no URI) from localhost
E [16/Oct/2014:15:48:55.462540 +0200] Missing attributes-natural-language attribute
E [16/Oct/2014:15:48:55.462577 +0200] Missing printer-uri, job-uri, or ppd-name attribute
E [16/Oct/2014:15:48:55.462651 +0200] Returning IPP client-error-bad-request for Get-Jobs (no URI) from localhost
E [16/Oct/2014:15:48:55.463161 +0200] Missing attributes-charset attribute
E [16/Oct/2014:15:48:55.463192 +0200] Missing attributes-natural-language attribute
E [16/Oct/2014:15:48:55.463228 +0200] Missing printer-uri, job-uri, or ppd-name attribute
E [16/Oct/2014:15:48:55.463303 +0200] Returning IPP client-error-bad-request for Get-Jobs (no URI) from localhost
E [16/Oct/2014:15:48:55.463831 +0200] Missing attributes-charset attribute
E [16/Oct/2014:15:48:55.463862 +0200] Missing attributes-natural-language attribute
E [16/Oct/2014:15:48:55.463898 +0200] Missing printer-uri, job-uri, or ppd-name attribute
E [16/Oct/2014:15:48:55.463981 +0200] Returning IPP client-error-bad-request for Get-Jobs (no URI) from localhost
E [16/Oct/2014:15:48:55.464499 +0200] Missing printer-uri, job-uri, or ppd-name attribute
E [16/Oct/2014:15:48:55.464590 +0200] Returning IPP client-error-bad-request for Get-Jobs (no URI) from localhost
E [16/Oct/2014:15:48:55.465803 +0200] Returning IPP client-error-bad-request for Get-Jobs (ipp://localhost:8631/jobs) from localhost
E [16/Oct/2014:15:48:55.466380 +0200] Returning IPP server-error-version-not-supported for Get-Jobs (no URI) from localhost
E [16/Oct/2014:15:48:55.522710 +0200] Returning IPP client-error-bad-request for Print-Job (ipp://localhost:8631/printers/Test1) from localhost
E [16/Oct/2014:15:49:02.558807 +0200] Returning IPP client-error-too-many-subscriptions for Create-Printer-Subscription (ipp://localhost:8631/printers/Test1) from localhost
E [16/Oct/2014:15:49:13.164121 +0200] [cups-deviced] PID 8234 (usb) crashed on signal 11!
E [16/Oct/2014:15:49:13.164484 +0200] [cups-deviced] PID 8235 (snmp) stopped with status 1!
PASS: 9 warning messages.
PASS: 0 notice messages.
PASS: 787 info messages.
PASS: 9755 debug messages.
PASS: 19774 debug2 messages.

1 tests failed.
Log files can be found in /tmp/cups-martin/log.
A HTML report was created in /tmp/cups-martin/cups-str-1.5-2014-10-16-martin.html.

Copies of the error_log and cups-str-1.5-2014-10-16-martin.html files are in
/home/martin/src/debian/cups-1.5.3/test.

make[1]: *** [check] Error 1
make[1]: Leaving directory `/home/martin/src/debian/cups-1.5.3'
make: *** [debian/stamp-makefile-check] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

      

I do not know what happened. I have all installed dependencies installed.

I am using Debian Wheezy

Can anyone please help?

+3


source to share


2 answers


apt-get build-dep cups

should be running to get all build dependencies for cups. I know you are saying that you installed all the dependencies, but since you didn’t say how you did it, I am providing this command as the mechanism I would use to do this.

Many things come to mind. Some packages don't build well when run as a user root

(you won't find an official source that talks about this, but I've made this observation over the years of building packages on Debian). I usually build software as a regular user, but using fakeroot

. Since I prefer to use fakeroot

to build packages, I make sure fakeroot is installed via apt-get install fakeroot

. Whereas a non-root user I would do apt-get source cups

and then typical dpkg-buildpackage -b -us -uc -rfakeroot

to create binaries on a Debian system. I managed to create Cups 1.5.3 on my Debian Wheezy system here without any problem as a non-root user.

I was able to try this build as root

and interestingly enough I cups

got stuck during tests when trying to run the scheduler. This issue did not exist as a non-root user. Although what happened on my system did not cause the same resulting error as my tests never ran out at all!

I would recommend trying building with fakeroot

as a non-root user if you haven't already.

Specifically for your debug output, I find this curious:

[cups-deviced] PID 8234 (usb) crashed on signal 11!



I am wondering if during the tests, the problem with the USB printer device is causing your error. Do you have a USB printer connected directly to your system? If so, try disabling it and building. I am wondering if a problem in the cup-device subsystem specific to a specific USB printer occurs as a result of a crash cups

.

I was lucky enough to find this bug report of a similar problem with the cup device and signal 11 (on an older Ubuntu based system - Debian) .This is an older bug that seems to have been fixed, but I'm wondering if there are other problems. which are still a problem. The error had the following:

But for one reason or another, Ubuntu 9.10 and 10.04 no longer recognize the existence of USB printers. It doesn't recognize my HP Laserjet 4 and probably doesn't recognize other USB printers either.

It then provides this in an error log, which is similar to the errors you see during your tests when creating cups:

Architecture: amd64
CupsErrorLog:
 E [18/Apr/2010:09:43:44 -0600] [cups-deviced] PID 1768 (usb) crashed on signal 11!
 E [18/Apr/2010:09:46:36 -0600] [cups-deviced] PID 1817 (usb) crashed on signal 11!

      

+3


source


Until I can tell you what exactly is wrong, I can point you in the right direction.
What you are seeing is dropping the unit test for ipptool.



You might want to look into this further, perhaps starting at this link

+1


source







All Articles