Is something broken ? (failed compile of libX11-X11R7)

[Rod Whitby]

>> You may want to also look in the OpenEmbedded bugzilla
>> (http://bugs.openembedded.org/), since this is not an openmoko-modified
>> package (i.e. it's not in the OpenMoko overlay SVN repository).
>>
>> You'll probably get better answers to this bug report on the
>> OpenEmbedded mailing list
>>
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 
> well a simillar bug was reported on openembedded list but reffered to
> openmoko by openembedded devels. Here is the openembedded bug report
> 
> http://bugs.openembedded.org/show_bug.cgi?id=1949
> 
> look at  the resolution, it says report it to openmoko.

Well, the simple fact is that libX11 is a standard OpenEmbedded package,
which builds fine for many people using OpenEmbedded, and also builds
fine for many people using the OpenMoko distribution which is based on
Openembedded.

So you have a problem which is isolated to a small number of people.

That means that it's unlikely to be solved unless one of those small
number of people is motivated to work out what is different about their
host environment compared to the host environments of the thousands (yes
*thousands*) of other people for whom this package compiles without error.

How do you go about doing that?  Here's some suggestions:

1) Try to reproduce the problem using the Angstrom distribution (which
also uses OpenEmbedded, and which is the distribution which is fully
supported by the OpenEmbedded core team of developers), and if you are
able to reproduce it there, then you can report it to the OpenEmbedded
bugzilla without fear of someone closing it simply because it mentions
OpenMoko.

2) Find out exactly who else is experiencing the problem, and see if you
 can identify some common factor in that group which differentiates it
from the much larger group of people who are not having a problem.

3) Find someone who is not having the problem (perhaps someone who is
building this in a virtual machine environment like VMWare) and
replicate their environment exactly.  Once you have a working build and
a non-working build, then examine the differences to find where it breaks.

Unfortunately, since this works for *many* other people, it's unlikely
that anyone is going to be motivated to solve it for you (unless you are
a developer who has some rare skill or talent that the project cannot do
without).  I know that will be hard to hear, but that's life in open
source development.

Alternatively, you can pay someone to solve the problem for you ...

-- Rod