From mboxrd@z Thu Jan 1 00:00:00 1970 From: tprinceusa@mindspring.com To: cgrab@minstrel.com Cc: gcc-help@gcc.gnu.org Subject: Re: Problems installing gcc Date: Fri, 09 Mar 2001 12:40:00 -0000 Message-id: X-SW-Source: 2001-03/msg00066.html cgrab@minstrel.com wrote: > Hi, I'm not certain if this is the appropriate place to ask for help installing gcc. If not, can you direct me to the appropriate folks. Close; gcc-help is better. I'm attempting to install gcc 2.95.2 (downloaded from ftp.gnu.org, build date 10/25/99) onto an HP box running HP-UX 10.2. The configure process runs successfully (as far as I can tell), but the install dies after about an hour or so when it attempts to do something with bison. Below are the last 40 or so lines of output from the make process. I also attempted to download and install bison separately. No luck there either. Again, configure went fine and make died part way through. The HPUX build process is pretty complex, and there are several ways to go about it. 1. The official page on installing HPUX assumes you have the HPUX C development system installed. 2. gcc does what it can to enable you to bootstrap from just the default tools included with HPUX, but doesn't document the process fully. 3. there are pre-built binary versions, which probably require super-user to install, which you could use to bootstrap the source version of your choice. It's been a long time since I had such a box, but the #2 drill as I remember it: build gnu make from source, using the HPUX tools. Install it separately from HPUX make, possibly renaming it gmake, for example. Use gmake from now on. build a temporary version of gcc, without bootstrapping. Use it to build bison, flex, and binutils. Figure out the scheme for installing binutils. Basically, build and install it in the same installation tree you will be using for gcc. One reason you need flex and bison is that gcc configure thinks that the presence of libl means that lex is present; you might get by without them at this stage if you removed libl from view. Another reason has to do with date stamps on files which may not really need to be rebuilt. configure prefers flex if it is available, so installing bison and flex avoids trouble with the partial installation of lex in HPUX. with gmake, binutils, bison, and flex available, you should be able to bootstrap and install gcc-2.95.2 with all the languages you desire. In theory, you can put all these into one build tree and have them build automatically in the proper sequence. That's the reason for not having more detailed instructions. If you run into builds which require the gnu macro processor, as you will, you must install that and set environment variables peculiar to each package which point to your new installation, as the HPUX version is broken from the gnu point of view. In order to test your gcc build, you will need to get one of the dejagnu sources intended specifically for this purpose. If you include it in your gcc build tree, it will build automatically, but I doubt you will want to rebuild it once it's working. You will need the gnu versions of patch, autoconf, maybe automake and perl in the long run; where there are HPUX versions, they won't work for gnu builds, even where they are derived from long ago gnu versions (which seemingly invokes GPL requirements which HP seems to ignore). I wonder whether it's worth keeping these oldsters functional when they require so much more effort than a basic linux box which can out-perform them.