🚀 go-pugleaf

The following answers are my opinion only.  (The person asking for
help wants to install the Gnu tools on the Sun-4).

In article <10210@bgsuvax.bgsu.edu> denbeste@enigma.bgsu.edu writes:
>+ What is the best order to install the various tools?

I would recommend installing gcc first, and using gcc to build other
things.  This is more important on some platforms than it is on the
Sun-4.

On platforms other than Sun-4, install gcc and Gnu make very early.

>+ How do I convince gcc to use gas instead of sun's asm?

Install gas as $(libsubdir)/as where $(libsubdir) is the place where
the compiler passes live.  You can determine the value for your system
by looking at the makefile for gcc-2.1.

If you want to create shared libraries on the Sun-4, do not install gas.
It doesn't handle PIC correctly yet.  The native assembler works fine with
both the Gnu linker and with collect.  On Sun-3's, on the other hand,
you'll need gas to make gcc work.

>+ Where can I find the gnu loader?  Should I be using it?

If you want to use shared libraries on the Sun-4, do not install the
Gnu linker, but make sure to install collect so that g++ will work
(see the directions in the gcc INSTALL file).

Advantages of the Gnu linker: linking C++ programs is faster than with
collect, and undefined symbol errors are printed out using the original
names, instead of the ugly mangled names.  If you're using only C, I
see no advantage to the Gnu linker at all.

>+ Does the g++ created by gcc-2.1 superceed g++1.39, or are they two
>  different creatures.

Both; the g++ in gcc-2.1 supersedes g++1.39, and it is a different
creature that is substantially closer to the ARM (Ellis and Stroustrup's
"The Annotated C++ Reference Manual").

>+ Should I insdtall glibc-1.03, or has it been incorporated into gcc-2.1

It hasn't been incorporated into gcc-2.1, and it is still experimental.
I'd advise against it, but you probably don't want to take my word for
it as I haven't played with it.

>+ How do I convert the documentation that is in texi format into something
>  that I can read/print?

Get the "texinfo" distribution from a Gnu archive site.  The file
texinfo.tex is a set of TeX macros that let you typeset the manual;
the program makeinfo produces a hypertext form that you can hop through
with Emacs or with the xinfo or info programs.

>+ Why does glib++/test-install/a.cc segmentation-fault when compiled and run?
>  (I am making a separate post with this question.)

Beats me.



--
Joe Buck	jbuck@ohm.berkeley.edu