Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Dave Korn" <dave.korn@artimi.com>
To: "'Daniel Jacobowitz'" <drow@false.org>
Cc: "'Bruce Dubbs'" <bdubbs@linuxfromscratch.org>, 	<gdb@sourceware.org>
Subject: RE: Building gdb from source
Date: Fri, 07 Apr 2006 16:27:00 -0000	[thread overview]
Message-ID: <000201c65a5c$09fdd900$a501a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <20060407154915.GA24300@nevyn.them.org>

On 07 April 2006 16:49, 'Daniel Jacobowitz' wrote:

> On Fri, Apr 07, 2006 at 04:39:42PM +0100, Dave Korn wrote:
>> On 07 April 2006 16:33, 'Daniel Jacobowitz' wrote:
>> 
>>> On Fri, Apr 07, 2006 at 04:25:55PM +0100, Dave Korn wrote:
>>>>   ?  Is this because releases could be coming from branches that were
>>>> branched at very different times?  Would it have been more reasonable if
>>>> I had said "releases that are based on roughly-contemporary branches"?
>>> 
>>> But there are no such releases.
>> 
>> 
>>   Ok, I give up, I haven't got the faintest idea what you're talking
>> about.  I can't even parse that.
> 
> Binutils and GDB releases are branched at unpredictably different
> times.  How close in time they are doesn't matter if there's been an
> interface change in between.

  Ah, ok, we're basically in agreement.  I understand that interface changes
are the one thing that can break compatibility.  I was simply inferring that
if the interval between a binutils branch and a gdb branch is smaller rather
than larger, the odds of someone having made such a change are smaller rather
than greater, even though that change is technically a delta that could take
place in an instant.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


  reply	other threads:[~2006-04-07 15:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-07  1:16 Bruce Dubbs
2006-04-07  6:39 ` Daniel Jacobowitz
2006-04-07 15:02 ` Dave Korn
2006-04-07 15:19   ` Bruce Dubbs
2006-04-07 15:26     ` Dave Korn
2006-04-07 15:32       ` Daniel Jacobowitz
2006-04-07 15:39         ` Dave Korn
2006-04-07 15:40           ` 'Daniel Jacobowitz'
2006-04-07 15:49             ` Dave Korn
2006-04-07 15:58               ` 'Daniel Jacobowitz'
2006-04-07 16:27                 ` Dave Korn [this message]
2006-04-07 15:54       ` Bruce Dubbs
2006-04-07 20:01       ` DJ Delorie
2006-04-14  6:10     ` "Program received signal SIG33" error yinglcs2

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='000201c65a5c$09fdd900$a501a8c0@CAM.ARTIMI.COM' \
    --to=dave.korn@artimi.com \
    --cc=bdubbs@linuxfromscratch.org \
    --cc=drow@false.org \
    --cc=gdb@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