From: STEPHANE.S.P.PERIO@tts.thomson.fr
To: gnu-win32@cygnus.com (Receipt Notification Requested)
Subject: Building GDB problem
Date: Wed, 06 Aug 1997 02:29:00 -0000 [thread overview]
Message-ID: <2200011106081997/A04771/INDRE/11B832C03900*> (raw) <@MHS> (raw)
Hi,
I apologize if this is an FAQ, but i see nothing about that in the mailing
lists.
I'm using gnu win32 b18 on NT 4.0 SP3 and i failed to build GDB.
Under bash, in the directory my-gdb, i run ../gdb/configure and it recognized
correctly the i386-pc-cygwin32 environment.
When i run make, the first problem i have is that the include files malloc.h
and bfd.h are missing but i found a copy of them in
/cdk/newlib/libc/stdlib/malloc.h and /gnuwin32/b18/include/bfd.h.
Are these two files the correct ones ?
If i use them, the make stops when compiling the i386-tdep.c file with the
error :
../gdb/i386-tdep.c: In function `get_longjmp_target':
../gdb/i386-tdep.c:592: `SP_ARG0' undeclared (first use this function)
../gdb/i386-tdep.c:592: (each undeclared identifier is reported only once
../gdb/i386-tdep.c:592: for each function it appears in.)
../gdb/i386-tdep.c: In function `set_assembly_language_command':
../gdb/i386-tdep.c:698: `bfd_mach_i386_i386' (first use this function)
../gdb/i386-tdep.c:698: `bfd_mach_i386_i8086' (first use this function)
../gdb/i386-tdep.c: In function _initialize_i386_tdep':
../gdb/i386-tdep.c:709: `bfd_mach_i386_i386' (first use this function)
Can someone help me ?
Thanks in advance.
S. PERIO
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next reply other threads:[~1997-08-06 2:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <@MHS>
1997-08-06 2:29 ` STEPHANE.S.P.PERIO [this message]
1997-08-06 10:37 ` Luke Diamand
1998-01-09 6:42 ` IOCTL NOT SUPPORTED ??? LAURENT.L.G.GEOFFROY
1998-01-09 18:22 ` Tim Newsham
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='2200011106081997/A04771/INDRE/11B832C03900*' \
--to=stephane.s.p.perio@tts.thomson.fr \
--cc=gnu-win32@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).