On Fri, 2009-01-02 at 19:03 +1030, Rod Whitby wrote: > The README on downloads.freesmartphone.org will point you to the build logs, > from where you can determine which OE packages are causing the builds to > fail. Then you can raise bug reports for those failures and when they are > all fixed the images will be built again. > Unfortunately, I don't have a working openmoko phone for some time now, so I > have little incentive to look into it .... > If the build logs indicate a problem with the autobuilder rather than just > the normal broken packages, feel free to email directly and I'll fix the > autobuilder. But it's usually just the packages that are broken, not the > autobuilder itself. > -- Rod
Okay, however I'm having trouble interpreting what I see on tinderbox. At the moment om-gta02 has started to show up again. om-gta01 is failing at frameworkd and the task do_fetch fails. Clicking on "failed" I see a "Package Information." Under Depends there are two packages that do not have hyperlinks; virtual/arm-angstrom-linux-gnueabi-gcc and virtual/libc Is it safe to say this is where it is failing? digger
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list [email protected] https://lists.openmoko.org/mailman/listinfo/devel
