<div dir="ltr">Hi Jan, <br><div class="gmail_extra"><br>2013/1/10 Jan Holzhueter <span dir="ltr"><<a href="mailto:jh@opencsw.org" target="_blank">jh@opencsw.org</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hi,<br>
I did brake it :)<br>
<br>
package.StdoutSyntaxError: Could not parse<br>
'/tmp/pkg_v0EICf/CSWffmpeg/root/opt/csw/bin/amd64/ffmpeg: warning:<br>
hardware capability (CA_SUNW_HW_1) unsupported: 0x100 [ AMD_3DNow ]'<br>[...]<br>
<br></blockquote><div><br></div><div>What a nice error message ! (this wil be improved soon ;) ).</div><div><br></div><div>This error happens because ldd encountered an unexpected line.</div><div>
In that case, we should figure out if this line is the sign of a problem or not:</div><div> - if this is not a problem, we should ignore it when parsing ldd output (modification to be done in checkpkg code),</div><div> - if this is a problem:</div>
<div>
- either we let the error be raised so that the maintainer is warned that something is wrong,</div><div> - or better we store the information in the checkpkg database and add a real check about this issue.</div>
<div><br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Don't know how it gets AMD_3DNow but thats fine too :)<br></blockquote><div><br></div><div>Well I am not sure it is fine. </div><div>It usually means that, to be run, your binary requires a system with hardware capability AMD_3DNOW.</div>
<div>See: <a href="http://docs.oracle.com/cd/E19082-01/819-0690/chapter2-20/index.html" target="_blank">http://docs.oracle.com/cd/E19082-01/819-0690/chapter2-20/index.html</a></div><div><br></div><div>I am not sure we want that for our binaries. Are there still a lot of computers without this capability ?<br>
</div><div><br></div><div>But maybe this is just an optional feature, I have to check exactly how it works.</div><div>Are you able to run the resulting binary on a system without AMD_3DNOW capabilites ?</div><div>
<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
package is ffmpeg if you want to test it.<br>
<br></blockquote><div><br></div><div>Do I have a direct access to the location where you built it so I can skip the building step ?</div><div><br></div><div>Yann</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Greetings<br>
Jan<br>
<br>
<br>
<br>
Am 03.01.13 22:27, schrieb Yann Rouillard:<br>
<div><div>> Hi everybody,<br>
><br>
> I proposed some time ago to implement new checkpkg checks in order to<br>
> detect binaries not honouring the new direct binding constraint or<br>
> having unused libraries dependencies:<br>
> <a href="http://lists.opencsw.org/pipermail/maintainers/2012-August/017126.html" target="_blank">http://lists.opencsw.org/pipermail/maintainers/2012-August/017126.html</a> and <a href="http://lists.opencsw.org/pipermail/maintainers/2012-August/017158.html" target="_blank">http://lists.opencsw.org/pipermail/maintainers/2012-August/017158.html</a><br>
><br>
> Well, as always, it took longer than expected but with the help and<br>
> advices of Maciej, I will eventually be able to commit the new tests on<br>
> the main branch the day after tomorrow.<br>
><br>
> These new checks will probably not change anything or trigger new<br>
> warnings for your package, except if your build system doesn't correctly<br>
> take into account the LD_OPTIONS default variable defined by GAR.<br>
> In that case, you will probably have one the two new checkpkg errors<br>
> documented here:<br>
> <a href="http://wiki.opencsw.org/checkpkg-error-tags#no-direct-binding" target="_blank">http://wiki.opencsw.org/checkpkg-error-tags#no-direct-binding</a><br>
> <a href="http://wiki.opencsw.org/checkpkg-error-tags#soname-unused" target="_blank">http://wiki.opencsw.org/checkpkg-error-tags#soname-unused</a><br>
><br>
> An important note: ldd is used to gather some information about<br>
> binaries. As ldd only work on binaries of the same architecture, this<br>
> means that the package content analysis step can now only be done on a<br>
> server with the same architecture as the package checked.<br>
> The real check step however can still be performed from anywhere.<br>
><br>
><br>
> These new checks required to add new information about symbols and<br>
> linkage in the checkpkg database. This information can now easily be<br>
> used to create others checks related to linkage, symbol and interfaces.<br>
> For exemple I also added a new test to detect if a binary is using a<br>
> forbidden version<br>
> interface: <a href="http://wiki.opencsw.org/checkpkg-error-tags#forbidden-version-interface-dependencies" target="_blank">http://wiki.opencsw.org/checkpkg-error-tags#forbidden-version-interface-dependencies</a><br>
><br>
> Unfortunately this also requires to re-import all the existing packages<br>
> to in the database to gather the symbols and linkage information from<br>
> previous packages.<br>
> I will begin this operation starting from now, it takes around 18h and<br>
> can be done live without preventing maintainers to upload new packages.<br>
> However, at the end, I will update the db schema version and commit the<br>
> new code. After this, you will have to svn update your gar build system<br>
> or it will complains about db schema version difference.<br>
> The procedure followed is described on the<br>
> wiki: <a href="http://wiki.opencsw.org/checkpkg#toc" target="_blank">http://wiki.opencsw.org/checkpkg#toc</a><br>
</div></div>> <<a href="http://wiki.opencsw.org/checkpkg#toc8" target="_blank">http://wiki.opencsw.org/checkpkg#toc8</a>><br>
<div>><br>
> I'll keep you updated as soon as it is finished.<br>
><br>
> If you have any question, don't hesitate.<br>
><br>
><br>
> BTW, happy New Year to everybody !<br>
><br>
><br>
> Yann<br>
><br>
><br>
</div>> _______________________________________________<br>
> maintainers mailing list<br>
> <a href="mailto:maintainers@lists.opencsw.org" target="_blank">maintainers@lists.opencsw.org</a><br>
> <a href="https://lists.opencsw.org/mailman/listinfo/maintainers" target="_blank">https://lists.opencsw.org/mailman/listinfo/maintainers</a><br>
> .:: This mailing list's archive is public. ::.<br>
><br>
<br>
_______________________________________________<br>
maintainers mailing list<br>
<a href="mailto:maintainers@lists.opencsw.org" target="_blank">maintainers@lists.opencsw.org</a><br>
<a href="https://lists.opencsw.org/mailman/listinfo/maintainers" target="_blank">https://lists.opencsw.org/mailman/listinfo/maintainers</a><br>
.:: This mailing list's archive is public. ::.<br>
</blockquote></div><br></div></div>