From: Arnaud Charlet <charlet@ACT-Europe.FR>
To: Trevor Ellermann <trevore@engr.arizona.edu>
Cc: gdb@sourceware.cygnus.com
Subject: Re: Problems with gdb after 5.1 upgrade (Tru64)
Date: Fri, 16 Feb 2001 00:47:00 -0000 [thread overview]
Message-ID: <20010216094746.D17175@dublin.int.act-europe.fr> (raw)
In-Reply-To: <Pine.OSF.4.31.0102151503250.388670-100000@intermix.engr.arizona.edu>
There has been major changes in Tru64 5.1, in particular wrt internal
structures that gdb relies upon.
Also, there are problems in GCC itself that prevents it from compiling
gdb properly on Tru64 5.1.
Arno
prev parent reply other threads:[~2001-02-16 0:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 14:04 Trevor Ellermann
2001-02-16 0:47 ` Arnaud Charlet [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=20010216094746.D17175@dublin.int.act-europe.fr \
--to=charlet@act-europe.fr \
--cc=gdb@sourceware.cygnus.com \
--cc=trevore@engr.arizona.edu \
/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