Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@equator.com>
To: gdb@sourceware.cygnus.com
Subject: building gdb-5.0 under cygwin b20.1
Date: Tue, 06 Jun 2000 08:03:00 -0000	[thread overview]
Message-ID: <r21z2ayhqx.fsf@bobdog.equator.com> (raw)

Is it possible? or do I need the latest 'net' release of the cygwin
tools.

Specifically, the build is failing at:

gcc -c -g -O2    -I. -I. -I./config -DHAVE_CONFIG_H -I./../include/opcode -I./../readline/.. -I../bfd -I./../bfd  -I./../include -I../intl -I./../intl -I./tui-DUSE_INCLUDED_REGEX   win32-nat.c
win32-nat.c:42: imagehlp.h: No such file or directory
win32-nat.c:339: psapi.h: No such file or directory
make: *** [win32-nat.o] Error 1

Are these missing headers part of some win32 tools I need to install,
or are they part of cygwin?

BTW, I'm building the gdb from the b20.1 'full' release without any
problems.

Thanks.

-- 
Kevin Hilman               ---  Equator Technologies Inc.
khilman@equator.com        ---  Seattle, WA USA
From cgf@cygnus.com Tue Jun 06 09:42:00 2000
From: Chris Faylor <cgf@cygnus.com>
To: Kevin Hilman <khilman@equator.com>
Cc: gdb@sourceware.cygnus.com
Subject: Re: building gdb-5.0 under cygwin b20.1
Date: Tue, 06 Jun 2000 09:42:00 -0000
Message-id: <20000606124253.A2714@cygnus.com>
References: <r21z2ayhqx.fsf@bobdog.equator.com>
X-SW-Source: 2000-06/msg00048.html
Content-length: 982

On Tue, Jun 06, 2000 at 08:03:02AM -0700, Kevin Hilman wrote:
>Is it possible?  or do I need the latest 'net' release of the cygwin
>tools.
>
>Specifically, the build is failing at:
>
>gcc -c -g -O2    -I. -I. -I./config -DHAVE_CONFIG_H -I./../include/opcode -I./../readline/.. -I../bfd -I./../bfd  -I./../include -I../intl -I./../intl -I./tui-DUSE_INCLUDED_REGEX   win32-nat.c
>win32-nat.c:42: imagehlp.h: No such file or directory
>win32-nat.c:339: psapi.h: No such file or directory
>make: *** [win32-nat.o] Error 1
>
>Are these missing headers part of some win32 tools I need to install,
>or are they part of cygwin?
>
>BTW, I'm building the gdb from the b20.1 'full' release without any
>problems.

Yes.  The headers are part of the latest cygwin release.  You will need
to install that to build gdb.

You might be able to get away with just grabbing the headers from

ftp://sourceware.cygnus.com/pub/cygwin/latest/cygwin/cygwin-1.1.1.tar.gz

but there are no guarantees.

cgf
From Sudhanshu_Tewari@3com.com Tue Jun 06 10:54:00 2000
From: Sudhanshu_Tewari@3com.com
To: gdb@sourceware.cygnus.com
Subject: Stub file for powerpc architecture !!
Date: Tue, 06 Jun 2000 10:54:00 -0000
Message-id: <882568F6.00614765.00@hqoutbound.ops.3com.com>
X-SW-Source: 2000-06/msg00049.html
Content-length: 208

Hi,

I am intrested to use GDB for the remote debugging of IBM-Powerpc based target
board.
Is there "powerpc-stub.c"  file is available any where ?
If yes pl forward me the location or file.

TIA
Sudhanshu



             reply	other threads:[~2000-06-06  8:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-06  8:03 Kevin Hilman [this message]
2000-06-06 14:08 ` Jim Ingham

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=r21z2ayhqx.fsf@bobdog.equator.com \
    --to=khilman@equator.com \
    --cc=gdb@sourceware.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