🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

2 total messages Started by Steve Chanin Sun, 03 Jan 1993 18:53
Building gcc/gdb on HP/UX with debugging
#550
Author: Steve Chanin
Date: Sun, 03 Jan 1993 18:53
29 lines
1624 bytes
I'm trying to help a friend build the most current gcc and gdb for an
HP-9000/827 (running HP/UX 8.02).  We would like the gcc to support
debugging.  I'm a little confused about how to do this build.

I have gcc-2.3.3 and gas-1.38 (from prep.ai.mit.edu).  I also have
pa-gas.u2.tar.Z, pa-gas.u3.tar.Z (a version of 1.36), and
pa-gdb-4.6.tar.Z from jaguar.cs.utah.edu.

1)Do I need to build gas before building gcc in order to get debugging
support?
2)Will I be ok if I build gas-1.36 (The HP FAQ says that 1.38.1
doesn't support HP/UX)

3)Will gcc-2.3.3 support HP PA with debugging or do I need the version
of 2.3.1 which is on jaguar (and has been specifically ported for HP
PA)?  I think building the 2.3.3 release would be better than using
the 2.1.1 because of bug fixes, etc.

3)Once I have gcc-2.x built, do I need to do anything special to build
pa-gdb-4.6?

4)Are there any plans to integrate the utah changes into the
gas/gcc/gdb standard distributions?

Thanks,
Steve
--
===============================================================================
DOMAIN: sbchanin@ai.mit.edu                                       Steven Chanin
Building gcc/gdb on HP/UX with debugging
#576
Author: Stu Grossman
Date: Mon, 04 Jan 1993 22:43
38 lines
2047 bytes
> 1)Do I need to build gas before building gcc in order to get debugging
> support?

There are really two issues here.  Are you talking about debugging the
compiler, or debugging your gcc compiled programs?  In the former case, you
will definately need to use Utah's pa-gas when building gcc after stage 1.

If you don't use Utah's pa-gas for building gcc, you will have to compile it
WITHOUT the -g option because the native HP assembler doesn't understand the
.stabxxx pseudo-ops.  You will still get a working gcc which is capable of
generating debug output, but you won't be able to debug gcc itself.

In either case, you will need to use Utah's pa-gas in order to use gcc's
debugging info.

> 3)Will gcc-2.3.3 support HP PA with debugging or do I need the version
> of 2.3.1 which is on jaguar (and has been specifically ported for HP
> PA)?  I think building the 2.3.3 release would be better than using
> the 2.1.1 because of bug fixes, etc.

I've been using 2.3.1 from Utah with very few problems.  I haven't tried
2.3.3 yet.

> 3)Once I have gcc-2.x built, do I need to do anything special to build
> pa-gdb-4.6?

Make sure that you install the appropriate patch file from Utah over the
standard GDB-4.6 distribution.  The name is pa-gdb-4.6.tar.Z.  It won't even
compile without that.

> 4)Are there any plans to integrate the utah changes into the
> gas/gcc/gdb standard distributions?

I have been doing a lot of work recently on the PA-GDB port.  It should come
out with release 4.8 of GDB.

			Stu Grossman
			Cygnus Support
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads