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