Summary: | implicit declaration of function ‘_doprnt’ in libiberty/vfprintf.c | ||
---|---|---|---|
Product: | gdb | Reporter: | Kamaraju Kusumanchi <kamaraju> |
Component: | build | Assignee: | Not yet assigned to anyone <unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | tromey, tromey |
Priority: | P2 | ||
Version: | 7.2 | ||
Target Milestone: | --- | ||
Host: | Target: | ||
Build: | Last reconfirmed: | ||
Attachments: | libiberty/config.log is attached |
Description
Kamaraju Kusumanchi
2011-06-15 04:58:28 UTC
It seems to me that vfprintf.c should not be compiled on a Debian box. I suspect the error occurs elsewhere. Maybe libiberty/config.log would be helpful. Created attachment 5794 [details]
libiberty/config.log is attached
As per the request, I am attaching the libiberty/config.log
I think the problem is in autoconf. libiberty uses AC_REPLACE_FUNCS and apparently this is not -Werror safe. From the log: configure:5913: checking for vfprintf configure:5913: i486-linux-gnu-gcc -o conftest -g -Werror conftest.c >&5 conftest.c:86:6: error: conflicting types for built-in function 'vfprintf' [-Werror] cc1: all warnings being treated as errors You could report this to the autoconf maintainers. Meanwhile, don't configure with -Werror. Not really a gdb bug, more of an autoconf thing and/or don't pass -Werror to configure. |