From: "Bobo" <spiridenok@tut.by>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>,Mark Kettenis
<mark.kettenis@xs4all.nl>
Cc: drow@false.org, gdb@sourceware.org
Subject: Re: Breakpoint in C++ class constructor is never reached
Date: Tue, 30 Oct 2007 09:53:00 -0000 [thread overview]
Message-ID: <web-421282098@speedy.tutby.com> (raw)
In-Reply-To: <1193495532.5787.187.camel@localhost.localdomain>
Sorry i don't really know what "off-list a regenerated configure script"
means and what i need to do with it to verify if the build problem is
gone...
Is there maybe a snapshot available with the latest changes of Thiago?
(the latest snapshot version i can find on pub/gdb/snapshots/ is from 26 Oct
2007)
Anyway, i would like to check if the build problem is solved. please let me
know how i can do that.
Sat, 27 Oct 2007 12:32:12 -0200, Thiago Jung Bauermann <bauerman@br.ibm.com>
> On Fri, 2007-10-26 at 13:02 -0200, Thiago Jung Bauermann wrote:
>> On Fri, 2007-10-26 at 16:50 +0200, Mark Kettenis wrote:
>> > > Date: Fri, 26 Oct 2007 10:31:28 -0400
>> > > From: Daniel Jacobowitz <drow@false.org>
>> > > Oh dear. GCC requires GNU make, but GDB is not supposed to, I don't
>> > > think. This is a new problem.
>> >
>> > I regularly build GDB with OpenBSD make, so yes this is new (and I'd
>> > very much appreciate it if it got fixed).
>>
>> I will work on this ASAP.
>
> I just posted a patch to fix this. Sorry for the delay, it took me some
> time to determine if I had copyright assignment to contribute to GCC.
>
> I tested the change with NetBSD's make, so I think the GNUisms are gone.
> If this is not enough to fix your build problems, please let me know.
>
> I can send you off-list a regenerated configure script if you want to
> test the patch and don't have autoconf 2.59 handy.
> --
> []'s
> Thiago Jung Bauermann
> Software Engineer
> IBM Linux Technology Center
---------
Âñå áëîãè - òóò: http://blogs.tut.by/
next prev parent reply other threads:[~2007-10-30 9:53 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 11:45 Bobo
2007-10-26 11:54 ` Daniel Jacobowitz
2007-10-26 12:18 ` Bobo
2007-10-26 12:21 ` Daniel Jacobowitz
2007-10-26 14:26 ` Bobo
[not found] ` <web-419222549@speedy.tutby.com>
2007-10-26 14:31 ` Daniel Jacobowitz
2007-10-26 14:51 ` Mark Kettenis
2007-10-26 14:59 ` Daniel Jacobowitz
2007-10-26 15:02 ` Thiago Jung Bauermann
2007-10-27 14:32 ` Thiago Jung Bauermann
2007-10-27 15:57 ` Mark Kettenis
2007-10-30 9:53 ` Bobo [this message]
2007-10-30 11:19 ` Daniel Jacobowitz
2007-10-30 13:50 ` Thiago Jung Bauermann
2007-10-30 14:13 ` Thiago Jung Bauermann
2007-10-31 8:10 ` Bobo
2007-10-31 19:06 ` Thiago Jung Bauermann
2007-11-05 9:01 ` Bobo
2007-11-06 20:12 ` Thiago Jung Bauermann
2007-11-07 8:31 ` Bobo
2007-11-07 20:34 ` Thiago Jung Bauermann
2007-11-08 8:27 ` Bobo
2007-11-08 14:58 ` Thiago Jung Bauermann
2007-11-08 15:05 ` Daniel Jacobowitz
2007-11-08 16:29 ` Bobo
2007-11-08 16:33 ` Daniel Jacobowitz
2007-11-09 7:38 ` Bobo
2007-11-09 14:02 ` Daniel Jacobowitz
2007-11-16 15:26 ` Bobo
2007-11-26 19:11 ` Thiago Jung Bauermann
2007-11-06 15:58 ` Gordon Prieur
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=web-421282098@speedy.tutby.com \
--to=spiridenok@tut.by \
--cc=bauerman@br.ibm.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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).