Il giorno mer, 25/08/2010 alle 17.20 +0300, Markos Chandras ha scritto:
> On Wed, Aug 25, 2010 at 01:42:12PM +0200, Thilo Bangert wrote:
> > * QA Notice: Package has poor programming practices which may compile
> > * fine but exhibit random runtime failures.
> > * closefromtest.c:46: warning: implicit declaration of function
> > ‘closefrom’
> This is a rather common bug for 64bit arches
Actually no; the one common for 64bit arches is "implicit pointer
conversion" warning (which may be caused by an implicit declaration,
since implicit declarations default to int as return type!) that is
always fatal on 64-bit (it would crash the code as the returned pointer
would be crippled.
What this bug is about is rather the kind of errors that I've commented
on in ,  and  which is that they _may_ be related to macros or
functions that are not declared/defined by the current set of library
dependencies, and would then lead to unresolved undefined symbols, and
thus, to runtime failure.
> This is not only related to stricter but also related to CFLAGS ( having -ggdb
> and -Wall, produce same failures for me even if I don't use stricter )
> Diego, any ideas why this happens? -Wall & -ggdb produce extra output on
> warning that makes portage abort because of that? I always wondered why this
> is happening.
They are not issues for users to care much about, but if _you_ are
maintaining a package that have those warnings should probably go fix
them; upstream and in Gentoo; in my last blog post  I have noted that
we should really just use stricter for _our_ packages, not _all_
packages, as it makes it bothersome and lead to more people just
forgetting about stricter (I don't use it, for instance).
Diego Elio Pettenò — “Flameeyes”
If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/