From: Hui Zhu <teawater@gmail.com>
To: dj@sourceware.org
Cc: gdb@sourceware.org
Subject: Re: Got some error with cvs-head
Date: Sat, 25 Jul 2009 14:18:00 -0000 [thread overview]
Message-ID: <daef60380907250717w4401c8a2ve7f55d34d970ed5@mail.gmail.com> (raw)
In-Reply-To: <daef60380907250201m243c1b37m9004e91a2eefa636@mail.gmail.com>
It's OK with me now. Thanks DJ.
Hui
On Sat, Jul 25, 2009 at 17:01, Hui Zhu<teawater@gmail.com> wrote:
> And others:
>
> gcc -DHAVE_CONFIG_H -I. -I../../src/binutils -I. -I.
> -I../../src/binutils -I../bfd -I../../src/binutils/../bfd
> -I../../src/binutils/../include
> -DLOCALEDIR="\"/usr/local/share/locale\""
> -Dbin_dummy_emulation=bin_vanilla_emulation -W -Wall
> -Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2 -c
> ../../src/binutils/readelf.c
> In file included from ../../src/binutils/readelf.c:146:
> ../../src/binutils/../include/libiberty.h:316: error: conflicting
> types for 'crc32'
> /usr/include/zlib.h:1305: error: previous declaration of 'crc32' was here
> make[4]: *** [readelf.o] Error 1
> make[4]: Leaving directory `/home/teawater/gdb/orig/bgdb/binutils'
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory `/home/teawater/gdb/orig/bgdb/binutils'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory `/home/teawater/gdb/orig/bgdb/binutils'
> make[1]: *** [all-binutils] Error 2
> make[1]: Leaving directory `/home/teawater/gdb/orig/bgdb'
> make: *** [all] Error 2
>
>
> On Sat, Jul 25, 2009 at 16:56, Hui Zhu<teawater@gmail.com> wrote:
>> gcc -g -I. -I../../src/gdb -I../../src/gdb/common
>> -I../../src/gdb/config -DLOCALEDIR="\"/usr/local/share/locale\""
>> -DHAVE_CONFIG_H -I../../src/gdb/../include/opcode
>> -I../../src/gdb/../readline/.. -I../bfd -I../../src/gdb/../bfd
>> -I../../src/gdb/../include -I../libdecnumber
>> -I../../src/gdb/../libdecnumber -I../../src/gdb/gnulib -Ignulib
>> -DMI_OUT=1 -DTUI=1 -Wall -Wdeclaration-after-statement
>> -Wpointer-arith -Wformat-nonliteral -Wno-pointer-sign -Wno-unused
>> -Wno-switch -Wno-char-subscripts -Werror -c -o remote.o -MT remote.o
>> -MMD -MP -MF .deps/remote.Tpo ../../src/gdb/remote.c
>> ../../src/gdb/remote.c:164: error: conflicting types for 'crc32'
>> ../../src/gdb/../include/libiberty.h:316: error: previous declaration
>> of 'crc32' was here
>> make: *** [remote.o] Error 1
>>
>> Looks like new crc32 make something wrong.
>>
>> Thanks,
>> Hui
>>
>> On Sat, Jul 25, 2009 at 08:01, <dj@sourceware.org> wrote:
>>> CVSROOT: /cvs/src
>>> Module name: src
>>> Changes by: dj@sourceware.org 2009-07-25 00:01:58
>>>
>>> Modified files:
>>> libiberty : ChangeLog Makefile.in functions.texi
>>> Added files:
>>> libiberty : crc32.c
>>>
>>> Log message:
>>> merge from gcc
>>>
>>> Patches:
>>> http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/libiberty/crc32.c.diff?cvsroot=src&r1=NONE&r2=1.1
>>> http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/libiberty/ChangeLog.diff?cvsroot=src&r1=1.497&r2=1.498
>>> http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/libiberty/Makefile.in.diff?cvsroot=src&r1=1.96&r2=1.97
>>> http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/libiberty/functions.texi.diff?cvsroot=src&r1=1.34&r2=1.35
>>>
>>>
>>
>
prev parent reply other threads:[~2009-07-25 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-25 8:57 Hui Zhu
2009-07-25 9:02 ` Hui Zhu
2009-07-25 14:18 ` Hui Zhu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=daef60380907250717w4401c8a2ve7f55d34d970ed5@mail.gmail.com \
--to=teawater@gmail.com \
--cc=dj@sourceware.org \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox