From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24622 invoked by alias); 27 Nov 2001 07:01:27 -0000 Mailing-List: contact gdb-help@sourceware.cygnus.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 24586 invoked from network); 27 Nov 2001 07:01:13 -0000 Received: from unknown (HELO localhost.cygnus.com) (24.114.42.213) by hostedprojects.ges.redhat.com with SMTP; 27 Nov 2001 07:01:13 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.cygnus.com (Postfix) with ESMTP id F1DE53DBA for ; Tue, 27 Nov 2001 02:00:56 -0500 (EST) Message-ID: <3C033A28.50209@cygnus.com> Date: Fri, 16 Nov 2001 07:37:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.3) Gecko/20011020 X-Accept-Language: en-us MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: 5.1 ERRATA file? Content-Type: multipart/mixed; boundary="------------060904010807080702050207" X-SW-Source: 2001-11/txt/msg00169.txt.bz2 This is a multi-part message in MIME format. --------------060904010807080702050207 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-length: 393 Hello, Something I noticed from the feedback so far is that it is hard to know what problems a release will have - they are burried in the file gdb/README. What do people think of them being moved to the file gdb/ERRATA? Then again, the GNU coding standard might override such an idea :-/ (This is more of a policy decision so I've posted it to gdb@ rather than gdb-patches@) Andrew --------------060904010807080702050207 Content-Type: text/plain; name="diffs" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="diffs" Content-length: 3749 2001-11-27 Andrew Cagney * ERRATA: New file. Move build notes to here. * README: From here. Index: ERRATA =================================================================== RCS file: ERRATA diff -N ERRATA *** /dev/null Tue May 5 13:32:27 1998 --- ERRATA Mon Nov 26 22:51:37 2001 *************** *** 0 **** --- 1,45 ---- + hppa2.0-hp-hpux10.20 + + Due to a problem (conflicting types) with libiberty/regex.c, GDB 5.1 + does not build on HP/UX 10.20 when using the HP supplied compiler. + + Due to bit rot, GDB 5.1 does not work on HP/UX 10.20 when built with + GCC. + + + hppa2.0w-hp-hpux11.00 + + Due to a problem with ltconfig and long argument lines, GDB 5.1 does + not configure on HP/UX 11.00. + + + alpha-dec-osf5.1 + + GDB 5.1 has a number of problems on this platform (Ref PR gdb/237). A + GDB 5.1 built with ``CC="cc -DUSE_LDR_ROUTINES"'' is reported to work + much better. + + + alpha-dec-osf4.0e + + GDB 5.1 is known to have problems on this platform (encounters an + internal error in the symbol table reader). + + + sparcv9-sun-solaris2.8 + + There are known problems with building GDB 5.1 using GCC 3.0.x for the + 64 bit SPARC target (bad code gen). You could try a development + version of GCC. + + + i586-sco-sysv5uw7.1.1 + + There are known problems with GDB 5.1's thread support on this + platform. Non-threaded programs should work. + + + *-*-* + + GDB 5.1 assumes that the host C compiler implemends alloca(). GCC is + one such compiler. This problem should be fixed on the trunk. Index: README =================================================================== RCS file: /cvs/src/src/gdb/README,v retrieving revision 1.8.2.5 diff -p -r1.8.2.5 README *** README 2001/11/18 04:42:41 1.8.2.5 --- README 2001/11/27 06:52:02 *************** A summary of new features is in the file *** 7,13 **** --- 7,15 ---- See the GDB home page at http://www.gnu.org/software/gdb/ for up to date release information, mailing list links and archives, etc. + See the file ERRATA for late breaking news. + Unpacking and Installation -- quick overview ========================== *************** prefer; but you may abbreviate option na *** 425,480 **** `configure' accepts other options, for compatibility with configuring other GNU tools recursively; but these are the only options that affect GDB or its supporting libraries. - - - Host/target specific installation notes - ======================================= - - hppa2.0-hp-hpux10.20 - - Due to a problem (conflicting types) with libiberty/regex.c, GDB 5.1 - does not build on HP/UX 10.20 when using the HP supplied compiler. - - Due to bit rot, GDB 5.1 does not work on HP/UX 10.20 when built with - GCC. - - - hppa2.0w-hp-hpux11.00 - - Due to a problem with ltconfig and long argument lines, GDB 5.1 does - not configure on HP/UX 11.00. - - - alpha-dec-osf5.1 - - GDB 5.1 has a number of problems on this platform (Ref PR gdb/237). A - GDB 5.1 built with ``CC="cc -DUSE_LDR_ROUTINES"'' is reported to work - much better. - - - alpha-dec-osf4.0e - - GDB 5.1 is known to have problems on this platform (encounters an - internal error in the symbol table reader). - - - sparcv9-sun-solaris2.8 - - There are known problems with building GDB 5.1 using GCC 3.0.x for the - 64 bit SPARC target (bad code gen). You could try a development - version of GCC. - - - i586-sco-sysv5uw7.1.1 - - There are known problems with GDB 5.1's thread support on this - platform. Non-threaded programs should work. - - - *-*-* - - GDB 5.1 assumes that the host C compiler implemends alloca(). GCC is - one such compiler. This problem should be fixed on the trunk. Remote debugging --- 427,432 ---- --------------060904010807080702050207-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cagney To: gdb@sources.redhat.com Subject: 5.1 ERRATA file? Date: Mon, 26 Nov 2001 23:01:00 -0000 Message-ID: <3C033A28.50209@cygnus.com> X-SW-Source: 2001-11/msg00276.html Message-ID: <20011126230100.1QoxjQPiDGSAbLqCnG_C40f2qoz0s0aLY9oRq1IYbWg@z> Hello, Something I noticed from the feedback so far is that it is hard to know what problems a release will have - they are burried in the file gdb/README. What do people think of them being moved to the file gdb/ERRATA? Then again, the GNU coding standard might override such an idea :-/ (This is more of a policy decision so I've posted it to gdb@ rather than gdb-patches@) Andrew >From ac131313@cygnus.com Mon Nov 26 23:24:00 2001 From: Andrew Cagney To: gdb@sources.redhat.com Subject: 5.1.1 commit policy Date: Mon, 26 Nov 2001 23:24:00 -0000 Message-id: <3C033F9C.8070001@cygnus.com> X-SW-Source: 2001-11/msg00277.html Content-length: 1087 Same rules as for 5.1 apply :-) http://sources.redhat.com/ml/gdb/2001-07/msg00418.html > There, er, is no 5.1 branch commit policy. Instead the MAINTAINERS file > still holds. > > The only things I ask are: > > o > don't fix something on the branch > unless/until it is also fixed in > the trunk. If this isn't possible > then I think a mention in the > gdb/README file is better. > > o > try criteria like: > - does it fix a build build > - does does it fix break main, > run on a static binary > > o > only propose changes to core-gdb > after you've sent individual > bribes to all the people listed > in the MAINTAINERS file :-) > > o > the further you are away from > core-gdb then the less likely > that it will worry me (i.e. target > specific code). > > enjoy, > Andrew > > looks like some fixes for HP/UX at least will be available. That top level tweek, for instance, can probably be put onto the branch. Andrew PS: If you need to send a bribe, I've organied a credit card facility - dial +1 555 123 4567 and just follow the prompts ;-)