This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

3.0 PATCH: Update install.texi for alpha*-dec-osf*


The patch below updates the Tru64 UNIX (or whatever it's called today)
information in install.texi.

The old section on alpha*-dec-osf* is obsolete with the introduction of the
shared libgcc_s.  I've updated the section above (renamed from
alpha-*-osf1) to notice bootstrap caveats on Tru64 UNIX V5.1.

Tested with makeinfo and texi2dvi.

Ok for branch and mainline?

	Rainer

-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University

Email: ro@TechFak.Uni-Bielefeld.DE


Wed Jun 13 21:17:06 2001  Rainer Orth  <ro@TechFak.Uni-Bielefeld.DE>

	* doc/install.texi (Specific, alpha*-*-*): Fixed Tru64 UNIX
	etc. spelling.
	(Specific, alpha-*-osf1): Renamed to alpha*-*-osf*.
	Added Tru64 UNIX V5.1 bootstrap hints.
	(Specific, alpha*-*-osf*): Removed old section, obsolete.

Index: install.texi
===================================================================
RCS file: /cvs/gcc/egcs/gcc/doc/install.texi,v
retrieving revision 1.1.2.23
diff -u -p -r1.1.2.23 install.texi
--- install.texi	2001/06/13 13:08:32	1.1.2.23
+++ install.texi	2001/06/13 19:11:48
@@ -1165,8 +1169,6 @@ GNU Compiler Collection on your machine.
 @item
 @uref{#alpha*-*-*,,alpha*-*-*}
 @item
-@uref{#alpha-*-osf1,,alpha-*-osf1}
-@item
 @uref{#alpha*-dec-osf*,,alpha*-dec-osf*}
 @item
 @uref{#arc-*-elf,,arc-*-elf}
@@ -1420,8 +1422,8 @@ AMD Am29050 used in a system running a v
 
 This section contains general configuration information for all
 alpha-based platforms using ELF (in particular, ignore this section for
-OSF and tru64).  In addition to reading this section, please read all
-other sections that match your target.
+DEC OSF/1, Digital UNIX and Tru64 UNIX).  In addition to reading this
+section, please read all other sections that match your target.
 
 We require binutils 2.11.1 (as of yet unreleased), binutils with
 @samp{binutils-2_11-branch} tag after May 31, 2001 (as taken below), or newer.
@@ -1449,10 +1451,26 @@ options to point into the prefix used ab
 </p>
 <hr>
 @end html
-@heading @anchor{alpha-*-osf1}alpha-*-osf1
+@heading @anchor{alpha*-dec-osf*}alpha*-dec-osf*
 Systems using processors that implement the DEC Alpha architecture and
-are running the DEC Unix (OSF/1) operating system, for example the DEC
-Alpha AXP systems.CC.)
+are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
+Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.)
+
+In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
+currently (2001-06-13) work with @command{mips-tfile}.  As a workaround,
+we need to use the old assembler, invoked via the barely documented
+@option{-oldas} option.  To bootstrap GCC, you either need to use the
+Compaq C Compiler:
+
+@example
+   % CC=cc @var{srcdir}/configure [@var{target}] [@var{options}]
+@end example
+
+or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
+
+@example
+   % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{target}] [@var{options}]
+@end example
 
 GNU CC writes a @samp{.verstamp} directive to the assembler output file
 unless it is built as a cross-compiler.  It gets the version to use from
@@ -1495,52 +1513,6 @@ different depending on whether or not @o
 To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
 DBX.  DEC is now aware of this problem with the assembler and hopes to
 provide a fix shortly.
-
-@html
-</p>
-<hr>
-@end html
-@heading @anchor{alpha*-dec-osf*}alpha*-dec-osf*
-
-If you install a shared libstdc++ and, when you link a non-trivial C++
-program (for example, @file{gcc/testsuite/g++.other/delete3.C}),
-the linker reports a couple of errors about multiply-defined symbols
-(for example, @code{nothrow}, @code{__throw} and
-@code{terminate(void)}), you've probably got a linker bug, for
-which there's no known fix.  The officially recommended work-around is
-to remove the shared libstdc++.
-
-An alternative solution is to arrange that all symbols from
-@code{libgcc} get copied to the shared @code{libstdc++};
-see detailed solution below.  (Surprising as it may seem, this does
-indeed fix the problem!)  @emph{Beware} that this may bring you
-binary-compatibility problems in the future, if you don't use the same
-work-around next time you build @code{libstdc++}: if programs
-start to depend on @code{libstdc++} to provide symbols that used
-to be only in @code{libgcc}, you must arrange that
-@code{libstdc++} keeps providing them, otherwise the programs
-will have to be relinked.
-
-The magic spell is to add @option{-Wl,-all,-lgcc,-none} to the
-definition of macro @code{SHDEPS} in
-@file{libstdc++/config/dec-osf.ml} @emph{before}
-@file{alpha*-dec-osf*/libstdc++/Makefile} is created (a 
-@uref{dec-osf-shlibstdc++.patch,,patch} 
-that does just that is available).  If the Makefile already exists, run
-@file{./config.status} within directory
-@file{alpha*-dec-osf*/libstdc++} (and
-@file{alpha*-dec-osf*/ieee/libstdc++}, if it also exists).
-Remove any existing @file{libstdc++.so*} from such directories,
-and run @samp{make all-target-libstdc++} in the top-level
-directory, then @samp{make install-target-libstdc++}.
-
-If you have already removed the build tree, you may just remove
-@file{libstdc++.so.2.10.0} from the install tree and re-create
-it with the command 
-@samp{gcc -shared -o libstdc++.so.2.10.0 -Wl,-all,-lstdc++,-lgcc,-none -lm}.
-If the @file{ieee}
-sub-directory exists, repeat this command in it, with the additional
-flag @option{-mieee}.
 
 @html
 </p>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]