This is the mail archive of the
mailing list for the glibc project.
glibc-2.8 and libiberty
- From: Peter Hjalmarsson <xake at rymdraket dot net>
- To: libc-help at sourceware dot org
- Date: Tue, 02 Sep 2008 10:48:33 +0200
- Subject: glibc-2.8 and libiberty
I have been playing around with glibc, FORTIFY_SOURCE and gcc.
After I installed glibc-2.8 I started to get problems with building gcc, gdb and binutils.
The thing they have in common (and the place of breakage) is libiberty.
Searching for a solution I found a mail on gcc-patches describing the problem and offers a solution .
>From the mail:
HAVE_DECL_ASPRINTF is computed with _GNU_SOURCE unset,
libiberty/floatformat.c sets _GNU_SOURCE and uses libiberty.h,
so asprintf is redeclared (/usr/include/stdio.h + libiberty.h)
Libiberty fails with the following message (gcc from svn, checkout date 20080902):
gcc -c -DHAVE_CONFIG_H -g -O2 -I. -I../.././libiberty/../include -W -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic ../.././libiberty/floatformat.c -o floatformat.o
In file included from ../.././libiberty/floatformat.c:40:
../.././libiberty/../include/libiberty.h:598: error: expected declaration specifiers or '...' before numeric constant
../.././libiberty/../include/libiberty.h:598: error: conflicting types for '__asprintf_chk'
/usr/include/bits/stdio2.h:135: error: previous declaration of '__asprintf_chk' was here
As I could not se any fix for this going anywhere I post my question here:
Is this something that is meant to be fixed in glibc, or is this something that should be fixed in libiberty?
And in the case of the latter: where should I report the bug (there are some projects containing libiberty,
but I never got really sure on what project is the "upstream")?