This is the mail archive of the gcc-bugs@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]
Other format: [Raw text]

[Bug bootstrap/11668] Make error on HPUX with gcc3.3


PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11668


danglin at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|                            |FIXED


------- Additional Comments From danglin at gcc dot gnu dot org  2003-08-10 02:26 -------
1) Regarding the initial report, it should have been possible to continue the
   build after the comparison failure with a simple `make'.  This is documented
   in the installation notes.  I would recommend that you start exactly
   as you did except add `--enable-languages=c' to your initial
   configure command.  When you get the comparison failure, just continue
   with `make'.  If that completes successfully, install the C compiler.
   Use this compiler to build and install binutils.  Then, rebuild GCC with
   all the languages that you want.  For this, specify `--with-gnu-as' and
   `--with-as=/path-to-gas/as'.  Another route is to build binutils with the
   HP compiler.  After binutils is installed, there are numerous reports
   in the gcc-testresults list that show how to configure for a successful
   build.  If you already have GCC and binutils installed, look at one of
   these reports to see how to build 3.3 or 3.3.1.  There were a couple
   posted yesterday.

2) As noted in comment #6, there is an unresolved problem using the HP
   assembler with C++.  It should work with C, Fortran and Objective C.  Java
   is NOT currently supported on the PA although the compiler builds.  A port
   for libffi is missing and as a result the java library can't be built.

3) It is HIGHLY recommended that the GNU assembler be used.  Read the
   installation notes.  The HP assembler doesn't provide weak symbol support,
   etc., etc.  This is very important when using C++.

4) Dara's comment in #6 misled you.  --with-as and --with-ld must specify
   the complete path to the executable (e.g., --with-ld=/usr/ccs/bin/ld).
   There also isn't a GNU ld port for the HP SOM port.  This is because of
   the unique nature of the SOM object format.  Thus, don't specify
   `-with-gnu-ld' on the 32-bit HP-UX port unless you have somehow managed
   to port GNU ld to it.

5) I don't recommend just using `make' to build GCC unless you are building
   a cross compiler.  Use `make bootstrap'.

6) There is more info in the installation documentation about required HP
   patches, make, sed, etc.

I am closing this PR because there isn't anything new in this report.


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