From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: xtscal fails + other Xorg init problems.
Date: Sun, 16 Aug 2009 21:38:33 +0200 [thread overview]
Message-ID: <4A886039.5050508@atmel.com> (raw)
In-Reply-To: <1250375020.5033.7.camel@utx.utx.cz>
Stanislav Brabec skrev:
> Ulf Samuelsson wrote:
>> Stanislav Brabec skrev:
>>> Well, there may be a problem in recipes. There is xcalibrate and
>>> libxcalibrate. Both provide the same library. Some recipes use
>>> xcalibrate in DEPENDS, some use libxcalibrate. libxcalibrate does not
>>> compile on images with xserver-kdrive.
>>>
>> I have looked through the code.
>> x11-image uses Xorg and libxcalibrate.
>>
>> There can be several reasons for this error message:
>>
>> 1) Xmalloc fails
>> 2) There is no extension XCALIBRATE
>> 3) There is an extension, but with different casing
>> XCALIBRATE is used by libxcalibrate.
>> if another name is used when it is added,
>> then there is a problem when queried.
>> The library is called libXcalibrate.so.
>
> 4) Both xcalibrate and libxcalibrate were populated to staging and one
> overwrites the other. .la files from one could "poison" the other.
> To identify this possible problem, please look at your build logs or
> check your tmp/work. If both xcalibrate and libxcalibrate were staged,
> you may expect problem.
>
> If only one of the was built, it is a different problem.
>
I did a patch to xtscal to print out all X11 Extensions
if the XInitExtension fails, and there is no XCALIBRATE
extension loaded.
The at91 confs have:
PREFERRED_PROVIDER_xserver = "xserver-kdrive"
This should be:
PREFERRED_PROVIDER_xserver = "xserver-kdrive-common"
Instead of kdrive, I am using the xorg server, and I saw
a comment that libXcalibrate does not work on xorg.
I will try with xerver-krive-common and see how it goes...
>
> ________________________________________________________________________
> Stanislav Brabec
> http://www.penguin.cz/~utx/zaurus
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2009-08-16 19:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-16 20:16 [PATCH] xserver-kdrive-common: fixed xTs_Calibrate script name Ihar Hrachyshka
2009-05-16 20:39 ` Koen Kooi
2009-05-16 20:59 ` Phil Blundell
2009-05-18 12:45 ` Florian Boor
2009-08-15 9:15 ` xtscal fails + other Xorg init problems Ulf Samuelsson
2009-08-15 9:37 ` Phil Blundell
2009-08-15 10:06 ` Stanislav Brabec
2009-08-15 11:51 ` Ulf Samuelsson
2009-08-15 22:23 ` Stanislav Brabec
2009-08-16 19:38 ` Ulf Samuelsson [this message]
2009-08-17 8:51 ` Phil Blundell
2009-08-16 21:33 ` Phil Blundell
2009-08-17 10:20 ` Ulf Samuelsson
2009-08-17 16:30 ` Stanislav Brabec
2009-08-17 23:22 ` Stanislav Brabec
2009-08-18 10:26 ` Stanislav Brabec
2009-08-18 10:34 ` Koen Kooi
2009-08-18 11:45 ` Phil Blundell
2009-08-18 15:22 ` Ulf Samuelsson
2009-08-18 18:35 ` Stanislav Brabec
2009-08-19 15:40 ` Ulf Samuelsson
2009-08-15 9:39 ` Phil Blundell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A886039.5050508@atmel.com \
--to=ulf.samuelsson@atmel.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox