public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/8516] Build of gdb-6.0 on hppa1.1-hp-hpux10.20 fails
Date: Wed, 24 Oct 2012 16:55:00 -0000 [thread overview]
Message-ID: <bug-8516-4717-6P7YbWJFnf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-8516-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=8516
Pedro Alves <palves at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
CC| |palves at redhat dot com
Resolution| |FIXED
--- Comment #19 from dave at hiauly1 dot hia.nrc.ca <dave at hiauly1 dot hia.nrc.ca> 2010-07-30 12:42:53 UTC ---
Subject: Re: Build of gdb-6.0 on hppa1.1-hp-hpux10.20 fails
> So, although the build breakage this time is probably easy to fix, IMO,
> we should just move the file into the attic. It may
> be even less work to start from scratch than to resurrect it into functional
> state. The file will always be in the attic for anyone wanting to salvage
> this. (I didn't go look for the current debian patch to see what they did to
> this file.)
Probably, nothing as I don't think it is used.
If you have a template, possibly I could try fill in the blanks later
next week.
Dave
--- Comment #20 from Pedro Alves <palves at redhat dot com> 2012-10-24 16:55:43 UTC ---
hpux-thread.c was finally deleted in Jan 2011.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next parent reply other threads:[~2012-10-24 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-8516-4717@http.sourceware.org/bugzilla/>
2012-10-24 16:55 ` palves at redhat dot com [this message]
2012-10-27 14:08 ` danglin at gcc dot gnu.org
[not found] <20031007181800.8516.dave.anglin@nrc-cnrc.gc.ca>
2010-07-29 19:40 ` danglin at gcc dot gnu dot org
2010-07-30 10:19 ` pedro at codesourcery dot com
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=bug-8516-4717-6P7YbWJFnf@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).