Re: [Bashdb-devel] Releases to bash 3.1 and 3.0 debuggers around Dec 10, 2006

[Rocky B. <roc...@gm...>]

One important thing I forgot to mention. There is a configure test for GNU
getopt that was failing on a  NetBSD box I tried. I guess it has a getopt
but it's different from from the GNU version. So I added option
--enable-getopt and the more relevant: twin --disable-getopt.

On cygwin I dont see GNU getopt installed at all and yet again the test was
failing. So one needs to manually add --disable-getopt on configure on
cygwin, assuming you don't have getopt (1) as well.

On 12/3/06, R. Bernstein <ro...@pa...> wrote:
>
> Eric Blake writes:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > According to R. Bernstein on 12/3/2006 9:51 AM:
> > > Recently I've needed to use the debugger on a computer that was
> > > running bash 3.0 and ran into a bug in the debugger. It is also
> > > present in the 3.1 debugger as well.
> >
> > Is the 3.1 release usable on bash 3.2, or do we need a 3.2 debugger
> > release as well?
>
> Hard as it is to believe, the bash API is upward compatible between
> versions 3.1 and 3.2 (I think this is the first time that's been the
> case in about 7 years.) So yes, this release will work on both.
>
> That said, it didn't necessarily mean it on either version of bash for
> *cygwin*. :-)
>
> I've just committed some changes to correct that.
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bashdb-devel mailing list
> Bas...@li...
> https://lists.sourceforge.net/lists/listinfo/bashdb-devel
>