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