Re: [5.3] What's the hold up?

Andrew Cagney
2002-11-21T05:09:46Z

> On Wed, Nov 20, 2002 at 02:07:05PM -0500, Daniel Jacobowitz wrote:
>
>> On Wed, Nov 20, 2002 at 01:52:27PM -0500, Daniel Jacobowitz wrote:
>
>> > On Wed, Nov 20, 2002 at 12:50:46PM -0500, Andrew Cagney wrote:
>
>> > > If you search the bug data base for high GDB PR's you'll see:
>> > >
>> > > PR Category State Priority Responsible Synopsis
>> > > 378 gdb suspended high unassigned ``GNU/Linux'' ``Linux kernel''
>> > > 394 gdb suspended high unassigned GDB 5.1.1 contains intl/ droppings
>> > > 527 gdb suspended high unassigned GDB 5.2 incompatibilities with GNU
>> > > textutils 2.0.21 in POSIX mode
>> > > 676 gdb analyzed high unassigned Alpha OSF1, gcc, internal GDB error in
>> > > mdebugread
>> > > 708 gdb open high unassigned Can't build 5.3 branch (and probably trunk).
>> > > 725 gdb open high unassigned Crash using debug target and regcaches (in
>> > > 5.3 branch?)
>> > > 763 gdb open high unassigned gdb 5.2 removes the conditional breakpoints
>> > > 840 gdb suspended high unassigned Expect on GDB 5.3 branch doesn't build
>> > > on IRIX 6.5
>> > >
>> > > It is these (actually the non-suspended ones) that I'm trying to get
>> > > flushed.
>> > >
>> > > Of most concern are 708 and 676. They both indicate something failing the:
>> > >
>> > > ./configure
>> > > make
>> > > ./gdb/gdb ./gdb/gdb
>> > > (gdb) b main
>> > > (gdb) run
>> > >
>> > > release criteria :-(
>
>> >
>> > I hit gdb/708 on HP/UX... it's really not that complicated to fix, I
>> > don't think...
>> >
>> > Of course trying to reproduce it I can't even build the snapshot; it
>> > tries to make distclean in itcl.
>
>>
>> However, my guess at a fix for gdb/708 is that dejagnu/Makefile.am
>> needs a distclean-local to parallel clean-local, which distcleans in
>> example/.
>>
>> The failure in itcl/ appears to be a configure script bug with autoconf
>> 2.5. Keith fixed this on mainline on Sep. 5th:
>>
>> * configure.in (subdirs): New variable. Don't put AC_CONFIG_SUBDIRS
>> macro into configure.in twice: it confuses autoconf. Instead use
>> the variable to hold the subdirs to be configured.
>> * configure: Regenerated.
>>
>> This should probably go to the branch.
>
>
> It did, two months ago. I haven't cvs up'd that tree in longer than I
> had thought :)
>
> Try this patch for the DejaGNU droppings. And one in gdb/doc/. That
> wasn't so hard, was it?

I think these can go in.

Andrew