This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: HP/UX 10.20 vanilla <-> gcc-2.95.2
- To: martin at mira dot isdn dot cs dot tu-berlin dot de
- Subject: Re: HP/UX 10.20 vanilla <-> gcc-2.95.2
- From: N8TM at aol dot com
- Date: Sat, 30 Oct 1999 17:34:43 EDT
- CC: philipp at buehler dot de, gcc-bugs at gcc dot gnu dot org, hpux at connect dot org dot uk
In a message dated 10/30/99 3:51:21 PM EST, martin@mira.isdn.cs.tu-berlin.de
writes:
> I thought we were talking about building GCC; how is building binutils
> relevant, here? I still don't see why any trickery with lex (be it
> installing flex, or removing libl) is necessary to build gcc.
Unfortunately, I'm working from memory, but binutils is needed to build gcc
properly, and I believe it was in the binutils configure where it wants to
set up to run lex or flex if one of those is available. On a basic HPUX
installation the configure sees the lex libraries and so the build breaks
down trying to run the non-existent lex. One of the ways to avoid this
failure is to install flex. True, it's not directly needed to build gcc, but
no one would be trying to install binutils except for the purpose of building
gcc, and it's difficult to come by the necessary information in a reasonable
time. However, my employer is not willing to continue to support HPUX,
certainly not to license HP compilers or upgrade to HPUX11, and my hp-735 has
been removed in favor of NT, so I am struggling now with the non-standard
features of HP's NT rather than the strange by-ways of HPUX.
Tim