Fail to compile busybox 1.3.0 in gcc 3.2.2

[Yuwen Dai]

On 12/16/06, steven at nchc.org.tw <steven at nchc.org.tw> wrote:
>
> I failed to compile busybox 1.3.0 in gcc 3.2.2, this is in RedHat 9. Does
> anyone has same problem ?
>
> ~/tmp/busybox/busybox-1.3.0>gcc -v
> Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/specs
> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
> --infodir=/usr/share/info --enable-shared --enable-threads=posix
> --disable-checking --with-system-zlib --enable-__cxa_atexit
> --host=i386-redhat-linux
> Thread model: posix
> gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
>
> ~/tmp/busybox/busybox-1.3.0>make
> ...
> CC      libbb/messages.o
> CC      libbb/mode_string.o
> CC      libbb/mtab.o
> CC      libbb/mtab_file.o
> CC      libbb/obscure.o
> CC      libbb/parse_mode.o
> CC      libbb/perror_msg.o
> CC      libbb/perror_msg_and_die.o
> CC      libbb/perror_nomsg.o
> cc1: warnings being treated as errors
> libbb/perror_nomsg.c: In function `bb_perror_nomsg':
> libbb/perror_nomsg.c:15: warning: null format string
> make[1]: *** [libbb/perror_nomsg.o] Error 1
> make: *** [libbb] Error 2


The source file looks like this:
#include "libbb.h"

void bb_perror_nomsg(void)
{
        /* Ignore the gcc warning about a null format string. */
        bb_perror_msg(NULL);
}

It seems the author is aware that awarning will be here.  However, I use GCC
3.3.5 on Debian, without having such warning.

May be you can find a option to disable such warning in the manual of
gcc3.2.2?

-- 
yuwen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/busybox/attachments/20061217/d0b3f8d3/attachment.htm