When building gcc-4.0.2 I find many warnings about redefined HAVE_DECL_GETOPT.
Are they what we expect?

version: 4.0.2 20050711 (prerelease)
configuration: ../gcc/configure --prefix=/home/wf/local
--enable-languages=c,f95
host and target: i686-pc-linux-gnu

#grep warning buildlog.txt
[snip]
./auto-host.h:250:1: warning: "HAVE_DECL_GETOPT" redefined
../../gcc/gcc/tsystem.h:40:1: warning: this is the location of the previous
defi
./auto-host.h:250:1: warning: "HAVE_DECL_GETOPT" redefined
../../gcc/gcc/tsystem.h:40:1: warning: this is the location of the previous
defi
./auto-host.h:250:1: warning: "HAVE_DECL_GETOPT" redefined
../../gcc/gcc/tsystem.h:40:1: warning: this is the location of the previous
defi
./auto-host.h:250:1: warning: "HAVE_DECL_GETOPT" redefined
../../gcc/gcc/tsystem.h:40:1: warning: this is the location of the previous
defi
./auto-host.h:250:1: warning: "HAVE_DECL_GETOPT" redefined
../../gcc/gcc/tsystem.h:40:1: warning: this is the location of the previous
defi
./auto-host.h:250:1: warning: "HAVE_DECL_GETOPT" redefined
../../gcc/gcc/tsystem.h:40:1: warning: this is the location of the previous
defi
./auto-host.h:250:1: warning: "HAVE_DECL_GETOPT" redefined
../../gcc/gcc/tsystem.h:40:1: warning: this is the location of the previous
defi
./auto-host.h:250:1: warning: "HAVE_DECL_GETOPT" redefined
../../gcc/gcc/tsystem.h:40:1: warning: this is the location of the previous
defi
./auto-host.h:250:1: warning: "HAVE_DECL_GETOPT" redefined
../../gcc/gcc/tsystem.h:40:1: warning: this is the location of the previous
defi
./auto-host.h:250:1: warning: "HAVE_DECL_GETOPT" redefined
../../gcc/gcc/tsystem.h:40:1: warning: this is the location of the previous
defi
./auto-host.h:250:1: warning: "HAVE_DECL_GETOPT" redefined
../../gcc/gcc/tsystem.h:40:1: warning: this is the location of the previous
defi
[snip]


Best Regards,
Feng Wang

--
Creative Compiler Research Group,
National University of Defense Technology, China.

__________________________________________________
赶快注册雅虎超大容量免费邮箱?
http://cn.mail.yahoo.com

Reply via email to