On Friday 13 November 2009 00:06:53 Marcus Wanner wrote: > On 11/12/2009 5:01 PM, Alan McKinnon wrote: > > On Thursday 12 November 2009 23:51:32 Marcus Wanner wrote: > >> On 11/12/2009 4:43 PM, Alan McKinnon wrote: > >>> On Thursday 12 November 2009 20:21:41 Marcus Wanner wrote: > >>>> On 11/12/2009 12:56 PM, Roy Wright wrote: > >>>>> On Nov 12, 2009, at 11:24 AM, Marcus Wanner wrote: > >>>>>> On 11/12/2009 11:55 AM, Roy Wright wrote: > >>>>>>> Disable (either temporary or permanent) the "xinerama" USE flag. > >>>>>> > >>>>>> Me or Alan? > >>>>> > >>>>> OP > >>>>> > >>>>> As a suggestion for a work around for the compile issue. If you > >>>>> temporarily disable xinerama, then the build should proceed. Then if > >>>>> you need xinerama, enable the USE flag and build again. > >>>> > >>>> I don't have the xinerama use flag set anywhere...I don't know what it > >>>> is, I don't want it, and I hopefully don't need it. > >>>> > >>>> I did put -xinerama in my use flag variable and try again, we'll see > >>>> how that works...btw, I have switched to xorg-server-1.7.1, since I > >>>> don't want to go through upgrading more than I need to. > >>> > >>> libXinerama and xineramaproto are hard-DEPENDS on quite a few things: > >>> > >>> $ equery depends libXinerama > >>> * Searching for libXinerama ... > >>> app-emulation/vmware-player-2.5.3.185404 (x11-libs/libXinerama) > >>> app-office/openoffice-3.1.1 (x11-libs/libXinerama) > >>> > >>> > >>> $ equery depends xineramaproto > >>> * Searching for xineramaproto ... > >>> app-office/openoffice-3.1.1 (x11-proto/xineramaproto) > >>> x11-base/xorg-server-1.7.1 (>=x11-proto/xineramaproto-1.1.3) > >>> x11-libs/libXinerama-1.1 (>=x11-proto/xineramaproto-1.2) > >> > >> I'm really sorry for my noobishness, but could you explain exectly what > >> "proto" means in this context and how it applies to me? > > > > Xorg used to be one ginormous complicated package. It is now a ginormous > > complicated collection of small packages, each one simple. > > > > This is supposed to make someone's life easier. In reality it moves the > > complexity from point A to point B, where you still have to deal with it > > :-) > > > > The -proto packages are the protocol header files. They tell the compiler > > how to build other packages that use those protocols. They are separate > > because Ubuntu users don't need them - they don't compile stuff. You do, > > so you need them, and the Xorg ebuilds pull them in. > > Thank you. Do those need to be recompiled when something depending on > them is?
Not usually. You don't compile headers, you just unpack them from the archive so other apps can use them. But, this is software and we never really expect stuff to actually work. So some ebuilds might actually build something. In which case, it safer to just emerge them anyway. Those packages take just a few seconds to install -- alan dot mckinnon at gmail dot com
