From: asmwarrior <asmwarrior@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Tromey <tromey@redhat.com>, gdb@sourceware.org
Subject: Re: gdb with python support still get crash on showing uninitialized local variables
Date: Tue, 09 Nov 2010 02:06:00 -0000 [thread overview]
Message-ID: <4CD8ABA4.2090304@gmail.com> (raw)
In-Reply-To: <83bp6l9b4l.fsf@gnu.org>
On 2010-10-23 5:21, Eli Zaretskii wrote:
>> From: Tom Tromey<tromey@redhat.com>
>> Cc: "gdb\@sourceware.org"<gdb@sourceware.org>, gdb-patches@sourceware.org
>> Date: Fri, 22 Oct 2010 13:17:04 -0600
>>
>> asmwarrior> /bin/sh: line 1: ../../../../src/gdb/bfd/../mkinstalldirs: Permission denied
>>
>> This file should be +x.
> There's no such thing on Windows.
Dear GDB gurus, Today, I just do a git pull, then try to build the gdb
again. but I still failed under building gdb under windows/msys.
Here is the configure:
cd build
../gdb/configure --host=mingw32 --target=mingw32 \
--prefix=/E/test/install \
--build=mingw32 CFLAGS="-s -L/python/libs -I/python/include
-I/E/test/expat/install/include -static -L/E/test/expat/install/lib" \
--with-python \
--with-expat
and here is the build error when running the make command.
mingw32-gcc -c -DHAVE_CONFIG_H -s -L/python/libs -I/python/include
-I/E/test/exp
at/install/include -static -L/E/test/expat/install/lib
-D__USE_MINGW_ACCESS -I.
-I../../gdb/libiberty/../include -W -Wall -Wwrite-strings
-Wc++-compat -Wstric
t-prototypes -pedantic ../../gdb/libiberty/fibheap.c -o fibheap.o
../../gdb/libiberty/fibheap.c: In function 'fibheap_union':
../../gdb/libiberty/fibheap.c:151: warning: implicit declaration of
function 'fr
ee'
../../gdb/libiberty/fibheap.c:151: warning: incompatible implicit
declaration of
built-in function 'free'
../../gdb/libiberty/fibheap.c:156: warning: incompatible implicit
declaration of
built-in function 'free'
../../gdb/libiberty/fibheap.c:172: warning: incompatible implicit
declaration of
built-in function 'free'
../../gdb/libiberty/fibheap.c: In function 'fibheap_extract_min':
../../gdb/libiberty/fibheap.c:190: warning: incompatible implicit
declaration of
built-in function 'free'
../../gdb/libiberty/fibheap.c: In function 'fibheap_replace_key_data':
../../gdb/libiberty/fibheap.c:220: error: 'LONG_MIN' undeclared (first
use in th
is function)
../../gdb/libiberty/fibheap.c:220: error: (Each undeclared identifier is
reporte
d only once
../../gdb/libiberty/fibheap.c:220: error: for each function it appears in.)
../../gdb/libiberty/fibheap.c: In function 'fibheap_delete_node':
../../gdb/libiberty/fibheap.c:261: error: 'LONG_MIN' undeclared (first
use in th
is function)
../../gdb/libiberty/fibheap.c:265: warning: implicit declaration of
function 'ab
ort'
../../gdb/libiberty/fibheap.c:265: warning: incompatible implicit
declaration of
built-in function 'abort'
../../gdb/libiberty/fibheap.c: In function 'fibheap_delete':
../../gdb/libiberty/fibheap.c:277: warning: incompatible implicit
declaration of
built-in function 'free'
../../gdb/libiberty/fibheap.c: In function 'fibheap_consolidate':
../../gdb/libiberty/fibheap.c:368: warning: implicit declaration of
function 'me
mset'
../../gdb/libiberty/fibheap.c:368: warning: incompatible implicit
declaration of
built-in function 'memset'
make[2]: *** [fibheap.o] Error 1
make[2]: Leaving directory `/e/test/build/libiberty'
make[1]: *** [all-libiberty] Error 2
make[1]: Leaving directory `/e/test/build'
make: *** [all] Error 2
thank you very much.
asmwarrior
next prev parent reply other threads:[~2010-11-09 2:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 2:16 asmwarrior
2010-10-14 18:30 ` André Pönitz
2010-10-15 3:55 ` asmwarrior
2010-10-15 22:38 ` Tom Tromey
2010-11-05 17:14 ` André Pönitz
2010-10-15 22:37 ` Tom Tromey
2010-10-16 1:14 ` asmwarrior
[not found] ` <m3fww2ued0.fsf_-_@fleche.redhat.com>
2010-10-20 5:19 ` asmwarrior
2010-10-20 5:33 ` asmwarrior
2010-10-22 19:13 ` Tom Tromey
2010-10-22 21:22 ` Eli Zaretskii
2010-10-29 19:18 ` Joel Brobecker
2010-10-29 22:01 ` Eli Zaretskii
2010-10-31 2:24 ` asmwarrior
2010-11-09 2:06 ` asmwarrior [this message]
2010-11-12 18:07 ` Tom Tromey
[not found] ` <4CE0C149.6090609@gmail.com>
2010-11-15 18:10 ` Tom Tromey
2010-12-14 2:13 ` asmwarrior
[not found] ` <4D06D1DB.1070501@gmail.com>
2010-12-14 15:00 ` Tom Tromey
2010-12-16 8:48 ` asmwarrior
[not found] ` <AANLkTinsJLTZT0ws=LbpYcq85_Z9_R=fcXz+J+kqScJU@mail.gmail.com>
2010-12-17 19:04 ` RFA: add python exception subclasses Tom Tromey
2010-12-18 2:26 ` asmwarrior
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=4CD8ABA4.2090304@gmail.com \
--to=asmwarrior@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=tromey@redhat.com \
/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