Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 365457 - net-print/cups-1.4.6-r1: failes to build under a user mode linux image b/c of missing /usr/src/linux
Summary: net-print/cups-1.4.6-r1: failes to build under a user mode linux image b/c of...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Printing Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-30 20:45 UTC by Toralf Förster
Modified: 2011-05-01 16:20 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Toralf Förster gentoo-dev 2011-04-30 20:45:42 UTC
I chrooted into the UML image and tried to upgrade @world, nevertheless I'm sure it won't work even when i rally start that image and login into it ...

Reproducible: Always
Comment 1 Toralf Förster gentoo-dev 2011-04-30 20:49:45 UTC
BTW the ebuild says : "* cups-1.4.6 requires the USB_PRINTER support disabled."

But at least at my (host) system I need the kernel module for the USB printer Lexmark z617, b/c otherwise a "$>date | lpr" won't work.
What works for me at the Gentoo host system is to put this line "net-print/cups  -usb" into /etc/portage/package.use/misc and to have the kernel module option enabled and the module "usblp" loaded.
Comment 2 Tomáš Chvátal (RETIRED) gentoo-dev 2011-05-01 15:09:51 UTC
How about reading the whole message.


 eerror "Your usb printers will be managed via libusb."
 eerror "Note that this interface still has issues so alternatively"
 eerror "you should just disable usb useflag on ${P}."
 eerror "${P} requires the USB_PRINTER support disabled."

It quite clearly state that if you want to use USB_PRINTER you should just disable the usb useflag.

Closing as it is not a bug.
Comment 3 Toralf Förster gentoo-dev 2011-05-01 16:20:34 UTC
(In reply to comment #2)
> Closing as it is not a bug.
Well, probably I shouldn't put in an additional comment another topic onto the table - OTOH what's about the original problem I reported ? That is a bug, isn't it ?