Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=502387 Fridrich Strba <fridrich.st...@bluewin.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fridrich.st...@bluewin.ch --- Comment #7 from Fridrich Strba <fridrich.st...@bluewin.ch> 2009-05-26 10:47:01 EDT --- OK, I don't see how you want to change that. You need to run a programme to be sure that malloc(0) returns NULL or non-null. You have some other situations where you cannot determine something without actually running a programme, like allignments of types. The standard way of proceding is either to patch the system for known platform with values that we know to be true (I did this here http://svn.gnome.org/viewvc/evolution-data-server/trunk/configure.in?r1=9959&r2=9961 ) or to pre-populate the compile cache with values for tests that cannot be run. In this case, it is just to pre-fill the cache with: ac_cv_func_malloc_0_nonnull=yes -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@redhat.com http://www.redhat.com/mailman/listinfo/fedora-package-review
