This is the mail archive of the gdb@sourceware.cygnus.com mailing list for the GDB project. See the GDB home page for more information.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
For people on HP-UX 10.20 and up the HP extension 'Wildebeest' port is available
for 10.20 and shipped with 11 (apparently). I've bootstrapped egcs-1.1b with
the bundled K&R compiler successfully too (I think).
If HP resync Wildebeest (currently based on gdb-4.16) regularly with gdb, people
will have a useable gdb version available.
The "Software Porting And Archive Centre For HP-UX" <http://salam.cae.wisc.edu/>
has a gcc-2.8.1 (binary) package available - perhaps you could give the
references to archive sites with SunOs and HP-UX gcc binaries.
----
Switch to pure ANSI?
Stan Shebs (shebs@cygnus.com)
Mon, 7 Dec 1998 17:01:38 -0800
A number of people have pointed out that GDB's requirement to support
K&R C compilers by using PARAMS etc is somewhat archaic; at this point
only SunOS and some HP/UX systems even *have* pre-ANSI compilers, and
they have GCC ports already. So I'm contemplating changing the GDB
coding standard to specify ANSI-only code. (Note that this doesn't
require changing all the code, but it does allow files to be converted
as convenient.)
However, before taking this step, I'd like to be sure that everyone is
comfortable with the change. A few files are already like this; for
instance, Mac and Windows native support, and some of the simulators.
However, once common files start changing, then people trying to use
cc on SunOS 4.1 and HP/UX will be unable to build GDB. To those folks
I believe we can say "use GCC". Are there any other platforms that
would be adversely affected? Are there any other bad consequences to
changing the standard?
Stan