tags 492377 + help reassign 492377 qa.debian.org thanks dann frazier dixit:
> Function `strcasestr' implicitly converted to pointer at ] scn.c:4 I suggest you read your eMail INBOX, as I already wrote to you in Message-ID: <[EMAIL PROTECTED]> that this is a FALSE POSITIVE and that I request help for how to deal with this bug in your automated checker. Excerpt from that eMail, for the archives: │http://buildd.debian.org/fetch.cgi?pkg=mksh&arch=ia64&ver=35.2-1&stamp=1216828593&file=log&as=raw │ │The mksh build process involves a configuration and a build step, similar │to what GNU autoconf does. (In fact, it does this twice, once for the │normal glibc binary, once for a small dietlibc binary.) However, in con- │trast to GNU autoconf, the configuration step is verbose. │ │The autoconf check for strcasestr() is expected to return no with dietlibc, │because the function is not defined. Since it is not declared in any sy- │stem header file (of dietlibc), we have no prototype, so the compile test │also triggers a false positive on the warning: │Diagnostic output from the autoconf checks is prepended by “] ” (and always │occurs on the file scn.c, akin to conftest.c in GNU autoconf). │ │What do you suggest to remove this false positive while keeping the confi- │guration process as warning-free as possible? As for a possible solution, I don’t think that adding an exemption of mksh to the checker is worth the effort, but I can’t think of a modifi- cation to the test that would NOT trigger the warning while staying warning-free in all other cases (as the test is EXPECTED to fail on Debian with Fefe’s dietlibc). Maybe I could play some sed magic to fool the regex your scanner uses, so that it doesn’t recognise warnings emitted during the configuration process? This would then be a Debian- specific kludge and NOT go in upstream. If you have any BETTER solutions, please let me know. bye, //mirabilos -- Sometimes they [people] care too much: pretty printers [and syntax highligh- ting, d.A.] mechanically produce pretty output that accentuates irrelevant detail in the program, which is as sensible as putting all the prepositions in English text in bold font. -- Rob Pike in "Notes on Programming in C" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
