9.10.2014 17:45, Vincent Danjean kirjoitti: > 1) Debian bugs > Would you agree that I subscribe the ML itself (ie > [email protected] ) to the BTS so that all Debian bug > reports > will be sent to the ML ? > Of course, if any bugs are only related to the packaging, I will handle > them. But I suspect that most bugs will be for upstream and I would > probably be more efficient that the ML itself receive directly the mail.
Please use the pocl-commits-list instead. Let's try to keep this list for discussions only. > 2) the BTS also offer the possibility to receive mail about build for > each Debian architecture. Would it be interested that the ML is also > subscribed to these mails ? Same here. > 3) pocl provides and install utlist.h. It is already packaged in Debian > in uthash-dev (see #764571) > I will remove utlist.h from the libpoclu-dev package. I was considering > adding a dependency but I fail to see why utlist.h is needed. > If utlist.h is needed by external applications but not by libpoclu itself, > I will not add the dependency. It should not be required. > 4) #764561 and #764563 show that there is problem on most > architectures. ... > I will do an upload this evening, at least to close #764571. > I will put LLV_HOST_CPU for amd64, armhf and any other you > suggest me. And I will see later for the reminding architectures. Probably Erik has the best idea for x86-64 and i386 (I think he suggested using i486 earlier). Kalle has the best idea for the arm targets, and perhaps guesses for powerpcs (which is obsoleted due to lack of LLVM activity). For s390x we do not have a maintainer. The make check issue for i386 seems like a genuine upstream pocl or LLVM bug. Can I get the testsuite.log? With this (as most of them work) it is probably best to just set them XFAILs and add issues in github. Or just see if it goes away with i486 as the target (in case it's an LLVM codegen bug, it might well just do that). The ppc6el issue looks like something related to gcc 4.9 and its stdlib? PowerPC (at least ppc32, if I've understood correctly) has degraded due to lack of LLVM maintainership. Most of its tests seem to fail in the builder. testsuite.log would help figuring if it's something simpler than this. If no one steps to maintain pocl and LLVM for it, there's probably no point building pocl for it in Debian. -- Pekka ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ pocl-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pocl-devel
